You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by Christopher Riley <cr...@hkmconsultingllc.com> on 2010/02/03 06:28:54 UTC
Example of handling SOAP Header with mustUnderstand
The 2.3 migration notes describe the change from earlier releases and the requirement to use the property endpoint-processes-headers set to the QName of the header. I cannot find any details in the documentation as to where and how this property should be set.
Christopher Riley | Manager
HKM Consulting LLC
(o)508.923.8685 | (m)508.273.3102
criley@hkmconsultingllc.com
hkmconsultingllc.com
Re: Example of handling SOAP Header with mustUnderstand
Posted by Christopher Riley <cr...@hkmconsultingllc.com>.
Thanks Dan. We will give this a try.
Regards
Chris
Chris Riley
(508)273-3102
On Feb 3, 2010, at 2:57 PM, Daniel Kulp <dk...@apache.org> wrote:
> In your "jaxws:endpoint" element, just add something like:
>
>
> <jaxws:properties>
> <entry key="endpoint-processes-headers"
> value="{http://cxf.apache.org/outofband/Header}
> outofbandHeader"/>
> </jaxws:properties>
>
> Note: I'm still kind of working on this and it may change again.
> The JAX-WS
> TCK is having an issue with this so I may have to adjust it a bit,
> but I
> haven't had a chance to dig into the failure yet.
>
> I'm also planning on adding an annotation that could be added to the
> impl.
> Something like:
>
> @ProcessesHeaders( headers =
> {"{http://cxf.apache.org/outofband/Header}outofbandHeader"} )
>
> or similar.
>
>
> Dan
>
> On Wed February 3 2010 12:28:54 am Christopher Riley wrote:
>> The 2.3 migration notes describe the change from earlier releases
>> and the
>> requirement to use the property endpoint-processes-headers set to the
>> QName of the header. I cannot find any details in the documentation
>> as to
>> where and how this property should be set.
>>
>> Christopher Riley | Manager
>> HKM Consulting LLC
>> (o)508.923.8685 | (m)508.273.3102
>> criley@hkmconsultingllc.com
>> hkmconsultingllc.com
>>
>
> --
> Daniel Kulp
> dkulp@apache.org
> http://www.dankulp.com/blog
Re: Example of handling SOAP Header with mustUnderstand
Posted by Daniel Kulp <dk...@apache.org>.
In your "jaxws:endpoint" element, just add something like:
<jaxws:properties>
<entry key="endpoint-processes-headers"
value="{http://cxf.apache.org/outofband/Header}outofbandHeader"/>
</jaxws:properties>
Note: I'm still kind of working on this and it may change again. The JAX-WS
TCK is having an issue with this so I may have to adjust it a bit, but I
haven't had a chance to dig into the failure yet.
I'm also planning on adding an annotation that could be added to the impl.
Something like:
@ProcessesHeaders( headers =
{"{http://cxf.apache.org/outofband/Header}outofbandHeader"} )
or similar.
Dan
On Wed February 3 2010 12:28:54 am Christopher Riley wrote:
> The 2.3 migration notes describe the change from earlier releases and the
> requirement to use the property endpoint-processes-headers set to the
> QName of the header. I cannot find any details in the documentation as to
> where and how this property should be set.
>
> Christopher Riley | Manager
> HKM Consulting LLC
> (o)508.923.8685 | (m)508.273.3102
> criley@hkmconsultingllc.com
> hkmconsultingllc.com
>
--
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog
Re: Example of handling SOAP Header with mustUnderstand
Posted by Daniel Kulp <dk...@apache.org>.
Well, you would need to configure something in to handle WS-Security. There
are really two options:
1) Configure in the older WSS4JInInterceptor to handle it
2) Define a WS-SecurityPolicy in the wsdl that defines what is expected.
Some docs at:
http://cxf.apache.org/docs/ws-security.html
Dan
On Thu February 18 2010 3:02:36 pm PrSd wrote:
> Sending the following SOAP Header :
>
> <soap:Header><wsse:Security
> xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecur
> ity-secext-1.0.xsd" mustUnderstand="1">....
>
> and getting back a
>
> org.apache.cxf.binding.soap.SoapFault: MustUnderstand headers:
> [{http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext
> -1.0.xsd}Security] are not understood.
> at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:141)
>
> I am using CXF 2.2.6. I am new to CXF so if you can reply in detail I would
> really be grateful to you.
>
> thanks
>
> Christopher Riley wrote:
> > The 2.3 migration notes describe the change from earlier releases and the
> > requirement to use the property endpoint-processes-headers set to the
> > QName of the header. I cannot find any details in the documentation as to
> > where and how this property should be set.
> >
> > Christopher Riley | Manager
> > HKM Consulting LLC
> > (o)508.923.8685 | (m)508.273.3102
> > criley@hkmconsultingllc.com
> > hkmconsultingllc.com
--
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog
Re: Example of handling SOAP Header with mustUnderstand
Posted by PrSd <si...@yahoo.com>.
Sending the following SOAP Header :
<soap:Header><wsse:Security
xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
mustUnderstand="1">....
and getting back a
org.apache.cxf.binding.soap.SoapFault: MustUnderstand headers:
[{http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd}Security]
are not understood.
at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:141)
I am using CXF 2.2.6. I am new to CXF so if you can reply in detail I would
really be grateful to you.
thanks
Christopher Riley wrote:
>
> The 2.3 migration notes describe the change from earlier releases and the
> requirement to use the property endpoint-processes-headers set to the
> QName of the header. I cannot find any details in the documentation as to
> where and how this property should be set.
>
> Christopher Riley | Manager
> HKM Consulting LLC
> (o)508.923.8685 | (m)508.273.3102
> criley@hkmconsultingllc.com
> hkmconsultingllc.com
>
>
>
>
>
>
>
>
>
>
>
>
>
>
--
View this message in context: http://old.nabble.com/Example-of-handling-SOAP-Header-with-mustUnderstand-tp27431684p27644810.html
Sent from the cxf-user mailing list archive at Nabble.com.