axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sanka Samaranayake (JIRA)" <>
Subject [jira] Updated: (AXIS2-2120) Metadata Exchange support on Axis2
Date Wed, 14 Feb 2007 06:44:05 GMT


Sanka Samaranayake updated AXIS2-2120:


I've reviewed the uploaded patch and it looks good to me except for few minor errors. ( I've
fixed them and uploaded the files to the JIRA).

IMO, the DataLocator concept makes lot of senses. Perhaps Gee could provide few concrete scenario
that demonstrate the use of DataLocators, to ensure we fully understand it before committing
it to the codebase.

However the MetadataExchange module has a limitation where it doesn't support WS-Transfer
based metadata requests. However there is a workaround. Since the wsa:To of the WS-Transfer
based metadata requests ends with '/metadata', you can rename the control operation of the
module to 'metadata' s.t. any of those requests are dispatched to that operation via RequestURIBasedOperationDispatcher.
Then you can check whether the soap action is equal to WS-Transfer-Get action and process
appropriately.  (The MexMessageReceiver and module.xml with the suggested changes are also

> Metadata Exchange support  on Axis2
> -----------------------------------
>                 Key: AXIS2-2120
>                 URL:
>             Project: Axis 2.0 (Axis2)
>          Issue Type: New Feature
>          Components: modules
>    Affects Versions: nightly
>            Reporter: Gee Chia
>         Attachments: mexPatch,
> New features to support WS-MetadataExchange specification on Axis.  Basically, to support
incoming Get Metadata request message from SOAP protocol engines, Axis2 SOAP processing is
extended with new metadataExchange module, and allows plug-in of Data Locators. Data Locator
is responsible to perform data retrieval. The plug-in support allows other Web Services engines
that build on top of Axis2 to support different data retrieval implementation. 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

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

View raw message