Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7079481
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 28, 20262026-05-28T06:40:39+00:00 2026-05-28T06:40:39+00:00

I have a web service client using axis. It’s using document/literal style and supposed

  • 0

I have a web service client using axis. It’s using document/literal style and supposed to have void response however the server insists on sending header response inside of soap body as following

<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
    <SOAP-ENV:Body>
        <SOAP-ENV:Code>
            <SOAP-ENV:Value>HTTP/1.1 200 OK</SOAP-ENV:Value>
        </SOAP-ENV:Code>
    </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

And of course client is raising deserializer exception as following

AxisFault
 faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
 faultSubcode: 
 faultString: org.xml.sax.SAXException: SimpleDeserializer encountered a child element, which is NOT expected, in something it was trying to deserialize.
 faultActor: 
 faultNode: 
 faultDetail: 
    {http://xml.apache.org/axis/}stackTrace:org.xml.sax.SAXException: SimpleDeserializer encountered a child element, which is NOT expected, in something it was trying to deserialize.
    at org.apache.axis.encoding.ser.SimpleDeserializer.onStartChild(SimpleDeserializer.java:145)
    at org.apache.axis.encoding.DeserializationContext.startElement(DeserializationContext.java:1035)
    at org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:165)
    at org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java:1141)
    at org.apache.axis.message.RPCElement.deserialize(RPCElement.java:236)
    at org.apache.axis.message.RPCElement.getParams(RPCElement.java:384)
    at org.apache.axis.client.Call.invoke(Call.java:2467)
    at org.apache.axis.client.Call.invoke(Call.java:2366)
    at org.apache.axis.client.Call.invoke(Call.java:1812)

Is there a way to bypass this exception instead of using invokeOneWay function (which is not a good way I suppose)?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-28T06:40:40+00:00Added an answer on May 28, 2026 at 6:40 am

    Solved it by adding output messages to service.

    <xsd:element name="Code" type="codeDT" />
    <xsd:complexType name="codeDT">
        <xsd:sequence>
            <xsd:any />
        </xsd:sequence>
    </xsd:complexType>
    ...
    <wsdl:message name="Code">
        <wsdl:documentation />
        <wsdl:part name="Code" element="p1:Code" />
    </wsdl:message>
    

    Just changing return type AXIS_VOID to SOAP_ELEMENT inside stub works fine but oh well; this way I can get what’s inside of value tag even though I don’t need it.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have implemented a web service with server and client authentication using keytool. The
I have a Java web service client running on Linux (using Axis 1.4) that
I have a .NET web-service client that has been autogenerated from a wsdl-file using
I have a Java client that calls a web service at the moment using
I have no experience with web services. Historically I've built client-server systems using proprietary
I have hard times using maven to generate my web service client. So please
I'm using a .NET 2.0 Client to communicate with an AXIS Web service. The
I have a RESTful web service and a rich client application using it. I
I have a web service written in C# using SOAP. A client has requested
I have a web reference to web-service: using (var client = new GetTemplateParamSoapClient(GetTemplateParamSoap)) {

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.