Forum Stats

  • 3,750,548 Users
  • 2,250,192 Discussions
  • 7,867,003 Comments

Discussions

Exception in thread "main" org.apache.axis2.AxisFault: Error in extracting

801558
801558 Member Posts: 9
I am getting this exception when I call the web service from the client. Please help me here.

Exception in thread "main" org.apache.axis2.AxisFault: Error in extracting message properties
at org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:70)
at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:262)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:427)
at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:406)
at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
at com.ttdev.ss.SecureServiceStub.concat(SecureServiceStub.java:182)
at com.ttdev.ss.SecureClient.main(SecureClient.java:29)
Caused by: org.apache.rampart.RampartException: Error in extracting message properties
at org.apache.rampart.RampartMessageData.<init>(RampartMessageData.java:386)
at org.apache.rampart.MessageBuilder.build(MessageBuilder.java:61)
at org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:64)
... 9 more
Caused by: org.apache.ws.security.WSSecurityException: Error in converting SOAP Envelope to Document; nested exception is:
java.lang.UnsupportedOperationException: TODO
at org.apache.rampart.util.Axis2Util.getDocumentFromSOAPEnvelope(Axis2Util.java:161)
at org.apache.rampart.RampartMessageData.<init>(RampartMessageData.java:272)
... 11 more
Caused by: java.lang.UnsupportedOperationException: TODO
at org.apache.axiom.om.impl.dom.DocumentImpl.setStandalone(DocumentImpl.java:415)
at org.apache.axiom.om.impl.builder.StAXOMBuilder.createDocument(StAXOMBuilder.java:190)
at org.apache.axiom.om.impl.builder.StAXOMBuilder.<init>(StAXOMBuilder.java:105)
at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.<init>(StAXSOAPModelBuilder.java:167)
at org.apache.rampart.util.Axis2Util.getDocumentFromSOAPEnvelope(Axis2Util.java:130)
... 12 more

Client WSDL:
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions name="SecureService"
targetNamespace="http://ttdev.com/ss"
xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200512"
xmlns:wsp="http://www.w3.org/Submission/2006/SUBM-WS-Policy-20060425"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:tns="http://ttdev.com/ss"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurityutility-1.0.xsd">
<wsdl:types>
<xsd:schema targetNamespace="http://ttdev.com/ss">
<xsd:element name="concat">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="s1" type="xsd:string"/>
<xsd:element name="s2" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="concatResponse">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="r" type="xsd:string">
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
</wsdl:types>
<wsdl:message name="concatResponse">
<wsdl:part name="parameters" element="tns:concatResponse">
</wsdl:part>
</wsdl:message>
<wsdl:message name="concatRequest">
<wsdl:part name="parameters" element="tns:concat">
</wsdl:part>
</wsdl:message>
<wsdl:portType name="SecureService">
<wsdl:operation name="concat">
<wsdl:input message="tns:concatRequest">
</wsdl:input>
<wsdl:output message="tns:concatResponse">
</wsdl:output>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="SecureServiceSOAP" type="tns:SecureService">
<wsp:PolicyReference URI="#p1" wsdl:required="true"/>
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="concat">
<soap:operation soapAction="http://ttdev.com/ss/NewOperation"/>
<wsdl:input>
<soap:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="SecureService">
<wsdl:port name="p1" binding="tns:SecureServiceSOAP">
<soap:address location="http://localhost:8080/ss/p1"/>
</wsdl:port>
</wsdl:service>
<wsp:Policy wsu:Id="p1">
<sp:AsymmetricBinding>
<wsp:Policy>
<sp:InitiatorToken>
<wsp:Policy>
<sp:X509Token sp:IncludeToken="http://schemas.xmlsoap.org/ws/2005/12/securitypolicy/IncludeToken/AlwaysToRecipient">
<wsp:Policy>
<sp:WssX509V3Token10/>
</wsp:Policy>
</sp:X509Token>
</wsp:Policy>
</sp:InitiatorToken>
<sp:RecipientToken>
<wsp:Policy>
<sp:X509Token sp:IncludeToken="http://schemas.xmlsoap.org/ws/2005/12/securitypolicy/IncludeToken/Never">
<wsp:Policy>
<sp:WssX509V3Token10/>
</wsp:Policy>
</sp:X509Token>
</wsp:Policy>
</sp:RecipientToken>
<sp:AlgorithmSuite>
<wsp:Policy>
<sp:TripleDesRsa15/>
</wsp:Policy>
</sp:AlgorithmSuite>
</wsp:Policy>
</sp:AsymmetricBinding>
<sp:Wss10>
<wsp:Policy>
<sp:MustSupportRefEmbeddedToken/>
<sp:MustSupportRefIssuerSerial/>
</wsp:Policy>
</sp:Wss10>
<sp:SignedParts>
<sp:Body/>
</sp:SignedParts>
<sp:EncryptedParts>
<sp:Body/>
</sp:EncryptedParts>
<sp:EncryptedElements>
<sp:XPath>
//*[local-name()='Signature']
</sp:XPath>
</sp:EncryptedElements>
<sp:SignedSupportingTokens>
<wsp:Policy>
<sp:UsernameToken sp:IncludeToken="http://schemas.xmlsoap.org/ws/2005/12/securitypolicy/IncludeToken/AlwaysToRecipient"/>
</wsp:Policy>
</sp:SignedSupportingTokens>
</wsp:Policy>
</wsdl:definitions>

Answers

  • 800151
    800151 Member Posts: 23
    I think you are asking this question not only on the wrong section but also on the wrong website.

    The error you are refering to is a Axis2 specific exception, you might get the best answer by posting your question to the Axis2 mailing list:
    http://axis.apache.org/axis2/java/core/mail-lists.html

    BTW your exception "java.lang.UnsupportedOperationException: TODO"
    => looks like you have some comment left over in your Web-Service invokation. Actually your WSDL has no Method "TODO" so where should this call route to? I guess you should debug your code that invokes the call. Is there really a method TODO.
    I am also a bit confused with "Client Side WSDL" actually only the server does create a WSDL file, client only reads it (maybe you have some code generator that uses the WSDL to generate some code .. but the client has no WSDL).

    Further you should post a complete working example that can be run by somebody else, espacially with such a specific problem. Otherwise I am afraid hardly anybody will push you to the right direction.

    Sebastian
This discussion has been closed.