Well, the security was just an example. I'm trying to integrate WSDM with a WS-CAF implementation, so in sends Context information in the headers and so, I need to get that information and then send it to another service.
On 11/15/06, Daniel Jemiolo <[EMAIL PROTECTED]> wrote:
I think that comment is outdated - in WS-A 08/2004, all non-WS-A headers were assumed to be possible reference parameters, so we did just that. This was pretty vague, and the WS-A authors fixed it in WS-A 08/2005 - now only elements with a wsa:IsReferenceParameter attribute are considered parameters. So you will not get the other SOAP headers from this class. I will update the JavaDoc to reflect this. In the meantime, if you're doing security-type work with the SOAP headers, why not use the Axis2 programming model for doing this? They have documented ways to add pre-request and post-request handlers, and a security library (WSS4J). Dan "José Antonio Sánchez" <[EMAIL PROTECTED]> wrote on 11/13/2006 04:13:05 PM: > So in the current snapshot there is no way to acess to headers from a > Capability code, isn't it? In the message headers class, in the > constructor > > http://ws.apache.org/muse/docs/2.0. > 0/javadoc/org/apache/muse/ws/addressing/MessageHeaders. > html#MessageHeaders(org.w3c.dom.Element) > > It says: > ... > The wsa:To URI is transformed into an EPR. If there are non-WS-A > headers in the SOAP Header, these are tranformed into reference > properties for the wsa:To EPR. > ... > > While a snapshot is released that supports the complete header reading: > - Can I use MessageHeaders.toXML() to transform it to a DOM and then > read it with the DOM interface? > - Can I use EndPointReference.getParameter() to read it? > > > On 11/13/06, Daniel Jemiolo <[EMAIL PROTECTED]> wrote: > > Hi, > > > > I was actually hoping to answer this after we got all of our changes in > > for 2.1, which will run on the latest Axis2 1.1 release candidate; the > > Axis2 1.1 RC 2 build makes it much easier to get the SOAP headers from > > anywhere in a service. The current code won't run on 1.1 RC 2 because of > > compatibility changes in the Axis2 core engine. > > > > So... if it's not urgent, we're hoping to get the new content/build up > > asap! Sorry for the delay. :/ > > > > For future reference, the Axis2 1.1 API for getting the SOAP headers will > > be: > > > > MessageContext.getCurrentMessageContext().getEnvelope().getHeader(); > > > > thanks, > > Dan > > > > > > > > "Vinh Nguyen \(vinguye2\)" <[EMAIL PROTECTED]> wrote on 11/13/2006 > > 03:21:51 PM: > > > > > Jose, > > > Not sure about this, but perhaps the SimpleResourceRouter class might > > help? > > > The muse.xml file has this class specified by default for passing > > requests to > > > resources. In the javadocs, the SimpleResourceRouter.invoke(Element) > > method > > > specifies that it receives the parameters still in its SOAP body form. > > I'm > > > not sure if this means that it is receiving the original raw request > > data, or > > > data that has already been processed in a way that is readable by the > > router. > > > > > > > > > -----Original Message----- > > > From: José Antonio Sánchez [mailto:[EMAIL PROTECTED] > > > Sent: Monday, November 13, 2006 7:23 AM > > > To: [email protected]; [email protected] > > > Subject: Can I access to the SOAP message from a Capability? > > > > > > I have seen how to access the addressing headers from a Capability, but > > is > > > there a way to access to the raw SOAP message so I can access to some > > other > > > headers elements (like ws-security headers)? > > > > > > -- > > > Saludos. > > > José Antonio Sánchez > > > > > > --------------------------------------------------------------------- > > > 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] > > > > > > > -- > Saludos. > José Antonio Sánchez > > --------------------------------------------------------------------- > 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]
-- Saludos. José Antonio Sánchez --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
