[jira] Resolved: (AXIS2-2710) throws when OutflowSecurity is on

["Deepal Jayasinghe (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AXIS2-2710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Deepal Jayasinghe resolved AXIS2-2710.
--------------------------------------

    Resolution: Won't Fix

Wont belong here, it is Rampart 

> <xs:any> throws when OutflowSecurity is on
> ------------------------------------------
>
>                 Key: AXIS2-2710
>                 URL: https://issues.apache.org/jira/browse/AXIS2-2710
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>         Environment: Axis 1.1.1, out of the box. Slightly modified axis2.xml is enclosed.
>            Reporter: Rich Adili
>            Assignee: Ruchith Udayanga Fernando
>            Priority: Critical
>         Attachments: xsanybug.zip
>
>
> One of my methods takes, among other things, an <xs:any> bit of generic xml. Can't make heads or tails of this exception. Only clue I've found is that the exception does not fire if I create the stub using one of the ctors that does not take a ConfigurationContext The only unusual thing in my config is the .NET-style OutflowSecurity, which works fine if I'm not sending an <xs:any> message. I've tried commenting out the OutflowSecurity and the exception goes away.
> java.lang.reflect.InvocationTargetException
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at test.GUI$2$1.run(GUI.java:89)
> 	at java.lang.Thread.run(Thread.java:595)
> Caused by: org.apache.axis2.AxisFault: Error in extracting message properties; nested exception is: 
> 	org.apache.rampart.RampartException: Error in extracting message properties
> 	at org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:65)
> 	at org.apache.axis2.engine.Phase.invoke(Phase.java:382)
> 	at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:522)
> 	at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:655)
> 	at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:237)
> 	at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:202)
> 	at net.xatanet.axisstubs.ConduitServiceStub.ModifyData(ConduitServiceStub.java:274)
> 	at net.xatanet.services.ConduitService.modifyData(ConduitService.java:102)
> 	at test.TestModifyData.invokeTest(TestModifyData.java:40)
> 	... 6 more
> Caused by: org.apache.rampart.RampartException: Error in extracting message properties
> 	at org.apache.rampart.RampartMessageData.<init>(RampartMessageData.java:294)
> 	at org.apache.rampart.MessageBuilder.build(MessageBuilder.java:56)
> 	at org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:59)
> 	... 14 more
> Caused by: org.apache.ws.security.WSSecurityException: Error in converting SOAP Envelope to Document; nested exception is: 
> 	org.apache.axiom.om.OMException: javax.xml.stream.XMLStreamException
> 	at org.apache.rampart.util.Axis2Util.getDocumentFromSOAPEnvelope(Axis2Util.java:121)
> 	at org.apache.rampart.RampartMessageData.<init>(RampartMessageData.java:146)
> 	... 16 more
> Caused by: org.apache.axiom.om.OMException: javax.xml.stream.XMLStreamException
> 	at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:194)
> 	at org.apache.axiom.om.impl.dom.NodeImpl.build(NodeImpl.java:469)
> 	at org.apache.axiom.om.impl.dom.DocumentImpl.build(DocumentImpl.java:476)
> 	at org.apache.rampart.util.Axis2Util.getDocumentFromSOAPEnvelope(Axis2Util.java:107)
> 	... 17 more
> Caused by: javax.xml.stream.XMLStreamException
> 	at org.apache.axiom.om.impl.llom.OMStAXWrapper.updateLastNode(OMStAXWrapper.java:952)
> 	at org.apache.axiom.om.impl.llom.OMStAXWrapper.next(OMStAXWrapper.java:913)
> 	at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:111)
> 	... 20 more

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.