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:
http://wiki.apache.org/ws/FrontPage/Woden/WSDLExtensionChanges

------------------------------------------------------------------------------
  
  The {{{ExtensionRegistry}}} methods that handled the 
{{{ComponentExtensions}}} type have been changed to use 
{{{ComponentExtensionContext}}} instead. These are the 
{{{registerComponentExtension}}} and {{{createComponentExtension}}} methods.
  
- ''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.
+ ''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 ===
  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.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to