Paul
Yes, we need to spend more time on this, as this is almost the same
example used in the Axis2 Integration test scenario 3 - which works
during an Axis2 build.
The error we encounter at Axis2 is:
java.lang.NullPointerException
at
org.apache.axiom.om.impl.dom.ChildNode.getNextOMSibling(ChildNode.java:45)
at
org.apache.axiom.om.impl.dom.ElementImpl.getNextOMSibling(ElementImpl.java:1355)
at
org.apache.axiom.om.impl.dom.ChildNode.getNextSibling(ChildNode.java:52)
at
org.apache.ws.security.util.WSSecurityUtil.findElementById(WSSecurityUtil.java:299)
at
org.apache.ws.security.util.WSSecurityUtil.getElementByWsuId(WSSecurityUtil.java:439)
at
org.apache.ws.security.message.token.SecurityTokenReference.getTokenElement(SecurityTokenReference.java:176)
at
org.apache.ws.security.processor.SignatureProcessor.verifyXMLSignature(SignatureProcessor.java:186)
at
org.apache.ws.security.processor.SignatureProcessor.handleToken(SignatureProcessor.java:79)
at
org.apache.ws.security.WSSecurityEngine.processSecurityHeader(WSSecurityEngine.java:279)
at
org.apache.ws.security.WSSecurityEngine.processSecurityHeader(WSSecurityEngine.java:201)
at org.apache.rampart.RampartEngine.process(RampartEngine.java:62)
at
org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:74)
....
And on the Synapse side, we encounter issue
http://issues.apache.org/jira/browse/WSCOMMONS-104 (Caused due to use of
Rampart) while trying to process the above fault message.
thanks
asankha
Paul Fremantle wrote:
Asankha
With the Signing/Enc am I right in understanding that the target
service (Axis2) can't understand the messages that Synapse is
creating?
Paul
Seems like a simple issue (104). Can we get a timeline?
On 10/4/06, Asankha C. Perera <[EMAIL PROTECTED]> wrote:
Paul
I have just checked in the changes for the new Policy framework with two
sample services which could be deployed on an Axis2 instance and a
sample Synapse configuration to demonstrate this. Though the first
example works, the second example which demonstrates signing and
encryption fails on the Axis2 server side currently due to an issue I
couldn't figure out yet with help from Ruchith. But it seems like its
not on Synapse side, and hence I'm checking in these changes. Also when
Rampart is being used, we are hit by
http://issues.apache.org/jira/browse/WSCOMMONS-104 which prevents
Synapse from reading a SOAP fault in an incoming fault message. This
again is out of our scope, and should work once Axiom is fixed - though
this may take some time.
asankha
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
