Thanks Dan, I will have to try and test this sometime later. Due to the current bug with wsdl imports (Muse-161), I've been avoiding using Muse2.1.0's wsdl2java. It's also hard for me to work around it because I'm working with wsdls maintained by another team, and the wsdl/xsds have various levels of inheritence that make it difficult to cut-paste into a single file.
Also, the request header properties are currently being generated dynamically. That is, they are not defined in the wsdl as part of the request header, so I assume the wsdl2java flag approach may not work for me. Out of curiousity though, what would the wsdl have to look like so that the new flag can generate the new method signatures? -Vinh -----Original Message----- From: Daniel Jemiolo [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 31, 2007 2:59 PM To: [email protected] Subject: Re: custom header properties 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
