Andrew is (sort-of) right:
http://issues.apache.org/jira/browse/MUSE-166
This adds the ability to specify custom headers for client side, and
receive them on the server side. However, I think I need to update the
routing mechanism so that it takes the extra Element[] into consideration
when invoking the methods on the capability.
While I'm doing that, Vinh, can you try the wsdl2java flag for custom
headers and make sure it generates the the parameter(s) you're looking
for?
Dan
Andrew Eberbach/Durham/[EMAIL PROTECTED] wrote on 01/31/2007 05:46:27 PM:
> 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
> [EMAIL PROTECTED]
>
>
>
> "Vinh Nguyen \(vinguye2\)" <[EMAIL PROTECTED]>
> 01/31/2007 05:35 PM
> Please respond to
> [email protected]
>
>
> To
> <[email protected]>
> 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: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
