ws-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <>
Subject [Ws Wiki] Update of "FrontPage/Woden/WSDLExtensionChanges" by JohnKaputin
Date Mon, 04 Feb 2008 23:32:00 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Ws Wiki" for change notification.

The following page has been changed by JohnKaputin:

The comment on the change is:
WSDL Extension Changes page

  ''NOTE:'' Extension properties cannot be treated entirely generically. They can be accessed
in a generic way and ''wrapped'' as generic {{{ExtensionProperty}}} objects, but the caller
will still need to know what to do with the {{{java.lang.Object}}} returned by the {{{ExtensionProperty.getContent()}}}
method - what to cast it to or whether it implements a useful toString() method. Woden should
possibly provide some guidance here, like ''"extension implementors should define a suitable
{{{toString()}}} method for their extension properties, or for items in an extension property
based on a set."''. Then, client applications like GUI tools can at least display extension
property content without needing to know what type of object it is. As the Woden API convention
is to return typed-arrays for a ''set'' property, applications could just check for an Array
type, then call {{{toString()}}} on each element.
  === API change impact ===
- Changes to the {{{WSDLComponent}}} API are:
-  * {{{ComponentExtensions getComponentExtensionsForNamespace(NSuri)}}} is replaced by {{{ComponentExtensionContext
-  * 
+ Most of the API changes in WODEN-47 are additions to the API. Changes to the existing API
have been minimized to keep the new extension model largely backward-compatible.
+ The necessary changes to the existing API are:
+  * calls to {{{WSDLComponent.getComponentExtensionsForNamespace(NSuri)}}} must be replaced
with {{{WSDLComponent.getComponentExtensionContext(NSuri)}}} (the extension subtypes like
{{{SOAPBindingExtensions}}} have been changed to the new super-type, so those APIs will not
be affected)
+  * calls to {{{ExtensionRegistry.createComponentExtension}}} will now return {{{ComponentExtensionContext}}}
instead of {{{ComponentExtensions}}}, but this method is typically called by Woden anyway,
not by user code.
  === Overview of the new Component extensions model ===

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message