[ http://issues.apache.org/jira/browse/AXIS2-704?page=all ]
Davanum Srinivas resolved AXIS2-704:
------------------------------------
Resolution: Fixed
Applied. thanks.
-- dims
> Extract and support wsaw:UsingAddresing on service side
> -------------------------------------------------------
>
> Key: AXIS2-704
> URL: http://issues.apache.org/jira/browse/AXIS2-704
> Project: Apache Axis 2.0 (Axis2)
> Type: Sub-task
> Reporter: David Illsley
> Attachments: patch.txt, patch.txt
>
> Support for wsaw:UsingAddressing can be split into 2 parts:
> 1. Server side support to reject inbound messages if addressing is required
> and it is not present (or not processed)
> 2. Client side support to automatically engage the addressing module
> This issue is to include support for 1 above (I haven't delved into codegen
> code yet)
> The patch to follow includes:
> 1. Methods AxisService::get/setWSAddressingFlag() to represent whether
> ws-addressing is required/optional/undefined for a given service
> 2. Code added to ServiceBuilder to read an attribute on the service element
> in the services.xml and call axisService.setWSAddressingFlag appropriately.
> 3. Code added to WSDL2AxisServiceBuilder to read wsaw:UsingAddressing
> elements from wsdl an call axisService.setWSAddressingFlag appropriately.
> 4. Code added to AxisEngine to check that the addressing namespace has been
> set on the message context if WSAddressing is required and faults if it is not
> 5. Code added to AxisService2OM to generate appropriate wsaw:UsingAddressing
> elements based on the value of axisService.getWSAddressingFlag
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
