OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsrp message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: V2 Schema and WSDL Issues


Looking at the draft xsd and wsdl files, I would like to bring up a few 
points.

The current wsrp_v2_types.xsd redefines all V1 types in a new V2 
namespace URI, and then makes modifications to it. On the positive side, 
this makes it easy for certain implementations

- those that only offer V2
- those that would like to maintain separate V1 and V2 implementations 
with minimal code sharing.
- those that use generic programming (such as DOM, SAAJ etc.).

For those implementations that generate types from the schema (e.g. 
JAX-RPC), this approach makes type-sharing impossible since V1 and V2 
types have no association (e.g. xs:extension). AFAIK, none of the web 
service stacks support any namespace mapping between compatible versions.

Another issue is that V1 Consumers cannot send a V1-compliant message to 
a V2 Producer, unless the Producer offers V1 port that accepts a V1 
message, which goes back to code sharing.

Rich - I know you mentioned this earlier, do you still have a V2 xsd 
that extends V1 xsd? If required, I can explore this further.

On the otherhand, extensions don't completely solve the problem, 
particularly when we change deeply nested types (I've examples, if 
anyone is interested). So, as long as the additions we make are 
immediately under the root of a message, we should be able to reuse 
sub-types.

Any thoughts?

Subbu


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]