[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [ebxml-cppa-negot] Re: [ebxml-cppa] Moberg 5/23/2004: Use of Substitution Groups
I think JAXB might be used when manipulating CPPA structures (CPP or CPA) so according to Farrukh, no problems there. JAXRPC _might_ be relevant to implementations. Since the extensibility options are substitution groups on global elements, I think ebCPPA will be covered by Java APIs just as the ebXML Registry has been. Dale -----Original Message----- From: Monica J. Martin [mailto:Monica.Martin@Sun.COM] Sent: Monday, May 24, 2004 1:11 PM To: Farrukh Najmi Cc: ebxml-cppa-negot; ebxml-cppa@lists.oasis-open.org Subject: [ebxml-cppa-negot] Re: [ebxml-cppa] Moberg 5/23/2004: Use of Substitution Groups >> mm1: Dale, >> In the informal F2F in late April, we discussed use of the >> substitution groups and increasing extensibility to further support a >> service-based approach. How does this approach align with JAXB and >> JAX-RPC (For example, relationship of types of element in a group)? > > Najmi: Here is my experience with latest JAXB and JAXRPC. ebXML > Registry 3.0 schema is using element substitution with latest JAXB > from JWSDP 1.4 and it seems well supported. We had some trouble with > JAXRPC but I believe that has been fixed within JAXRPC for JWSDP 1.4 > version. > > ebXML Registry specs use element substitution heavily for > extensibility. mm2: Thanks, Farrukh. Now, perhaps Dale can answer with the extensibility options being placed / discussed for ebCPPA. Regards. To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/ebxml-cppa-negot/members/le ave_workgroup.php.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]