A clean separation exists between the WSDL 2.0 xml model and the WSDL 2.0
component model within the WSDL 2.0 spec. You guys have done a great job
manifesting this within the Woden architecture. There are a few places
within Woden, however, where this separation has become blurred:
1. WSDLReader impls should not throw an exception if a wsdl:import fails to
resolve to a wsdl document when building the xml model. QName resolution
should be deferred to the time at which component model is generated, i.e.
broken references within the xml model are NOT errors. The WSDL 2.0 spec
states that the location attribute on a wsdl:import is optional, and if
present, it is merely a hint.
2. Schema docs contained within TypesElement are parsed into Schema
components rather than SchemaElements (which may model a schema language
other than xml shema.) Schema component generation should be deferred to
component model generation using a deserializer. Woden's xml schema
deserializer should be registered within pre-populated extension registry. A
Schema component should be a ComponentExtension?
3. BindingFaultReferenceElement has no Direction attribute, i.e. user has no
way of distinguishing between an infault and an outfault element without
access to component model. Note that the BindingMessageReferenceElement API
is correct in this regard.
By maintaining the separation between component model and xml model, Woden
becomes much more flexible, i.e. allowing users to leverage one or the
other, or both. This is especially critical in situations where referenced
components may be constructed from information other than an XML 1.0
serialization.
_________________________________________________________________
Get free, personalized commercial-free online radio with MSN Radio powered
by Pandora http://radio.msn.com/?icid=T002MSN03A07001
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
