[jbossws-issues] [JBoss JIRA] Reopened: (JBWS-1938) Assign message name instead of IN and OUT for Inbound/Outbound Addressing Property

[Heiko Braun (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBWS-1938?page=all ]

Heiko Braun reopened JBWS-1938:
-------------------------------

             
Please double check with the WSA spec. I think IN/OUT is the required default.

> Assign message name instead of IN and OUT for Inbound/Outbound Addressing Property
> ----------------------------------------------------------------------------------
>
>                 Key: JBWS-1938
>                 URL: http://jira.jboss.com/jira/browse/JBWS-1938
>             Project: JBoss Web Services
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: ws-addressing, jbossws-native
>    Affects Versions: jbossws-1.2.1,  jbossws-2.0.2
>            Reporter: Magesh Kumar B
>         Assigned To: Magesh Kumar B
>             Fix For: jbossws-native-2.0.4
>
>          Time Spent: 3 hours
>  Remaining Estimate: 0 minutes
>
> When wsa:action is not set explicitly the builder just appends IN or OUT to the endpoint's QName. This does not indicate as to what operation was perfomed when we peek the SOAP Message header. 
> All along I was thinking that it worked fine for JAXWS tests, but it 
> has been hard-coded in JAXWSMetaDataBuilder.java: 
> // default action values 
>       { 
>          // TODO: figure out a way to assign message name instead of IN and OUT 
>          String tns = epMetaData.getPortName().getNamespaceURI(); 
>          String portTypeName = epMetaData.getPortName().getLocalPart(); 
>          addrExt.setInboundAction(tns + "/" + portTypeName + "/IN"); 
>          if (!opMetaData.isOneWay()) 
>             addrExt.setOutboundAction(tns + "/" + portTypeName + "/OUT"); 
>       } 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira