[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: [regrep] ebXML Reg Rep & UDDI interoperability
I agree with Matt's observation that the JAXR API [1] can map to other languages rather easily and would not look very different in C++ or C# than it does in Java. Max, JAXR (like other JCP approved standard APIs) is not "about a particular vendor-specific implementation" as you put it. It is a standard Java API agreed upon by the JCP membership which is several hundred companies (See http://www.jcp.org/en/participation/members ). I will respond separately to the UDDI usage suggestion from Max. [1] http://www.jcp.org/en/jsr/detail?id=93 -- Regards, Farrukh Matthew MacKenzie wrote: > Ok, so download the JAXR spec, and wherever is says > Object.getProperty() change it to Object.GetProperty(), or possibly > Object.Property() if you are using c# and some of its neat features. > > :-) > > Seriously, the JAXR (Java API for XML Registries) spec, which Farrukh > can elaborate on if he wishes (he was the JSR lead), is just an API > specification which could be mapped to .NET with no problems. I agree > that something more language neutral would be optimal, maybe "AXR", > but Farrukh & Co. have already done the heavy lifting on it. > > Farrukh: Is there anything stopping us from doing "AXR" by using the > JAXR stuff verbatim? > > -Matt > > Max Voskob wrote: > >> Matthew, sorry, I'm in MS camp. Have no idea about JARX. >> >> I'm not talking about a particular vendor-specific implementation. >> I'm talking about providing a mapping and recommendations at the spec >> level >> so it can be implemented on any platform. >> >> Cheers, >> Max >> >> >> ----- Original Message ----- >> From: "Matthew MacKenzie" <matt@mac-kenzie.net> >> To: "Max Voskob" <mvoskob@msi.net.nz> >> Cc: "OASIS_RegRep (E-mail)" <regrep@lists.oasis-open.org> >> Sent: Wednesday, February 12, 2003 10:41 AM >> Subject: Re: [regrep] ebXML Reg Rep & UDDI interoperability >> >> >> >> >>> Max, >>> >>> Check out JAXR. It's business query interface is somewhat like UDDI >>> and >>> it has already done the work for mapping between data models. >>> >>> -Matt >>> >>> Max Voskob wrote: >>> >>> >>> >>>> Hi guys, >>>> >>>> As you know, I'm just watching your TC like fly on the wall, but >>>> >>> >> sometimes I >> >> >>>> stretch my wings and make a little buzz. So here we go bzzzz :) >>>> >>>> I'm not sure if you discussed this option before, but I thought of >>>> >>> >> providing >> >> >>>> some UDDI interfaces to your Registry. >>>> >>>> Lets say that an organization is using a web-services platform, but >>>> they >>>> want to use Reg/Rep as well. It would be very inconvenient to have 2 >>>> registries - UDDI and Reg/Rep. Why can't they talk to Reg/Rep thru >>>> UDDI >>>> interfaces? >>>> I don't think that implementing all UDDI interfaces is a wise idea, >>>> but >>>> >>> >> the >> >> >>>> query interface would definitely come handy. >>>> >>>> Still sounds weird? Think again! ;) >>>> >>>> Cheers, >>>> Max >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> ---------------------------------------------------------------- >>>> To subscribe or unsubscribe from this elist use the subscription >>>> manager: <http://lists.oasis-open.org/ob/adm.pl> >>>> >>>> >>>> >>> >> >> >> ---------------------------------------------------------------- >> To subscribe or unsubscribe from this elist use the subscription >> manager: <http://lists.oasis-open.org/ob/adm.pl> >> >>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC