search

javaee / metro-jax-ws

https://javaee.github.io/metro-jax-ws/
Other
132 stars 68 forks source link

Ability to mark outbound WS-Addressing headers with mustUnderstand #737

Open glassfishrobot opened 15 years ago

glassfishrobot commented 15 years ago

Currently JAX-WS always generates the WS-Addressing headers Action and ReplyTo without mustUnderstand attribute:

<?xml version='1.0' encoding='UTF-8'?><S:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"><To xmlns="http://www.w3.org/2005/08/addressing">[http://localhost/service](http://localhost/service)SomeAction<ReplyTo xmlns="http://www.w3.org/2005/08/addressing">

[http://www.w3.org/2005/08/addressing/anonymous](http://www.w3.org/2005/08/addressing/anonymous)

<MessageID xmlns="http://www.w3.org/2005/08/addressing">uuid:135b3a91-ac4b-4ca9-9439-38a91eb5302c</S:Header><test /></S:Body></S:Envelope>

This could result in unexpected service failure if the SOAP receiver does not understand the WS-Addressing headers and fails to respond accordingly.

It would be nice if a JAX-WS RI API user could control the "mustUnderstand" attribute on outbound messages by setting AddressingFeature's required field to true (mustUnderstand=1").

Environment

Operating System: All Platform: All

Affected Versions

[2.1.5]

glassfishrobot commented 15 years ago

Reported by walco@java.net

glassfishrobot commented 15 years ago

jitu@java.net said: Assigning this to Rama.

glassfishrobot commented 13 years ago

venkikeesara said: Hi ,

Is this issue is fixed in any version of JAX-WS RI and when could be the expected fix date ?

glassfishrobot commented 13 years ago

ramapulavarthi said: This issue has been fixed in JAX-WS RI 2.2.2 as http://java.net/jira/browse/JAX_WS-895

If is AddressingFeature is configured as required either programtically or via policy assertion then mustUnderstand attribute is added. Also, We add only on wsa:Action header as that would suffice the WS-I BP requirements that if one of the WSA headers is MU, then all of the WSA headers are treated as MU headers.

glassfishrobot commented 13 years ago

ramapulavarthi said: This issue is fixed as JAX-WS-895.

glassfishrobot commented 15 years ago

Issue-Links: depends on JAX_WS-895

glassfishrobot commented 15 years ago

Was assigned to ramapulavarthi

glassfishrobot commented 7 years ago

This issue was imported from java.net JIRA JAX_WS-737