Hi Andrew,
This is actually on the server side, not the client. The server
capability needs to get the header properties specified in the client
request. This is to support other standards, like WS-Security.
-Vinh
-----Original Message-----
From: Andrew Eberbach [mailto:aeberbac@us.ibm.com]
Sent: Wednesday, January 31, 2007 2:46 PM
To: muse-user@ws.apache.org
Subject: Re: custom header properties
Hi,
This was changed in the code generation. Same flag as for the proxy.
Thanks,
Andrew
Andrew Eberbach
Autonomic Computing
(919) 254-2645
T/L: 444-2645
aeberbac@us.ibm.com
"Vinh Nguyen \(vinguye2\)" <vinguye2@cisco.com>
01/31/2007 05:35 PM
Please respond to
muse-user@ws.apache.org
To
<muse-user@ws.apache.org>
cc
Subject
custom header properties
I remember that recently there was a discussion on how to send custom
properties in the request header. The resolution was a new
AbstractResourceClient.invoke(String,Element,Element[]) method. But, I
haven't seen a corresponding update on the server side on how to get
those custom properties, particularly in a capability class.
Is there a way to get the custom header properties from within a
capability class? I tried
Capability.getEnvironment.getAddressingContext().toXML(), but it only
returns the properties it explicitly knows about (i.e. has methods for).
Any help is appreciated, thanks!
-Vinh
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-user-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-user-help@ws.apache.org
|