WebService SOAP response problems

hey,
I'm developing a WebService, using EJB's. I have a session bean, which has several methods. One of them returns, say, a class like follows:
class TeamDTO implements Serializable {
private String name;
private Integer teamId;
//getters and setters ..
I have several such methods returning various, very similar, classes. Now the problem is, when I try to test my application in the Web Services Navigator the response NEVER contains all the fields I wish. Why is that? Example of a response:
<SOAP-ENV:Envelope ...>
<SOAP-ENV:Body>
  <rpl:getAllTeamsResponse  ... >
   <rpl:Response ...>
    <pns:TeamDTO>
     <pns:name>team0</pns:name>
    </pns:TeamDTO>
   </rpl:Response>
  </rpl:getAllTeamsResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
But the TeamDTO class has apart from a name field an teamId field as well. What happened?! The same happens to other classes, but there's no rule about the missing column (first I thought it's the PK, like in the above example, but that's not the case).
What am I doing wrong? Ah, the fields are definetely not null, since in the above case it's a PK.
regards,
Kornel

Hey,
thanks for your hint, but that's not the problem here - for the example I've posted above java.lang.Integer won't appear, and for another case java.lang.String (whereas in my example String appeared). I'm sure the problem is somewhere else.. What happens if the field is null, will the appropriate tag appear in the soap response?
regards,
Kornel

Similar Messages

  • Synchronous RFC -- SOAP Scenario: problem with SOAP Response/Fault Mapping

    Hi,
    I've a synchronous RFC --> PI --> SOAP Scenario. The problem is that the message structure of the sending RFC doesn't match the Webservice Structure.
    The (SAP standard) RFC has just a Request / Response message structure. Part of the Response Message structure is a exception structure.
    The Webservice has a Request / Response message structure and in case of an error I get a SOAP:Fault.
    Problem now is that I cannot configure that scenario without usage of BPM as I will have to map SOAP:Response or SOAP:Fault to the RFC Response structure.
    Has anybody another idea to do that synchronous scenario (with usage of message mapping) without BPM?
    BR
    Holger

    1)
    you maus define 3 mapping.
    1)request
    2)response
    3)Fault
    in Interface mapping define at response boths (2-3) mapping. its clear??
    2)
    otherwise sometjhing is not clear, why do you want fault?? why dont you  get only response message. we implement this kind of response:
    <response_MT>
    <ID> (error ID)
    <system> (target system) 
    <error> (Error Description)
    </response>
    by this way fault message is not needed. but if you must have it just follow the top of message else, propose second.
    Thanks
    Rodrigo
    Thanks
    Rodrigo
    Edited by: Rodrigo Pertierra on Feb 25, 2008 11:52 AM

  • Xsl/stylesheet transformation problem in soap response(usinf xmlx-tags.tld)

    Hi,
    I have problem in transforming the soap response using xmlx-tags.tld.....
    I was not able to read the <EmpName> value from the returned xml...
    The stylesheet / xsl does not return any elements if I use other then "/" in match
    attribute : <xsl:template match="/">
    here is my soap call and stylesheet in JSP:
    <x:xslt media="html">
    <x:xml>
    <ws:soap ttl="360000">
    <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
    <soap:Body>
    ... making soap call here...
    </soap:Body>
    </soap:Envelope>
    </ws:soap>
    </x:xml>
    <x:stylesheet media="html">
    <xsl:stylesheet version='1.0' xmlns:xsl='http://www.w3.org/1999/XSL/Transform'>
    <xsl:output method="xmll" omit-xml-declaration="no"
    doctype-public="-//W3C//DTD HTML 4.0 Transitional//EN" indent="yes" />
    <xsl:template match="GetEmpResult">
    <html>
    <body>
    Result: <B>Symbol <xsl:value-of select="EmpName"/></B>
    </body
    </html>
    </xsl:stylesheet>
    </x:stylesheet>
    </x:xslt>
    the SOAP response looks like this:
    <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
    <soap:Body>
    <GetEmpResponse xmlns="http://ws.cdyne.com/">
    <GetEmpResult>
    <EmpID>string</EmpID>
    <EmpName>string</EmpName>
    <SalAmount>decimal</SalAmount>
    <Error>boolean</Error>
    </GetEmpResult>
    </GetEmpResponse>
    </soap:Body>
    </soap:Envelope>
    I tried all the possibilities of template matches, but not succeeded....
    Can somebody help me the correct <xsl:template> to access EmpName from the above
    SOAP responses...
    regards
    Vijay

    Hi,
    Dynamic xslt are not quite supported in OSB, there are some approaches that may be helpful for your case though...
    Have a look at these...
    http://atheek.wordpress.com/2011/12/21/using-xalanevaluate-to-parametrize-xpath/
    http://beatechnologies.wordpress.com/2010/12/01/dynamic-xquery-in-oracle-service-bus/
    Let me know how you go...
    Cheers,
    Vlad

  • SOAP Response Unmarshal Problem

    I am using the SOAP Proxy Generator to generate stubs from a WSDL file.  This part is okay. 
    When I use a method in the stub, the runtime generates an exception -- "null".  Yes that all it says.  I have verified that there is a SOAP response. You can find the actual response text below.
    I have traced the problem to the following statement in the generated stub:
    <i>perm.unmarshal((SOAPElementImpl) result, container);</i>
    Does anyone know if this SOAP response is something that the SOAP client SDK can support?
    <?xml version="1.0" encoding="utf-8"?>
    <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns5="http://www.themindelectric.com/package/com.esri.is.services.glue.v2.mapimage/" xmlns:ns6="http://www.themindelectric.com/package/com.esri.is.services.common.v2.geom/">
    <soap:Body>
    <n:getMapResponse xmlns:n="http://arcweb.esri.com/v2">
    <Result href="#id0"/>
    </n:getMapResponse>
    <id0 id="id0" soapenc:root="0" xsi:type="ns5:MapImageInfo">
    <mapUrl xsi:type="xsd:string">http://redlandsarcweb.esri.com/out/maps/GDT_ArcWeb_US_mangomap1735235894.jpg</mapUrl>
    <legendUrl xsi:type="xsd:string">http://redlandsarcweb.esri.com/out/maps/GDT_ArcWeb_US_mangomap1735235895.jpg</legendUrl>
    <mapExtent href="#id1"/></id0>
    <id1 id="id1" soapenc:root="0" xsi:type="ns6:Envelope">
    <minx xsi:type="xsd:double">-127.666666666666</minx>
    <miny xsi:type="xsd:double">20.0000000000001</miny>
    <maxx xsi:type="xsd:double">-106.333333333333</maxx>
    <maxy xsi:type="xsd:double">35.9999999999999</maxy>
    </id1>
    </soap:Body>
    </soap:Envelope>

    I'm afraid the response I incuded earlier in this forum is a "touched" version.  I got it by using the response object in the generated stub.
    I spoke to the developers of the web service and the response should look like:
    <n:getMapResponse xmlns:n='http://arcweb.esri.com/v2' xmlns:ns1='http://www.themindelectric.com/package/com.esri.is.services.glue.v2.mapimage/' xmlns:ns2='http://www.themindelectric.com/package/com.esri.is.services.common.v2.geom/'>
    <Result id='id0' xsi:type='ns1:MapImageInfo'>
         <mapUrl
    xsi:type='xsd:string'>http://redlandsarcweb.esri.com/out/maps/GDT_ArcWeb_US_
    blackmap606135221.png
         </mapUrl>
         <legendUrl xsi:type='xsd:string'></legendUrl>
         <mapExtent id='id1' xsi:type='ns2:Envelope'>
              <minx xsi:type='xsd:double'>-117.256667</minx>
              <miny xsi:type='xsd:double'>33.980556</miny>
              <maxx xsi:type='xsd:double'>-117.106667</maxx>
              <maxy xsi:type='xsd:double'>34.1305559999999</maxy>
         </mapExtent>
    </Result>
    </n:getMapResponse>
    Is there a way to get the "actual" SOAP response that was received direct from the web service?  What is the official debugging method?

  • SOAP Response Message Format for APEX Webservice

    Hi,
    Can anyone from Oracle post it here about the exact format of the response message from webservice in order to build a report on top of this?
    I have this format which is not working
    <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <SOAP-ENV:Body>
    <getRecordsResponse xmlns="http://www.service-now.com/incident">
    <getRecordsResult>
    <active>0</active>
    <activity_due/>
    <approval>not requested</approval>
    <approval_set/>
    <assigned_to>f298d2d2c611227b0106c6be7f154bc8</assigned_to>
    <assignment_group/>
    <business_duration>1970-01-01 00:00:00</business_duration>
    <business_stc>0</business_stc>
    <impact>3</impact>
    <incident_state>7</incident_state>
    <knowledge>0</knowledge>
    <location/>
    <made_sla>1</made_sla>
    <notify>1</notify>
    <number>INC0000060</number>
    <opened_at>2012-06-15 04:14:15</opened_at>
    <opened_by>glide.maint</opened_by>
    <order>0</order>
    <parent/>
    <parent_incident/>
    <priority>4</priority>
    <problem_id/>
    <reassignment_count>0</reassignment_count>
    <reopen_count>0</reopen_count>
    <resolved_at/>
    <resolved_by/>
    <rfc/>
    <severity>3</severity>
    <short_description>Computer running slow</short_description>
    </getRecordsResult>
    </getRecordsResponse>
    </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
    But below format is working.
    <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <SOAP-ENV:Body>
    <getRecordsResponse xmlns:tns1="http://www.service-now.com/incident">
    <tns1:getRecordsResult>
    <tns1:active>0</active>
    <tns1:activity_due/>
    <tns1:approval>not requested</approval>
    <tns1:approval_set/>
    <tns1:assigned_to>f298d2d2c611227b0106c6be7f154bc8</assigned_to>
    <tns1:assignment_group/>
    <tns1:business_duration>1970-01-01 00:00:00</business_duration>
    <tns1:business_stc>0</business_stc>
    <tns1:impact>3</impact>
    <tns1:incident_state>7</incident_state>
    <tns1:knowledge>0</knowledge>
    <tns1:location/>
    <tns1:made_sla>1</made_sla>
    <tns1:notify>1</notify>
    <tns1:number>INC0000060</number>
    <tns1:opened_at>2012-06-15 04:14:15</opened_at>
    <tns1:opened_by>glide.maint</opened_by>
    <tns1:order>0</order>
    <tns1:parent/>
    <tns1:parent_incident/>
    <tns1:priority>4</priority>
    <tns1:problem_id/>
    <tns1:reassignment_count>0</reassignment_count>
    <tns1:reopen_count>0</reopen_count>
    <tns1:resolved_at/>
    <tns1:resolved_by/>
    <tns1:rfc/>
    <tns1:severity>3</severity>
    <tns1:short_description>Computer running slow</short_description>
    </tns1:getRecordsResult>
    </getRecordsResponse>
    </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
    Please let us know so that can work with third parties to integrate webservices
    Thanks,
    Mehabub

    Here is the query that apex is using to extract the individual element
    select extractValue(value(t),'/*/number','xmlns="http://www.service-now.com/incident"') "number"
    , extractValue(value(t),'/*/severity','xmlns="http://www.service-now.com/incident"') "severity"
    from wwv_flow_collections c,
    table(xmlsequence(extract(c.xmltype001,'//getRecordsResponse/getRecordsResult','xmlns="http://www.service-now.com/incident"'))) t
    where c.collection_name = 'P_RESULTS21'FYI, that extraction method is deprecated starting with 11.2, though APEX still uses it for backward compatibility.
    That query works when applied on the first SOAP response you posted :
    SQL> select extractValue(value(t),'/*/number','xmlns="http://www.service-now.com/incident"') "number"
      2       , extractValue(value(t),'/*/severity','xmlns="http://www.service-now.com/incident"') "severity"
      3  from wwv_flow_collections c,
      4       table(
      5         xmlsequence(
      6           extract(c.xmltype001,'//getRecordsResponse/getRecordsResult','xmlns="http://www.service-now.com/incident"')
      7         )
      8       ) t
      9  where c.collection_name = 'P_RESULTS21';
    number                   severity
    INC0000060               3
    The second SOAP response is not even well-formed so I doubt the query works on it as you claim it does :
    <tns1:active>0</active>
    ...

  • SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPT

    Hi there,
    I am trying to publish a file from SAP as web service using XI and SOAP Adapter.
    I am using ABAP proxy to get the data into XI.
    Designing and Configuration in XI has no problems because when i use File adapter the data is trasmitted to FTP server.
    But when I used SOAP Reciever adapter I am getting following error in RWB
    Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Error during parsing of SOAP header.
    <b>Scenario</b>: SAP ABAP Proxy -> XI -> WebService. Asynchronous.
    <b>SOAP</b> Receiver adaptor.
    <b>Target URL</b> http://<host>:<port number >/sap/xi/engine?type=entry&version=3.0&Sender.Service=SAPDC2653&Interface=urn:bzttest:00:hsa:test%5EOB_MI_BZT_TEST&QualityOfService=ExactlyOnce
    Do not use SOAP Envelop is checked.
    <b>SOAP Action</b> http://sap.com/xi/WebService/soap1.1
    What i am missing here? How should I solve this problem?
    Any help is appreciated,
    Thx,
    Yogi

    Say there's a bapi/rfc that you want to call on an R/3 backend (e.g. 4.6c).  On it's own, the R/3 system cannot expose the rfc/bapi as a web service, but XI can.  So in this case, the scenario would be:
    WS client -> XI -> R/3
    When XI "exposes" a web service, it is exposing a service for a receiving system (in the above example, the R/3 system).  XI itself does not provide or contain the service implementation.  When XI exposes a web service, it is always done via the <b>sender</b> soap adapter (i.e. if soap adapter is used).   Receiver soap adapter is used to call or consume an actual web service from an external application.
    Regards,
    Jin

  • Soap response with envelope

    Hi
    My PI server is able to make a soap call to the SFDC ( webservice ) ...however the response that is received within PI
    has a SOAP envelope...and hence the response mapping is going in error....because the source data type in response mapping doesnot match with the soap response ( with envelope )
      <?xml version="1.0" encoding="UTF-8" ?>
    - <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns="urn:enterprise.soap.sforce.com">
    - <soapenv:Body>
    - <upsertResponse>
    - <result>
      <created>false</created>
      <id>a0UT0000004aeaMMAQ</id>
      <success>true</success>
      </result>
      </upsertResponse>
      </soapenv:Body>
      </soapenv:Envelope>
    how do i handle this

    Hi,
    I think there is an option while configuration of SOAP adapter, where you can define, not to keep SOAP envelop. Please check the option Conversion Parameters\Do Not Use SOAP Envelope and set it as per your requirement. That might solve the problem. Here is the link which can be helpful
    http://help.sap.com/saphelp_nw04/helpdata/en/29/5bd93f130f9215e10000000a155106/content.htm
    Alternatively you need a java mapping or XSLT mapping to remove the envelop.
    Here is the java mapping code to remove SOAP envelop
    import java.io.FileInputStream;
    import java.io.FileOutputStream;
    import java.io.InputStream;
    import java.io.OutputStream;
    import java.util.Map;
    import javax.xml.parsers.DocumentBuilder;
    import javax.xml.parsers.DocumentBuilderFactory;
    import javax.xml.transform.Transformer;
    import javax.xml.transform.TransformerFactory;
    import javax.xml.transform.dom.DOMSource;
    import javax.xml.transform.stream.StreamResult;
    import org.w3c.dom.Document;
    import org.w3c.dom.Element;
    import org.w3c.dom.Node;
    import org.w3c.dom.NodeList;
    import com.sap.aii.mapping.api.StreamTransformation;
    import com.sap.aii.mapping.api.StreamTransformationException;
    public class RemoveSoapEnvelop implements StreamTransformation{
    public void execute(InputStream in, OutputStream out)
    throws StreamTransformationException {
    try
         DocumentBuilderFactory factory=DocumentBuilderFactory.newInstance();
         DocumentBuilder builderel=factory.newDocumentBuilder();
         /*input document in form of XML*/
         Document docIn=builderel.parse(in);
         /*document after parsing*/
         Document docOut=builderel.newDocument();
         TransformerFactory tf=TransformerFactory.newInstance();
         Transformer transform=tf.newTransformer();
         Element root;
         Node p;
         NodeList l;
         int mm,n1;
         //if you need to include namespace use next two lines
         //root=docOut.createElement("ns0:upsertResponse");
         //root.setAttribute("xmlns:ns0","http://connectsystems.be/MAINFR/AccDocument");
         root=docOut.createElement("upsertResponse");
         p=docIn.getElementsByTagName("upsertResponse").item(0);
         l=p.getChildNodes();
         n1=l.getLength();
         for(mm=0;mm<n1;++mm)
              Node temp=docOut.importNode(l.item(mm),true);
              root.appendChild(temp);
         docOut.appendChild(root);
         transform.transform(new DOMSource(docOut), new StreamResult(out));
    catch(Exception e)
         e.printStackTrace();
    public void setParameter(Map arg0) {
    public static void main(String[] args) {
    try{
         RemoveSoapEnvelop genFormat=new RemoveSoapEnvelop();
         FileInputStream in=new FileInputStream("C:\\Apps\\my folder\\sdn\\sd2.xml");
         FileOutputStream out=new FileOutputStream("C:\\Apps\\my folder\\sdn\\removedEnvelop.xml");
         genFormat.execute(in,out);
    catch(Exception e)
    e.printStackTrace();
    input xml file sd2.xml
      <?xml version="1.0" encoding="UTF-8" ?>
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns="urn:enterprise.soap.sforce.com">
    <soapenv:Body>
    <upsertResponse>
    <result>
      <created>false</created>
      <id>a0UT0000004aeaMMAQ</id>
      <success>true</success>
      </result>
      </upsertResponse>
      </soapenv:Body>
      </soapenv:Envelope>
    Here is the output xml removedEnvelop.xml
      <?xml version="1.0" encoding="UTF-8" ?>
    <upsertResponse>
    <result>
      <created>false</created>
      <id>a0UT0000004aeaMMAQ</id>
      <success>true</success>
      </result>
      </upsertResponse>
    Helpful articles on java mapping for PI 7.1
    http://wiki.sdn.sap.com/wiki/display/XI/SampleJAVAMappingcodeusingPI7.1+API
    You can also try following XSLT mapping to get the same output as java mapping
    <xsl:stylesheet version="1.0"
    xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
    exclude-result-prefixes="SOAP-ENV">
    <xsl:output method="xml" version="1.0" encoding="UTF-8" indent="yes" />
    <xsl:template match="/">
    <xsl:for-each select="SOAP-ENV:Envelope/SOAP-ENV:Body">     
    <upsertResponse>
    <result>
         <xsl:variable name="var" select="normalize-space(.)"></xsl:variable>
         <xsl:variable name="tokenizedSample" select="tokenize($var,' ')"/>
        <created><xsl:value-of select="$tokenizedSample[1]"/></created>
        <id><xsl:value-of select="$tokenizedSample[2]"/></id>
        <success><xsl:value-of select="$tokenizedSample[3]"/></success>
    </result>
    </upsertResponse>
    </xsl:for-each>
    </xsl:template>
    </xsl:stylesheet>
    Other than these please refer to following links for further examples on the topic
    Remove SOAP-ENV tags from xml RECEIVER RESPONSE payload (XSL needed?)
    Remove SOAP Envelop using XSLT  mapping.
    Hope this helps your cause.
    regards
    Anupam

  • Weblogic throwing "null SOAP element Exception" in multi-part SOAP response

    Hi All,
    I'm using weblogic 10. My application is a webservice client generated using '*clientgen*', which is running on weblogic, and
    is invoking a remotely hosted webservice ( Remotely hoseted webservice may not be running on weblogic).
    I've the wsdl file of remotely hosted webservice.
    Now the problem is with WSDL file (I suppose), have a look at this.
    *&lt;message name="m1"&gt;*
    *&lt;part name="body" element="tns:GetCompanyInfo"/&gt;*
    *&lt;/message&gt;*
    *&lt;message name="m2"&gt;*
    *&lt;part name="body" element="tns:GetCompanyInfoResult"/&gt;*
    *&lt;part name="docs" type="xsd:AnyComplexType"/&gt; ------&gt; assume all elements inside this complex type can be nil or minOccurs set to '0'*
    *&lt;part name="logo" type="xsd:AnyOtherComplexType"/&gt; ------&gt; assume all elements inside this complex type can be nil or minOccurs set to '0'*
    *&lt;/message&gt;*
    &lt;portType name="pt1"&gt;
    &lt;operation name="GetCompanyInfo"&gt;
    &lt;input message="m1"/&gt;
    *&lt;output message="m2"/&gt; -----&gt; multi part message.*
    &lt;/operation&gt;
    &lt;/portType&gt;
    Now here is sample message for the request(I've composed this message for this question):
    &lt;soap:Envelope&gt; MESSAGE1
    &lt;soap:header/&gt;
    &lt;soap:body&gt;
    &lt;tns:m2&gt;
    &lt;tns:GetCompanyInfoResult&gt;
    Blah Blah....
    &lt;/tns:GetCompanyInfoResult&gt;
    &lt;tns:docs&gt;
    Blah Blah....
    &lt;/tns:docs&gt; Assume no data for 'logo', so it's not returned. Since all its elements can be nillable.
    &lt;tns:m2&gt;
    &lt;/soap:body&gt;
    &lt;/soap:Envelope&gt;
    First of all, is this SOAP response is valid? I'm not sure about *'message' and 'parts' in SOAP*, but according to XML schema standards it's invalid.
    Because, according to *'message' m2, 'logo' is missing*, eventhough all it's elements are nillable in such case there should be *&lt;logo/&gt;* at the end.
    I mean valid message should be like below
    &lt;soap:Envelope&gt; '*MESSAGE2*'
    &lt;soap:header/&gt;
    &lt;soap:body&gt;
    &lt;tns:m2&gt;
    &lt;tns:GetCompanyInfoResult&gt;
    Blah Blah....
    &lt;/tns:GetCompanyInfoResult&gt;
    &lt;tns:docs&gt;
    Blah Blah....
    &lt;/tns:docs&gt;
    *&lt;tns:logo/&gt; ------------------&gt; here is the change compared to above message. empty element.*
    &lt;tns:m2&gt;
    &lt;/soap:body&gt;
    &lt;/soap:Envelope&gt;
    Now the concerns are :
    (1) Which is a valid response? Message1 or Message2
    (2) If message1 is valid then why is weblogic throwing an exception 'null SOAP element', I suppose this is due to missing 'logo' element.
    (To confirm this I've used tcpmonitor and found message1 as response but weblogic is still throwing 'null SOAP Element' exception,
    which confirms it needs 'logo' as well, I suppose &lt;logo/&gt; at least). Is there any workaround for this in weblogic for multi-part messages?
    (3) If message1 is invalid according to SOAP standards then You've answered my question. ---&gt; I need to talk to the webservice provider in this case.....
    Thanks in advance...

    Message 1 is not Basic Profile 1.1 compliant. It is specified by BP1.1 in section 4.4.1(http://www.ws-i.org/Profiles/BasicProfile-1.1-2004-08-24.html#Bindings_and_Parts) that when a wsdl:part element is defined using the type attribute, the serialization of that part in a message is equivalent to an implicit (XML Schema) qualification of a minOccurs attribute with the value "1", a maxOccurs attribute with the value "1" and a nillable attribute with the value "false".

  • Error when trying to read the SOAP Response

    Hai,
    iam trying to access the web service of DUBAI international Airport
    GetFlightSchedulebyDateRange at http://dca.gov.ae/WebServices/Flights
    This is my program
    package MyClient3;
    import java.io.FileOutputStream;
    import java.net.URL;
    import java.util.Iterator;
    import javax.xml.soap.MessageFactory;
    import javax.xml.soap.MimeHeaders;
    import javax.xml.soap.Name;
    import javax.xml.soap.SOAPBody;
    import javax.xml.soap.SOAPBodyElement;
    import javax.xml.soap.SOAPConnection;
    import javax.xml.soap.SOAPConnectionFactory;
    import javax.xml.soap.SOAPElement;
    import javax.xml.soap.SOAPEnvelope;
    import javax.xml.soap.SOAPFactory;
    import javax.xml.soap.SOAPFault;
    import javax.xml.soap.SOAPHeader;
    import javax.xml.soap.SOAPMessage;
    import javax.xml.soap.SOAPPart;
    public class Client3 {
    public static void main(String arg[]){
    try{
    MessageFactory factory = MessageFactory.newInstance();
    SOAPMessage message = factory.createMessage();
    SOAPPart soapPart = message.getSOAPPart();
    SOAPEnvelope envelope = soapPart.getEnvelope();
    SOAPHeader header = envelope.getHeader();
    SOAPBody body = envelope.getBody();
    // header.detachNode();
    SOAPFactory soapFactory = SOAPFactory.newInstance();
    Name bodyName = soapFactory.createName("GetFlightSchedulebyDateRange",null,"http://dca.gov.ae/WebServices/Flights");
    SOAPBodyElement bodyElement = body.addBodyElement(bodyName);
    Name name = soapFactory.createName("Todate");
    SOAPElement symbol = bodyElement.addChildElement(name);
    //symbol.addTextNode("2007-05-25T00:00:00.0000000+04:00");
    symbol.addTextNode("2007-05-27");
    name = soapFactory.createName("Fromdate");
    symbol = bodyElement.addChildElement(name);
    //symbol.addTextNode("2007-05-25T00:00:00.0000000+04:00");
    symbol.addTextNode("2007-05-27");
    MimeHeaders hd = message.getMimeHeaders();
    hd.addHeader("SOAPAction", "http://dca.gov.ae/WebServices/Flights/GetFlightSchedulebyDateRange");
    SOAPConnectionFactory soapConnectionFactory = SOAPConnectionFactory.newInstance();
    SOAPConnection connection = soapConnectionFactory.createConnection();
    message.writeTo(System.out);
    System.out.println();
    System.out.println(soapPart.toString());
    String endpoint = "http://dubaiairport.com/dcaflightinfo/fis/flights.asmx?WSDL";
    URL url = new URL(endpoint);
    SOAPMessage response = connection.call(message, url);
    response.writeTo(System.out);
    SOAPPart part = response.getSOAPPart();
    SOAPEnvelope env = part.getEnvelope();
    connection.close();
    System.out.println("\n\nIterating through the response object to get the values:\n\n");
    // SOAPBody se = response.getSOAPBody();
    }catch(Exception e){System.out.println("+++++++++++++++++++++++++"+e);}
    i am getting the error
    ERROR: 'Character reference "&#x1B" is an invalid XML character.
    in the statement
    SOAPEnvelope env = part.getEnvelope();
    can some help me to solve this problem, iam using JAX-WS 2.0, and netbeans

    I got the solution, there was a Invalid char in SOAP response message, i stored the SOAP res msg to a file, parsed that file to remove the invalid char , ans used the soap msg from the file,
    it worked perfectly fo me

  • SOAP Response cannot be decoded.

    Hello Everybody,
    I created a simple web service in asp.net using the c# sharp language. The web service extracts data from an MS SQL Database, translates that data in to xml, assigns the xml to a string varible and returns  the string varible to what ever called the service. I know the web service works becuase if you call it in a web browser at the following address http://www.jmmortimer.com/dataaccess/sqlhelper.asmx?wsdl, it will show you the xml that represents web service. Plus, I tested it by calling it in an asp.net application. However when I call it from a Flex 3 application it gives me the following error message. SOAP Response cannot be decoded. Raw response: " faultCode="DecodingError" faultDetail="null" The code that I have in Flex 3 is below. If anyone knows how to solve this problem, please let me know. Thanks in advance.
    <?xml version="1.0" encoding="utf-8"?>
    <mx:Application 
    xmlns:mx=http://www.adobe.com/2006/mxml layout="absolute">
    <mx:Script>
    <![CDATA[
    import mx.rpc.soap.LoadEvent;
    import mx.rpc.events.ResultEvent;
    private function getData(evt:LoadEvent):void
    var connString:String = "Data Source=Family\SQLExpress;Initial Catalog=SDJames;User ID=sa;Password=Password1";
    var storedProc:String = "GetAuxiliaries";
    myService.GetDataTable(connString, storedProc)
    private function resultHandler(evt:ResultEvent):void
    test.text = String(evt.result);
    ]]> 
    </mx:Script>
    <mx:WebService id="myService" wsdl="http://jmmortimer.com/dataaccess/sqlhelper.asmx?WSDL"
    load="getData(event)" result="resultHandler(event)" />
    <mx:TextArea id="test" x="10" y="10" width="452" height="348"/>
    </mx:Application>

    Hello Again Everybody,
    I have found the answer to my problem. The Problem was that I had the wrong value assigned the variable "connString" insted of  "Data Source=Family\SQLExpress;Initial Catalog=SDJames;User ID=sa;Password=Password1", it should have been "Data Source=Family\\SQLExpress;Initial Catalog=SDJames;User ID=sa;Password=Password1". Don't you just hate how just  messing up with one character can mess up you entire application. Thanks to everybody who took time to look over my problem.
    God Bless

  • Error Reading Soap Response

    Hi,
    We are having a problem reading Soap Response:
    Scenario: From XI/PI we are calling a webservice with Synchronous
    message with WS-Security including Authentication, Signature, TimeStamp
    and Encryption using SOAP Receiver Adapter. We are able to send the
    request successfully and also the webServer is able to understand the
    request and sending the response back. The problem is the PI is unable
    to read the response and giving a below error:
    com.sap.aii.af.ra.ms.api.DeliveryException: expecting end tag:
    Transform, but found
    InclusiveNamespaces at state 1
    We tested successfully end-end with NON-Secured sites with out WS-
    Security.
    Please let me know if you have seen this error or any thoughts.
    Thanks,
    Laxman
    This is the actual Request Message:
      <?xml version="1.0" encoding="UTF-8" ?>
              <ns0:getUser xmlns:ns0="http://csa -namespace:8090/ddsssaws/IdentityManagementService">
      <string>XYZ123</string>
      </ns0:getUser>
    Also we extracted raw traffic using TCPMon:
    Below is the raw-traffic of SOAP adapter (used TCPGateway to capture the traffic)
    Request:
    POST /edsssaws/IdentityManagement HTTP/1.0
    Accept: /
    Host: 999.97.19.45:9999
    User-Agent: SAP-Messaging-com.sap.aii.messaging/1.0505
    Content-ID: <soap-1f3af770018111ddc0d300144f2515b0Atsap.com>
    Content-Disposition: attachment;filename="soap-1f3af770018111ddc0d300144f2515b0Atsap.com.xml"
    Content-Type: text/xml; charset=utf-8
    Content-Description: SOAP
    Content-Length: 5530
    SOAPACTION:
    <SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'><SOAP:Header><wsse:Security xmlns:wsse='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd' SOAP:mustUnderstand='1'><wsse:BinarySecurityToken xmlns:wsu='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd' wsu:Id='sap-9' ValueType='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3' EncodingType='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary'>MIIFFTCCBH6gAwIBAgIKZptrmQABAAALBTANBgkqhkiG9w0BAQUFADByMRMwEQYKCZImiZPyLGQBGRYDY29tMRMwEQYKCZImiZPyLGQBGRYDZWRzMRQwEgYKCZImiZPyLGQBGRYEY29ycDEUMBIGCgmSJomT8ixkARkWBGFtZXIxGjAYBgNVBAMTEUVEUyBFbnRlcnByaXNlQ0ExMB4XDTA4MDQwMTIxMjMyN1oXDTEwMDQwMTIxMjMyN1owIjELMAkGA1UEBhMCVVMxEzARBgNVBAMTCklUQVBJTlRERVYwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALjKvScjIEmp5Q1X3/gfR0WZO22KiEAOAx9kM0q3kpT/0dk2ZVit5YCBT4Zkt6Tttyh21xmnCcVgcRo0YOxXcXrLq25HRsSbxY3Zu37qq4tqExX5gQCtfR1pRjRrhQfDPmPGzFOrTzSjxJ5BH49p3KZcUhj7KpWQEakDBvJAgMBAAGjggMAMIIC/DAdBgNVHQ4EFgQUadHS0gj0CBQymaNnAlGJphSCB/YwHwYDVR0jBBgwFoAULNVTI/CtjM0k4MlzJLuQI4tVUy8wggEaBgNVHR8EggERMIIBDTCCAQmgggEFoIIBAYaBxWxkYXA6Ly8vQ049RURTJTIwRW50ZXJwcmlzZUNBMSgxKSxDTj11c3Bsc3NjYTAwMixDTj1DRFAsQ049UHVibGljJTIwS2V5JTIwU2VydmljZXMsQ049U2VydmljZXMsQ049Q29uZmlndXJhdGlvbixEQz1jb3JwLERDPWVkcyxEQz1jb20/Y2VydGlmaWNhdGVSZXZvY2F0aW9uTGlzdD9iYXNlP29iamVjdENsYXNzPWNSTERpc3RyaWJ1dGlvblBvaW50hjdodHRwOi8vd3d3LmVkcy5jb20vY3J0cmV2bHN0L0VEUyUyMEVudGVycHJpc2VDQTEoMSkuY3JsMIIBDwYIKwYBBQUHAQEEggEBMIHMIG2BggrBgEFBQcwAoaBqWxkYXA6Ly8vQ049RURTJTIwRW50ZXJwcmlzZUNBMSxDTj1BSUEsQ049UHVibGljJTIwS2V5JTIwU2VydmljZXMsQ049U2VydmljZXMsQ049Q29uZmlndXJhdGlvbixEQz1jb3JwLERDPWVkcyxEQz1jb20/Y0FDZXJ0aWZpY2F0ZT9iYXNlP29iamVjdENsYXNzPWNlcnRpZmljYXRpb25BdXRob3JpdHkwQwYIKwYBBQUHMAKGN2h0dHA6Ly93d3cuZWRzLmNvbS9jcnRyZXZsc3QvRURTJTIwRW50ZXJwcmlzZUNBMSgxKS5jcnQwDAYDVR0TAQH/BAIwADALBgNVHQ8EBAMCBLAwPAYJKwYBBAGCNxUHBC8wLQYlKwYBBAGCNxUIh4qV4WN/hPFkRuHwclug63SWS2GpOIihPT8LwIBZAIBBDATBgNVHSUEDDAKBggrBgEFBQcDATAbBgkrBgEEAYI3FQoEDjAMMAoGCCsGAQUFBwMBMA0GCSqGSIb3DQEBBQUAA4GBAGzyuh56APinQtmE9oWsT8NHcQqMASHZnN26RAofnxuIUH1VyBK2CGyiiDnCS0cDIGBl45sqOO8uRClE7CngeZEAV9JL5bhpUF6rywmFKvqe5FyqnrScczeaODV0g9sO4vUrwdGlReA5ncvtSN/u82MWDqtHAHBfpYQxZUrW</wsse:BinarySecurityToken><wsu:Timestamp xmlns:wsu='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd' wsu:Id='wsu-targetID-1f10b320-0181-11dd-aebd-00144f2515b0'><wsu:Created ValueType='xsd:dateTime'>2008-04-03T13:23:17Z</wsu:Created><wsu:Expires ValueType='xsd:dateTime'>2008-04-03T13:25:17Z</wsu:Expires></wsu:Timestamp><xenc:EncryptedKey xmlns:xenc='http://www.w3.org/2001/04/xmlenc#' Id='EK52789332'><xenc:EncryptionMethod Algorithm='http://www.w3.org/2001/04/xmlenc#rsa-1_5'/><ds:KeyInfo xmlns:ds='http://www.w3.org/2000/09/xmldsig#'><wsse:SecurityTokenReference><wsse:KeyIdentifier ValueType='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509SubjectKeyIdentifier' EncodingType='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary'>ykCivrkfwQdj30aJid9VGnjtY=</wsse:KeyIdentifier></wsse:SecurityTokenReference></ds:KeyInfo><xenc:CipherData><xenc:CipherValue>Fi5B3uBMSp4nAKh3rLAs4DJQ5iCLoupE1oq3VOFueea1Y90xI200OFraV2mRS2ywsejH36nwy
    XYPuB5ZQScJampqZDtTR28cq890s4sEKFpycsNyNM9VScWaVoi4nKBKRIdGVoLgLf+NrmzJnXD
    6eb4F6tWWyw8g2FJel4=</xenc:CipherValue></xenc:CipherData><xenc:ReferenceList><xenc:DataReference URI='#ED13608949'/></xenc:ReferenceList></xenc:EncryptedKey><ds:Signature xmlns:ds='http://www.w3.org/2000/09/xmldsig#'><ds:SignedInfo><ds:CanonicalizationMethod Algorithm='http://www.w3.org/2001/10/xml-exc-c14n#'/><ds:SignatureMethod Algorithm='http://www.w3.org/2000/09/xmldsig#rsa-sha1'/><ds:Reference URI='#wsuid-body-1f108c10-0181-11dd-838e-00144f2515b0'><ds:Transforms><ds:Transform Algorithm='http://www.w3.org/2001/10/xml-exc-c14n#'/></ds:Transforms><ds:DigestMethod Algorithm='http://www.w3.org/2000/09/xmldsig#sha1'/><ds:DigestValue>UaW58GCrg/nrA/EfW+OyHP2DCio=</ds:DigestValue></ds:Reference><ds:Reference URI='#wsu-targetID-1f10b320-0181-11dd-aebd-00144f2515b0'><ds:Transforms><ds:Transform Algorithm='http://www.w3.org/2001/10/xml-exc-c14n#'/></ds:Transforms><ds:DigestMethod Algorithm='http://www.w3.org/2000/09/xmldsig#sha1'/><ds:DigestValue>LFuszgJ412Fe8PRtK3W69RTXndY=</ds:DigestValue></ds:Reference></ds:SignedInfo><ds:SignatureValue>K4iZoVGhuI41fj9BdXx7wUz/JEi2pqh60gZZta8tOfaVmC1PfNtPg61N0sYescfM4RmkQpDorS1d
    VB/DAJKz173HTD5rn/SuwmYgql4aVKPNlIDD90ZXoJ/mfzwT/Kei6yjWtvCYthCxaUtP/LFDB/dA
    mr1OUAj9X2DHkzF6g=</ds:SignatureValue><ds:KeyInfo><wsse:SecurityTokenReference><wsse:Reference URI='#sap-9'/></wsse:SecurityTokenReference></ds:KeyInfo></ds:Signature></wsse:Security></SOAP:Header><SOAP:Body xmlns:wsu='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd' wsu:Id='wsuid-body-1f108c10-0181-11dd-838e-00144f2515b0'><xenc:EncryptedData xmlns:xenc='http://www.w3.org/2001/04/xmlenc#' Type='http://www.w3.org/2001/04/xmlenc#Content' Id='ED13608949'><xenc:EncryptionMethod Algorithm='http://www.w3.org/2001/04/xmlenc#tripledes-cbc'/><xenc:CipherData><xenc:CipherValue>lZkC7zZZfqBUg5rnqMZypi5ZvnPBvw36fjeFmCDQ5DMDjKXShO4apBjBE3gUsLGL1TMli18D0NWK
    dmVHQTePitGhvQ7YiyaXgjekZckS2P91Qv/9Zut5/hzCYhgVarnUgGmr8Qi4aSYXCY0oBD6SzVXy
    /UoQHPASF3mhYPaFBtmTJu2dHmV6v4HTKC+Om0</xenc:CipherValue></xenc:CipherData></xenc:EncryptedData></SOAP:Body></SOAP:Envelope>
    Response:
    HTTP/1.1 200 OK
    Date: Thu, 03 Apr 2008 13:23:54 GMT
    Content-Length: 9511
    Content-Type: text/xml
    Set-Cookie: JSESSIONID=cTPmH0hKYvKqK427JJb573FT1RWZhHY5l7XnLlsjsk6yRkS2g5y6!1973031667; path=/
    Connection: close
    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><env:Header><wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" env:mustUnderstand="1"><xenc:EncryptedKey xmlns:xenc="http://www.w3.org/2001/04/xmlenc#"><xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#rsa-1_5"></xenc:EncryptionMethod><dsig:KeyInfo xmlns:dsig="http://www.w3.org/2000/09/xmldsig#"><wsse:SecurityTokenReference><wsse:KeyIdentifier xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509SubjectKeyIdentifier" wsu:Id="Id-dgdMMmsGkjae8aSYF_59_xwe" EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary">adHS0gj0CBQymaNnAlGJphSCB/Y=</wsse:KeyIdentifier></wsse:SecurityTokenReference></dsig:KeyInfo><xenc:CipherData><xenc:CipherValue>mbOmTXSiYuEiWHbP3dbrDXFpZaSoQ084wMBt7uRxNo49p1fpQBkDpr/H2wPNbHy4qzSTVzP7EESzWFjFEb/7BH3dt4JuyzBFH1M0X77YBW5YHNGpiUmj934ziydojqcU6jWBsUaFxXsAPmvy0q3vVk8xnZcQHxMNhPS5ebK9o=</xenc:CipherValue></xenc:CipherData><xenc:ReferenceList><xenc:DataReference URI="#Id-yMgwZrtQctSvW1mT1sDWdZ8D"></xenc:DataReference></xenc:ReferenceList></xenc:EncryptedKey><wsse:BinarySecurityToken xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3" wsu:Id="Id-2DXBQHwdRE0oquWQV0mjtw1U" EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary">MIIFVjCCBLgAwIBAgIKfps5MgABAAADHjANBgkqhkiG9w0BAQUFADByMRMwEQYKCZImiZPyLGQBGRYDY29tMRMwEQYKCZImiZPyLGQBGRYDZWRzMRQwEgYKCZImiZPyLGQBGRYEY29ycDEUMBIGCgmSJomT8ixkARkWBGFtZXIxGjAYBgNVBAMTEUVEUyBFbnRlcnByaXNlQ0ExMB4XDTA2MDUyMzIzMDY0OVoXDTA4MDUyMjIzMDY0OVowYzELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAlRYMQ4wDAYDVQQHEwVQbGFubzEMMAoGA1UEChMDRURTMQwwCgYDVQQLEwNTRFMxGzAZBgNVBAMTElNTQVdlYlNlcnZpY2VzLURFVjCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEA0qRmvQkxnPnEZQNSabPVwM6sEf8vFUOAlgQ9uuiDImVmDw4Afg45zbmTBeDdv4wsIap7kI4VJhv60SdOQg6i1mIEi83Qk7UJYD8XvKuOalSLYhHu92lsp0kIZlAdzipVd1Pp0cI3wSvP6o9zfX0gALpisf8rGJ1CkVWbtHaVp0CAwEAAaOCAwAwggL8MB0GA1UdDgQWBBTKT4KKuR/7BB2PfRomJ31UaeO1jAfBgNVHSMEGDAWgBQs1VMj8K2MzSTgyXMku5Aji1VTLzCCARoGA1UdHwSCAREwggENMIIBCaCCAQWgggEBhoHFbGRhcDovLy9DTj1FRFMlMjBFbnRlcnByaXNlQ0ExKDEpLENOPXVzcGxzc2NhMDAyLENOPUNEUCxDTj1QdWJsaWMlMjBLZXklMjBTZXJ2aWNlcyxDTj1TZXJ2aWNlcyxDTj1Db25maWd1cmF0aW9uLERDPWNvcnAsREM9ZWRzLERDPWNvbT9jZXJ0aWZpY2F0ZVJldm9jYXRpb25MaXN0P2Jhc2U/b2JqZWN0Q2xhc3M9Y1JMRGlzdHJpYnV0aW9uUG9pbnSGN2h0dHA6Ly93d3cuZWRzLmNvbS9jcnRyZXZsc3QvRURTJTIwRW50ZXJwcmlzZUNBMSgxKS5jcmwwggEPBggrBgEFBQcBAQSCAQEwgf4wgbYGCCsGAQUFBzAChoGpbGRhcDovLy9DTj1FRFMlMjBFbnRlcnByaXNlQ0ExLENOPUFJQSxDTj1QdWJsaWMlMjBLZXklMjBTZXJ2aWNlcyxDTj1TZXJ2aWNlcyxDTj1Db25maWd1cmF0aW9uLERDPWNvcnAsREM9ZWRzLERDPWNvbT9jQUNlcnRpZmljYXRlP2Jhc2U/b2JqZWN0Q2xhc3M9Y2VydGlmaWNhdGlvbkF1dGhvcml0eTBDBggrBgEFBQcwAoY3aHR0cDovL3d3dy5lZHMuY29tL2NydHJldmxzdC9FRFMlMjBFbnRlcnByaXNlQ0ExKDEpLmNydDAMBgNVHRMBAf8EAjAAMAsGA1UdDwQEAwIEsDA8BgkrBgEEAYI3FQcELzAtBiUrBgEEAYI3FQiHir5XhY3E8WRG4fByW6DrdJZLYak4iKE9PwvAgFkAgEEMBMGA1UdJQQMMAoGCCsGAQUFBwMBMBsGCSsGAQQBgjcVCgQOMAwwCgYIKwYBBQUHAwEwDQYJKoZIhvcNAQEFBQADgYEALsVozc1aVcPNBVsRXRbAiStchxG2fKDOt9kRzL6BHtQa/fkp81EjOBhETn8N1IHLUsINn05wGgdDA2UszjLtRIpQmdpCyh2gzFW8Dlx5X7vJyvJsoDOPDBArv55dTjCEfok1oz3ux3mrVotuvr1pKIVTr7ylpRM8p8GBXw=</wsse:BinarySecurityToken><dsig:Signature xmlns:dsig="http://www.w3.org/2000/09/xmldsig#"><dsig:SignedInfo><dsig:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"></dsig:CanonicalizationMethod><dsig:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"></dsig:SignatureMethod><dsig:Reference URI="#Id-wS1xP_ArcYYXY4qkqYznI7_W"><dsig:Transforms><dsig:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"></dsig:Transform></dsig:Transforms><dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"></dsig:DigestMethod><dsig:DigestValue>tr3NrozQWsKrvH38naIEnQXrzgQ=</dsig:DigestValue></dsig:Reference><dsig:Reference URI="#Id-1vPAqVSMhSLH3WiBQkTTfldz"><dsig:Transforms><dsig:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"><c14n:InclusiveNamespaces xmlns:c14n="http://www.w3.org/2001/10/xml-exc-c14n#" PrefixList="xsd n1"></c14n:InclusiveNamespaces></dsig:Transform></dsig:Transforms><dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"></dsig:DigestMethod><dsig:DigestValue>AUWlqeyq6w5LQnggK5dT6flLUU=</dsig:DigestValue></dsig:Reference></dsig:SignedInfo><dsig:SignatureValue>Yx5Pre8VChTLOhPVln5xhO21dM93a2FPxQTsZY1BBIWlqeHkAEQqXvhI/EU459QZIGDOubLK0Z9AT0SRmDOgtnWNBT0duqveQ1Ippbd0hXaehW48ObrMIKnYfq5ub1kNYv9mslybPRZw9OaiijNmLfIty8qc8ctRV0lFwAjcQyk=</dsig:SignatureValue><dsig:KeyInfo><wsse:SecurityTokenReference><wsse:Reference URI="#Id-2DXBQHwdRE0oquWQV0mjtw1U"></wsse:Reference></wsse:SecurityTokenReference></dsig:KeyInfo></dsig:Signature><wsu:Timestamp xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="Id-wS1xP_ArcYYXY4qkqYznI7_W"><wsu:Created>2008-04-03T13:23:55.459Z</wsu:Created></wsu:Timestamp></wsse:Security></env:Header><env:Body xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" wsu:Id="Id-1vPAqVSMhSLH3WiBQkTTfldz"><xenc:EncryptedData xmlns:xenc="http://www.w3.org/2001/04/xmlenc#" Type="http://www.w3.org/2001/04/xmlenc#Content" Id="Id-yMgwZrtQctSvW1mT1sDWdZ8D"><xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#tripledes-cbc"></xenc:EncryptionMethod><xenc:CipherData><xenc:CipherValue>LB6IKwEJgvTPdPGNeIzcpjPjC9GXi3sou5PaCnF3m4x6ToA6gDV5Sw/ODnCEeqFURgWFX8ZgxYF9YJdyj7ERAifs8MNBh/rHCitT02mU8pirwGdqSXlfCX4KYsHtUnyiGKbbMCwvCCs4LgBPnx8tCN39aazA1Ge/5JPfwupYMU/lAbyajdP1qva/gxhMCqGkgAnQgB1TJDfARvDsJnx6p2zqKsnRnNreBFClyBG7GHeMvpnzg4poPCFlj2baIoK2CSQmVbPdcPk4rgg1PAWDQwIIzBCKpZjysHeb/sW9jObekbnn4mCnUdzjRERoklstpZNeWKi/jLEaNsIX1ixhsUyWIyknYGaBjDiiGqmS6BIO1RHu0SydiMv1L/FzIWgyO9VhilGdTWsVDP6CxljxTqg41bobuPazkjQHyBK9rCGQI9J/bjSiA2S6FBDHxhA6SfDjyhvGzDhGNLMd/***2ieUGQWg/atFbqItqW2HZzb7T0cuIiROBYaGLUbWnghcUXAn9dV38GbCMfWk65OhpkD5EQXr/5bPxK41L3sPIrAs2JnMM9nLuj6gLo35VMlsdVQ1c0o3JYQ4JARnSlnUrgW20Cilwf3Fn2m7Yj4QicC6RUhChEudnbgYIjqq0Ypc8BsjJWAPYRuVAUVArINqgUjCNuOxQKV3dyEayS0lZ8UOBfopGBnIlEDS9h62ZIiIKfRhCD6xLsY1PED7K5ZHRvj2TEtQtYoZxeTNDH7/IdukO/cATF9B0DhSvx2YK8EzlG3pygcLGeHZ4DfwmGC5lnO5NZrqFaHXa1LNNgZ9H1rezZyOfizbvT/O5mC8tvINNvP5Ik37OdD6Lmjnc4u0gAKee6QqQ7uk8A6xbrjrnOWp46vnoNmvMZxyAMAD8xFBz9b8MVHu0IJX5etLdRbjsSsMYNpUomqFjfweFe3NeHESUA5IhkYUQVNNwJJ3MCpJDWWHFNLEbzRoUolXVOQhC0PC6j6KmHQH2yib0KWKKJn7kLrUtgGazJMatLDhWDU5oEtZbDJzauxikxto0R6ZirhjKqmVCeVu51yrbW4lgC2upXxJsQ2q5igBaX7Qvz4D1ICkp1m7CRG7cWrU6MfBSXusRsPIp/7wJsdBpXSPb97cZi6y82EP6iQhsyRJ9YODUr22WObb4CvIYo8bDFW1Sw6BImoqkgsoXB/j2oNp0g6vLhYy0OjF5LAdDbhDk23WA00KGj9xAHEPVkqfXdivfc3quxWdpIBri0JnQGA/T1GsxwM4YKvhp5hPl28sgLeo7/I0DstkK6Jispkt5/03N364bRQBAHykAqUAyDvMHz8jiZK0Jo2cnTDTzoDtDi9q2wbSI25lh31FZ68kKJ1t399VRdF4JlSKvaXE8pj1ljE3J6GsII6haD3W17Kns2hmnduL0pEeChUgq0VrXaK8k5e0CR1JdmzVEHNo7WKWwB901cOrtRfxh1yQWvw0dHCSlxzAlISAb7Y2t0MlIoITIKi9XzJSpbxtp5zCQiup3PPDni1wQWotYd9WVZ2Zs2KxDkusDbENOAu68RjtWoOQxGXPrek73CQ9ja2D6doNjdbwX9Exrhqlek9507Sn0J2RO5kJG6huXD3TTXcBcBlD8HYq76JfSNtqgpUwKztPCxaECMmvTm4n1YRT5pkpKfOmlx262TJllv1l2B5cs3f6ODWf/ULarjwMPT2ajviYvCDXl4Kl8HNcmXKhR3W8IzCvWCsPwwDoFbjCk5Xkdd6IVPAX9i0LP5hZqS1bMrJnTreNTVd4glne7T6SdjkFt2MR1UJnsNHlVDoeGhb5VhfphgPg2r1DUyY7k3QlXHGxCBctjlkTUVg9D0NgWf4JrE2KXtdCPR/gX7HjrR6wq24UsibqOH5yi2Zh2hGwP2OWrPRQ6QMqIdW2voAux0GOkL7Ip8GCRml5eilopmRyh8D3PxWw8CwfC81slylodVHvGP8AjGE9cddQhMzQ2s96ZPQVTLEo734UQFkH511HtJGWVCTbxGBmtpEyoJZSJJ9CeG2sXuwEGF7YXR31xJJZbtOKFyskQw3BJGb1SE35iF5lr0hshYB1/gm2YmlTX68nZtux9NWRIKnJ3EHvWUc9UIudzoEMf0LyLZm5pFtkZAUQ16F4BfqEVJekVlUBOs1dCSYN6lUcsVzinhUcY1eBni75vEXaO8zSTy4ZwcOiGYvR9QK2bSuzYen1LKBaFK6UIAVstr29avGAGp5nk3qM63/05rUv2jnDM6XYIoFSx1lpE7SwtvbiRUQjgUA4ZX7Oa7Mp9HJj5W0o7ZVViKbYTtxux5/2AXgXxLo/i3YsHd7BUE/2KTjUrKokTYUzCgTlXkSmYOfRY1wdxeixrLfbSWBD1Y4ZbcMw3l/57XIPmGl42HrRyEFIxGnt7kQHR9A3abfJ93E0Y8AMiQuhG2/WTZho/IzxQ/OfDJm78o97K10pbe7OUIrfpPNTfM3cenEd37ZFWI67yPNwYfiZw8E7uks8GIKSAqrt7q55C10EpmizEcydD5EKtGyElXk6ifr3GO6WbHJNUp6FvgyHQTF6VXRiC91Rv/ZvUQggxRDyF6HibOq5BqDwTbMY0OnbB6nR3KlGYfhkBfEUiqbd10HYzCzWx0uGv54swAwsRUtOQFMpbr5B17yXdE5vGN2uTm02Bgr3EwOUyuw2ttgdUedDH8APmOlDr23wPiFljsTgWbbX/UZQGCyhNxa8avQtDdlymu8e8PS5tMupjMSkJtULUUXQyoKGwcXwwvp25iubNODEt5aZNt45bGKwOW5P3Xzu2ZJ6tAtW/zh7NfN1EHVZIwIlxWgPaag0ComeirsmZfNu3W2wge7Cg9aOYws81iIRaLa0YgYWZwH3C6yTRRQcM8fx1U1TiK2tIkFcc4iAjefZKMHBsodtTzo4EYaYvb9SyjGgZLTMYSlTbpx31Ot0T/t8kFxpML/ObDgoKoxWUVXxfD74HDW/0Uo9JDgdaV/lxJ2CJ7y8gb4ayKsVRNB4BmP5OzA/q9vzZWgtfoM4ODu//vsAed9Dvi4f1pJt5Cf8WWxv1PtWS4gvFe87a03kyhwSzI4obai23oYlCcyrUyL9LBZCwcBgn4tDcno6HPIHT2iEpi00sTuTD2bqXyTkXrxgzGSwlfBzCXr7xczoZDJoU5oj5t59cyq/faUZZkhc0bb8dhOH2/oYcanpfdtNS64VeO42eXaPbkMP00IrHTAUb2KxXQa7h80vB3LMA29cS3EBaJ8pnIJ/sPh0bT5A/FiiiJVJNm8g7EBcvd2nbJWRAkVNp1SxLPoUKF1dRt3OiJwhbdOASOnmJS8IXRjskuIYRsMgXSNdlMGxadedsdB9TKRvgzGkutWu9mQ3+0XJJIp7S23E8b3OLH1CAxhH3wyWu8TmeksImbGc0VY7oSTTtNNWOdeRDQ==</xenc:CipherValue></xenc:CipherData></xenc:EncryptedData></env:Body></env:Envelope>

    Any thoughts???
    Appreciate your input.
    Thanks,
    Laxman

  • Data from SOAP response not getting into Flex object

    I'm trying to get data from an ALM application we use(Collabnet TeamForge) using a SOAP webservice, and am running into a problem.  I should mention that I am new to both Flex, and webservices.
    I used the "Import Web Services" option in Flex Builder 3, and had it generate code for all operations in the WSDL.  Some of them work just fine.  However, there are several where the data from the SOAP response does not get into the Flex object. The senario that doesn't work is when the response contains a data type that extends another datatype.  In TeamForge, they have a type called TrackerSoapRow.  It extends FolderSoapRow, adding 3 fields.  The problem seems to be that in the response from TeamForge, the 3 fields defined in TrackerSoapRow are in the middle of the fields defined in FolderSoapRow.  I've debugged into it, and the problem occures in mx.rpc.xml.XMLDecoder.getApplicableValues( starting at line 2204 of XMLDecoded.as).  As I read the code, the only way a match can be found is if the fields in the response are in the exact same order as in the definintion.  When its processing the extended data type(  by a call to XMLDecoder.decodeComplexExtension ) at some point, one of the derived type's fields is encountered, and the process stops.
    I have called the service using soapui and verified that all the data I expect is in the response.
    As I mentioned, I'm new to web services.  So, I suppose its possible that the format of the data being returned from TeamForge is incorrect.  That they are not supposed to intermingle base and derived fields.  If thats the case, then I need to report this as a bug to Collabnet.
    All help is appreciated.
    Marc Robertson

    Not knowing any of the details about how you call a web service from OAF myself - I'd suggest you post on the proper forum for OA Framework questions: {forum:id=210}
    John

  • SOAP Response conatins no quots, no opening or closing tags.

    Hello All,
    I have developed WebService and I have deployed it on a server, and I have developed client that speak with the WebService via the JDeveloper generated EmbeddedIntegrationWebServiceStub and everything goes greatly when the WebService and the Client are running locally, also it works greatly when the WebService are hosted on server and the client run locally but after I deployed the client to another testing server I found strange behavioure that the returned soap repsonse to the client contans no &lt; or &gt; or "" so I make some dummy solution to regenerate the missing &lt;, &gt;, or "" but the server (hosting the client) keeps giving me the following exception
    bq.      08/10/14 00:02:18 org.apache.xmlbeans.XmlException: error: Unexpected element: CDATA \\     08/10/14 00:02:18 at org.apache.xmlbeans.impl.store.Locale$SaxLoader.load(Locale.java:3486) \\     08/10/14 00:02:18 at org.apache.xmlbeans.impl.store.Locale.parse(Locale.java:712) \\     08/10/14 00:02:18 at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:696) \\     08/10/14 00:02:18 at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:683) \\     08/10/14 00:02:18 at org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:208) \\     08/10/14 00:02:18 at ae.dxbpolice.eps.xml.xmlBeans.ProcVersionsDocument$Factory.parse(Unknown Source) \\     08/10/14 00:02:18 at ae.dxbpolice.eps.tld.tag.FormCustomTag.doStartTag(FormCustomTag.java:158) \\     08/10/14 00:02:18 at eps_integration._jspService(_eps__integration.java:65) \\     08/10/14 00:02:18 at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:56) \\     08/10/14 00:02:18 at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:347) \\     08/10/14 00:02:18 at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:509) \\     08/10/14 00:02:18 at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:413) \\     08/10/14 00:02:18 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) \\     08/10/14 00:02:18 at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:810) \\     08/10/14 00:02:18 at com.evermind.server.http.ServletRequestDispatcher.include(ServletRequestDispatcher.java:121) \\     08/10/14 00:02:18 at com.evermind.server.http.GetParametersRequestDispatcher.newInclude(GetParametersRequestDispatcher.java:80) \\     08/10/14 00:02:18 at com.evermind.server.http.GetParametersRequestDispatcher.include(GetParametersRequestDispatcher.java:34) \\     08/10/14 00:02:18 at com.evermind.server.http.EvermindPageContext.include(EvermindPageContext.java:267) \\     08/10/14 00:02:18 at e_services._jspService(_e__services.java:333) \\     08/10/14 00:02:18 at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:56) \\     08/10/14 00:02:18 at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:347) \\     08/10/14 00:02:18 at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:509) \\     08/10/14 00:02:18 at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:413) \\     08/10/14 00:02:18 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) \\     08/10/14 00:02:18 at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65) \\     08/10/14 00:02:18 at ae.gov.dphq.internet.util.InternetFilter.doFilter(InternetFilter.java:111) \\     08/10/14 00:02:18 at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:649) \\     08/10/14 00:02:18 at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:322) \\     08/10/14 00:02:18 at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:790) \\     08/10/14 00:02:18 at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:208) \\     08/10/14 00:02:18 at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:125) \\     08/10/14 00:02:18 at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186) \\     08/10/14 00:02:18 at java.lang.Thread.run(Thread.java:534) \\     08/10/14 00:02:18 Caused by: org.xml.sax.SAXParseException: Unexpected element: CDATA \\     08/10/14 00:02:18 at org.apache.xmlbeans.impl.piccolo.xml.Piccolo.reportFatalError(Piccolo.java:1038) \\     08/10/14 00:02:18 at org.apache.xmlbeans.impl.piccolo.xml.Piccolo.parse(Piccolo.java:723) \\     08/10/14 00:02:18 at org.apache.xmlbeans.impl.store.Locale$SaxLoader.load(Locale.java:3454) \\     08/10/14 00:02:18 ... 32 more \\     08/10/14 00:02:18 javax.servlet.jsp.JspTagException: SimpleTag: error: Unexpected element: CDATA \\     08/10/14 00:02:18 at ae.dxbpolice.eps.tld.tag.FormCustomTag.doStartTag(FormCustomTag.java:277) \\     08/10/14 00:02:18 at eps_integration._jspService(_eps__integration.java:65) \\     08/10/14 00:02:18 at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:56) \\     08/10/14 00:02:18 at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:347) \\     08/10/14 00:02:18 at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:509) \\     08/10/14 00:02:18 at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:413) \\     08/10/14 00:02:18 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) \\     08/10/14 00:02:18 at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:810) \\     08/10/14 00:02:18 at com.evermind.server.http.ServletRequestDispatcher.include(ServletRequestDispatcher.java:121) \\     08/10/14 00:02:18 at com.evermind.server.http.GetParametersRequestDispatcher.newInclude(GetParametersRequestDispatcher.java:80) \\     08/10/14 00:02:18 at com.evermind.server.http.GetParametersRequestDispatcher.include(GetParametersRequestDispatcher.java:34) \\     08/10/14 00:02:18 at com.evermind.server.http.EvermindPageContext.include(EvermindPageContext.java:267) \\     08/10/14 00:02:18 at e_services._jspService(_e__services.java:333) \\     08/10/14 00:02:18 at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:56) \\     08/10/14 00:02:18 at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:347) \\     08/10/14 00:02:18 at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:509) \\     08/10/14 00:02:18 at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:413) \\     08/10/14 00:02:18 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) \\     08/10/14 00:02:18 at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65) \\     08/10/14 00:02:18 at ae.gov.dphq.internet.util.InternetFilter.doFilter(InternetFilter.java:111) \\     08/10/14 00:02:18 at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:649) \\     08/10/14 00:02:18 at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:322) \\     08/10/14 00:02:18 at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:790) \\     08/10/14 00:02:18 at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:208) \\     08/10/14 00:02:18 at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:125) \\     08/10/14 00:02:18 at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186) \\     08/10/14 00:02:18 at java.lang.Thread.run(Thread.java:534)
    and this is the XML document that generate this problem
    bq.      &lt;procVersions xmlns="http://www.xmlBeans.xml.eps.dxbpolice.ae"&gt; \\     &lt;procVersion id="2" beneficiaryType="EXTERNAL_PERSON" importanceLevel="NORMAL" isIncludeHierarchy="false" isNotifiable="false" isRemote="false" nameAR="&Ccedil;&Igrave;&Ntilde;&Ccedil;&Aacute; &aelig;&ccedil;&Ccedil;&ecirc;&Eacute; &Ccedil;&auml;&Icirc;&Iuml;&aring;&Eacute;" nameEN="Termination Procedure" status="ACTIVE" versionNo="V1"/&gt; \\     &lt;procVersion id="21" beneficiaryType="EXTERNAL_COMPANY" importanceLevel="NORMAL" isIncludeHierarchy="false" isNotifiable="false" isRemote="false" nameAR="&Ccedil;&Igrave;&Ntilde;&Ccedil;&Aacute; &times;&auml;&Egrave; &Atilde;&Igrave;&Ccedil;&Ograve;&Eacute;" nameEN="Vacation Request Procedure" status="ACTIVE" versionNo="V2"/&gt; \\     &lt;/procVersions&gt;
    so are there any suggestion about why the resposnse I got before my processing contains no &lt; or &gt; or " on the server however it comes gratly locally is there any library I should make sure that it doesn't exist on the server.
    this is how the xml returned looks before manual adjustment
    bq. procVersions xmlns=http://www.xmlBeans.xml.eps.dxbpolice.ae \\ procVersion id=2 beneficiaryType=EXTERNAL_PERSON importanceLevel=NORMAL isIncludeHierarchy=false isNotifiable=false isRemote=false nameAR=&Ccedil;&Igrave;&Ntilde;&Ccedil;&Aacute; &aelig;&ccedil;&Ccedil;&ecirc;&Eacute; &Ccedil;&auml;&Icirc;&Iuml;&aring;&Eacute; nameEN=Termination Procedure status=ACTIVE versionNo=V1/ \\ procVersion id=21 beneficiaryType=EXTERNAL_COMPANY importanceLevel=NORMAL isIncludeHierarchy=false isNotifiable=false isRemote=false nameAR=&Ccedil;&Igrave;&Ntilde;&Ccedil;&Aacute; &times;&auml;&Egrave; &Atilde;&Igrave;&Ccedil;&Ograve;&Eacute; nameEN=Vacation Request Procedure status=ACTIVE versionNo=V2/ \\ /procVersions
    and why it keeps giving me the same problem even after I have corrected the returned soap response manually
    Thanks in advance
    Edited by: Ali Abdel-Aziz on Oct 13, 2008 9:22 PM

    ok, now my work arround works greatly as I was missing to pass the correct variable to the parser method and was passing the same old variable ;).
    but I still wanna know what can be the reason for filtering the returned soap response and remove &lt;, &gt;, " from it.
    Are there any Application Server configuration that can be the reason for this behavioure ?
    thanks.
    Edited by: Ali Abdel-Aziz on Oct 14, 2008 2:39 PM

  • Valid SOAP response

    Hi All,
    I have a problem with a webservice response. I need to invoke a webservice (binary implementation is different) that is located in two seperate servers (binary implementation is different). Each webservice has the same interface for both the request and the response. My cliente (calling code) is using the Java API for XML-based RPC (JAX-RPC) and is implemented using weblogic server 7.0 to invoke the two web services. I can invoke correctly one of the web services but I get an error with the other one.
    I have seen in other forums that weblogic requires a property passed in when you start weblogic called:
    weblogic.webservice.i18n.charset=UTF-8 -Dfile.encoding=ISO-8859-1
    where I pass in like
    'Dweblogic.webservice.i18n.charset=UTF-8 -Dfile.encoding=ISO-8859-1'
    but this has not solved the problem.
    Questions:
    1: Does the WSDL have to be the same for the two web services ?
    2: Is it a problem with the response (XML) or a communication error ?
    Thanking you in advance,
    Nacho
    PD: The error I get is:
    com.amena.sgp.funcionalidades.incidencias.excepciones.ErrorEnvioEstado: Error reading the response from: https://ws/webservice/gi. Please ensure that this is a valid SOAP response. The message was:
    <env:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"><env:Header></env:Header><env:Body><m:gi-aperturaResponse xmlns:m="urn:pm_gi_interfaz_soap2" env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><result xmlns:ns100="urn:pm_gi_interfaz_soap2" xsi:type="ns100:gi-resp-t"><cod-respuesta xsi:type="xsd:string">05000</cod-respuesta><des-respuesta xsi:type="xsd:string">Ok. Ejecuci?n correcta de la operaci?n.</des-respuesta></result></m:gi-aperturaResponse></env:Body></env:Envelope>
    at com.amena.sgp.webservice.incidencias.proxy.IncidenciasWSProxy.abrirIncidencia(IncidenciasWSProxy.java:316)
    at com.amena.sgp.funcionalidades.incidencias.IncidenciaEmisor.abrirPendiente(IncidenciaEmisor.java:466)
    at com.amena.sgp.funcionalidades.incidencias.IncidenciaEmisor.abrirIncidencia(IncidenciaEmisor.java:129)
    at com.amena.sgp.funcionalidades.incidencias.FactoriaIncidencias.obtenerIncidencia(FactoriaIncidencias.java:117)
    at com.amena.sgp.factoria.comandos.incidencias.CmdCrearIncidenciaEmisor.ejecutarComando(CmdCrearIncidenciaEmisor.java:169)
    at com.amena.sgp.servlets.Controlador.doGet(Controlador.java:147)
    at com.amena.sgp.servlets.Controlador.doPost(Controlador.java:218)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1075)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:418)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5517)
    at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:685)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3156)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2506)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)
    and :
    unknown attr1.3.6.1.4.1.311.17.1
    <!--REQUEST.................-->
    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <env:Header>
    </env:Header>
    <env:Body>
    <m:gi-apertura xmlns:m="urn:pm_gi_interfaz_soap2"
    env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
    <cod-usuario xsi:type="xsd:string"></cod-usuario>
    <tex-password xsi:type="xsd:string"></tex-password>
    <cod-usuactuacion xsi:type="xsd:string">Administrador</cod-usuactuacion>
    <cod-incidencia xsi:type="xsd:string">AME-6002-000000061</cod-incidencia>
    <tip-asociado xsi:type="xsd:string">M</tip-asociado>
    <tex-asociado xsi:nil="true">
    </tex-asociado>
    <fec-actuacion xsi:type="xsd:string">29/08/2005 14:58:43</fec-actuacion>
    <lst-msisdn>
    <item>
    </item>
    </lst-msisdn>
    <tex-incidencia xsi:type="xsd:string">Prueba de sistemas.</tex-incidencia>
    </m:gi-apertura>
    </env:Body>
    </env:Envelope>Handshake finished!
    CipherSuite:SSL_RSA_WITH_RC4_128_MD5
    SessionId [Session-2, SSL_RSA_WITH_RC4_128_MD5]
    PeerHost www.portabilidad.vodafone.es
    java.io.CharConversionException: Illegal ASCII character, 0xf3
    at weblogic.xml.babel.reader.XmlReader$AsciiReader.read(XmlReader.java:824)
    at weblogic.xml.babel.scanner.ScannerState.read(ScannerState.java:382)
    at weblogic.xml.babel.scanner.ScannerState.expect(ScannerState.java:235)
    at weblogic.xml.babel.scanner.CloseTag.read(CloseTag.java:21)
    at weblogic.xml.babel.scanner.Scanner.startState(Scanner.java:226)
    at weblogic.xml.babel.scanner.Scanner.scan(Scanner.java:153)
    at weblogic.xml.babel.baseparser.BaseParser.prime(BaseParser.java:243)
    at weblogic.xml.babel.baseparser.BaseParser.initScanner(BaseParser.java:107)
    at weblogic.xml.babel.baseparser.BaseParser.init(BaseParser.java:222)
    at weblogic.xml.babel.baseparser.BaseParser.init(BaseParser.java:101)
    at weblogic.xml.babel.parsers.XMLInputStreamParser.<init>(XMLInputStreamParser.java:35)
    at weblogic.xml.babel.stream.XMLInputStreamBase.open(XMLInputStreamBase.java:64)
    at weblogic.xml.babel.stream.XMLInputStreamBase.open(XMLInputStreamBase.java:48)
    at weblogic.xml.babel.stream.XMLInputStreamFactoryImpl.newInputStream(XMLInputStreamFactoryImpl.java:66)
    at weblogic.xml.babel.stream.XMLInputStreamFactoryImpl.newInputStream(XMLInputStreamFactoryImpl.java:53)
    at weblogic.xml.stream.util.RecyclingFactory.remove(RecyclingFactory.java:95)
    at weblogic.xml.stream.util.RecyclingFactory.remove(RecyclingFactory.java:128)
    at weblogic.webservice.core.soap.SOAPEnvelopeImpl.<init>(SOAPEnvelopeImpl.java:165)
    at weblogic.webservice.core.soap.SOAPPartImpl.<init>(SOAPPartImpl.java:104)
    at weblogic.webservice.core.soap.SOAPMessageImpl.<init>(SOAPMessageImpl.java:113)
    at weblogic.webservice.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:27)
    at weblogic.webservice.binding.soap.HttpClientBinding.receive(HttpClientBinding.java:185)
    at weblogic.webservice.core.handler.ClientHandler.handleResponse(ClientHandler.java:57)
    at weblogic.webservice.core.HandlerChain.handleResponse(HandlerChain.java:199)
    at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:435)
    at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:360)
    at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:441)
    at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:310)
    at com.amena.sgp.webservice.incidencias.proxy.IncidenciasWSProxy.abrirIncidencia(IncidenciasWSProxy.java:284)
    at com.amena.sgp.webservice.incidencias.rmi.IncidenciasServer.abrirIncidencia(IncidenciasServer.java:54)
    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:324)
    at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:261)
    at sun.rmi.transport.Transport$1.run(Transport.java:148)
    at java.security.AccessController.doPrivileged(Native Method)
    at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
    at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
    at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
    at java.lang.Thread.run(Thread.java:536)
    amount read:0inputBufferSize512overflow256
    Error at line:1 col:562 Got character[0] expected a valid XML character
    at weblogic.xml.babel.scanner.ScannerState.checkedRead(ScannerState.java:594)
    at weblogic.xml.babel.scanner.CharData.read(CharData.java:65)
    at weblogic.xml.babel.scanner.Scanner.startState(Scanner.java:265)
    at weblogic.xml.babel.scanner.Scanner.scan(Scanner.java:153)
    at weblogic.xml.babel.baseparser.BaseParser.accept(BaseParser.java:451)
    at weblogic.xml.babel.baseparser.StartElement.parse(StartElement.java:77)
    at weblogic.xml.babel.baseparser.BaseParser.parseElement(BaseParser.java:381)
    at weblogic.xml.babel.baseparser.BaseParser.parseSome(BaseParser.java:278)
    at weblogic.xml.babel.parsers.XMLInputStreamParser.internalParseSome(XMLInputStreamParser.java:120)
    at weblogic.xml.babel.parsers.XMLInputStreamParser.streamParseSome(XMLInputStreamParser.java:135)
    at weblogic.xml.babel.stream.XMLInputStreamBase.peek(XMLInputStreamBase.java:203)
    at weblogic.xml.stream.util.XMLInputStreamFilterBase.hasNext(XMLInputStreamFilterBase.java:55)
    at weblogic.webservice.xml.XMLNode.readChildren(XMLNode.java:714)
    at weblogic.webservice.xml.XMLNode.read(XMLNode.java:664)
    at weblogic.webservice.xml.XMLNode.readChildren(XMLNode.java:722)
    at weblogic.webservice.xml.XMLNode.read(XMLNode.java:664)
    at weblogic.webservice.xml.XMLNode.readChildren(XMLNode.java:722)
    at weblogic.webservice.xml.XMLNode.read(XMLNode.java:664)
    at weblogic.webservice.xml.XMLNode.readChildren(XMLNode.java:722)
    at weblogic.webservice.xml.XMLNode.read(XMLNode.java:664)
    at weblogic.webservice.core.soap.SOAPEnvelopeImpl.<init>(SOAPEnvelopeImpl.java:166)
    at weblogic.webservice.core.soap.SOAPPartImpl.<init>(SOAPPartImpl.java:104)
    at weblogic.webservice.core.soap.SOAPMessageImpl.<init>(SOAPMessageImpl.java:113)
    at weblogic.webservice.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:27)
    at weblogic.webservice.binding.soap.HttpClientBinding.receive(HttpClientBinding.java:185)
    at weblogic.webservice.core.handler.ClientHandler.handleResponse(ClientHandler.java:57)
    at weblogic.webservice.core.HandlerChain.handleResponse(HandlerChain.java:199)
    at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:435)
    at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:360)
    at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:441)
    at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:310)
    at com.amena.sgp.webservice.incidencias.proxy.IncidenciasWSProxy.abrirIncidencia(IncidenciasWSProxy.java:284)
    at com.amena.sgp.webservice.incidencias.rmi.IncidenciasServer.abrirIncidencia(IncidenciasServer.java:54)
    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:324)
    at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:261)
    at sun.rmi.transport.Transport$1.run(Transport.java:148)
    at java.security.AccessController.doPrivileged(Native Method)
    at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
    at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
    at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
    at java.lang.Thread.run(Thread.java:536)
    --------------- nested within: ------------------
    weblogic.xml.stream.XMLStreamException: Got character[0] expected a valid XML character - with nested exception:
    [Error at line:1 col:562  Got character[0] expected a valid XML character]
    at weblogic.xml.babel.adapters.XMLInputStreamElementFactory.create(XMLInputStreamElementFactory.java:106)
    at weblogic.xml.babel.parsers.XMLInputStreamParser.internalParseSome(XMLInputStreamParser.java:123)
    at weblogic.xml.babel.parsers.XMLInputStreamParser.streamParseSome(XMLInputStreamParser.java:135)
    at weblogic.xml.babel.stream.XMLInputStreamBase.peek(XMLInputStreamBase.java:203)
    at weblogic.xml.stream.util.XMLInputStreamFilterBase.hasNext(XMLInputStreamFilterBase.java:55)
    at weblogic.webservice.xml.XMLNode.readChildren(XMLNode.java:714)
    at weblogic.webservice.xml.XMLNode.read(XMLNode.java:664)
    at weblogic.webservice.xml.XMLNode.readChildren(XMLNode.java:722)
    at weblogic.webservice.xml.XMLNode.read(XMLNode.java:664)
    at weblogic.webservice.xml.XMLNode.readChildren(XMLNode.java:722)
    at weblogic.webservice.xml.XMLNode.read(XMLNode.java:664)
    at weblogic.webservice.xml.XMLNode.readChildren(XMLNode.java:722)
    at weblogic.webservice.xml.XMLNode.read(XMLNode.java:664)
    at weblogic.webservice.core.soap.SOAPEnvelopeImpl.<init>(SOAPEnvelopeImpl.java:166)
    at weblogic.webservice.core.soap.SOAPPartImpl.<init>(SOAPPartImpl.java:104)
    at weblogic.webservice.core.soap.SOAPMessageImpl.<init>(SOAPMessageImpl.java:113)
    at weblogic.webservice.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:27)
    at weblogic.webservice.binding.soap.HttpClientBinding.receive(HttpClientBinding.java:185)
    at weblogic.webservice.core.handler.ClientHandler.handleResponse(ClientHandler.java:57)
    at weblogic.webservice.core.HandlerChain.handleResponse(HandlerChain.java:199)
    at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:435)
    at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:360)
    at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:441)
    at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:310)
    at com.amena.sgp.webservice.incidencias.proxy.IncidenciasWSProxy.abrirIncidencia(IncidenciasWSProxy.java:284)
    at com.amena.sgp.webservice.incidencias.rmi.IncidenciasServer.abrirIncidencia(IncidenciasServer.java:54)
    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:324)
    at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:261)
    at sun.rmi.transport.Transport$1.run(Transport.java:148)
    at java.security.AccessController.doPrivileged(Native Method)
    at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
    at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
    at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
    at java.lang.Thread.run(Thread.java:536)
    <Aug 29, 2005 2:58:48 PM MEST> <Info> <webservice> <220025> <Handler weblogic.webservice.core.handler.ClientHandler threw an exception from its handleResponse method. The exception was:
    javax.xml.rpc.JAXRPCException: java.io.IOException: Error reading the response from: https://www.xxx.xxxx. Please ensure that this is a valid SOAP response. The message was:
    <env:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"><env:Header></env:Header><env:Body><m:gi-aperturaResponse xmlns:m="urn:pm_gi_interfaz_soap2" env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><result xmlns:ns100="urn:pm_gi_interfaz_soap2" xsi:type="ns100:gi-resp-t"><cod-respuesta xsi:type="xsd:string">05000</cod-respuesta><des-respuesta xsi:type="xsd:string">Ok. Ejecuci?n correcta de la operaci?n.</des-respuesta></result></m:gi-aperturaResponse></env:Body></env:Envelope>>
    <!--RESPONSE.................-->
    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <env:Header>
    </env:Header>
    <env:Body>
    <env:Fault>
    <faultcode>env:Server</faultcode>
    <faultstring>Error reading the response from: https://xxx.xxx.xxx/wwww. Please ensure that this is a valid SOAP response. The message was:
    <env:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"><env:Header></env:Header><env:Body><m:gi-aperturaResponse xmlns:m="urn:pm_gi_interfaz_soap2" env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><result xmlns:ns100="urn:pm_gi_interfaz_soap2" xsi:type="ns100:gi-resp-t"><cod-respuesta xsi:type="xsd:string">05000</cod-respuesta><des-respuesta xsi:type="xsd:string">Ok. Ejecuci?n correcta de la operaci?n.</des-respuesta></result></m:gi-aperturaResponse></env:Body></env:Envelope></faultstring>
    <detail>
    <bea_fault:stacktrace xmlns:bea_fault="http://www.bea.com/servers/wls70/webservice/fault/1.0.0">java.io.IOException: Error reading the response from: https://www.xxx.xxxe. Please ensure that this is a valid SOAP response. The message was:
    <env:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"><env:Header></env:Header><env:Body><m:gi-aperturaResponse xmlns:m="urn:pm_gi_interfaz_soap2" env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><result xmlns:ns100="urn:pm_gi_interfaz_soap2" xsi:type="ns100:gi-resp-t"><cod-respuesta xsi:type="xsd:string">05000</cod-respuesta><des-respuesta xsi:type="xsd:string">Ok. Ejecuci?n correcta de la operaci?n.</des-respuesta></result></m:gi-aperturaResponse></env:Body></env:Envelope>
    at weblogic.webservice.binding.soap.HttpClientBinding.receive(HttpClientBinding.java:189)
    at weblogic.webservice.core.handler.ClientHandler.handleResponse(ClientHandler.java:57)
    at weblogic.webservice.core.HandlerChain.handleResponse(HandlerChain.java:199)
    at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:435)
    at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:360)
    at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:441)
    at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:310)
    at com.amena.sgp.webservice.incidencias.proxy.IncidenciasWSProxy.abrirIncidencia(IncidenciasWSProxy.java:284)
    at com.amena.sgp.webservice.incidencias.rmi.IncidenciasServer.abrirIncidencia(IncidenciasServer.java:54)
    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:324)
    at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:261)
    at sun.rmi.transport.Transport$1.run(Transport.java:148)
    at java.security.AccessController.doPrivileged(Native Method)
    at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
    at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
    at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
    at java.lang.Thread.run(Thread.java:536)
    </bea_fault:stacktrace>
    </detail>
    </env:Fault>
    </env:Body>
    </env:Envelope>

    I'm having the same problem. We were calling the service via weblogic.jws.proxies. , after moving end point to another host in other lan (tunneled to old end point )
    After this we can't invoke old methods all we got is this exception
    <env:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
    xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <env:Header>
    </env:Header>
    <env:Body>
    <env:Fault>
    <faultcode>env:Server</faultcode>
    <faultstring>Error reading the response from: http://fire.unx.era.pl:7778/adPrm/ServicesForPRM/WS-Impl/FetchAtmosferaRejectableGroups. Please ensure that this is a valid SOAP response. The message was:
    <?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Body><ns0:fetchAtmosferaRejectableGroupsResponse xmlns:ns0="http://www.computerland.pl/xsd/matrix/ws/"><ns0:result><ns0:errCode>0</ns0:errCode><ns0:errDesc>OK</ns0:errDesc></ns0:result><ns0:groupList><ns0:group name="Poczta/Domena/Terminale/CIS/DokE/Intranet, II linia"/><ns0:group name="IPS HelpDesk, II linia"/><ns0:group name="Telekomunikacja Help, II linia"/><ns0:group name="SAP Help, II linia"/><ns0:group name="CS Technical Support"/><ns0:group name="Interfejsy z Sieci?? Telekom, III linia"/><ns0:group name="Billing Analiza i Rozw??j, III linia"/><ns0:group name="Customer Care Analiza i Rozw??j, III Linia"/><ns0:group name="SAP Analiza i Rozw??j Admin, III linia"/><ns0:group name="Systemy Wspomagania Sieci ERA AiR, III linia"/><ns0:group name="CIS Sekcja Budowy Hurtowni Danych, III linia"/><ns0:group name="CIS Sekcja Budowy Aplikacji Analitycznych, III linia"/><ns0:group name="Intranet Analiza i Rozw??j, III linia"/><ns0:group name="Dok Elektr i Workflow AiR, III linia"/><ns0:group name="Sekcja Nadzoru Operacyjnego, III Linia"/><ns0:group name="Sekcja Test??w System??w, III Linia"/><ns0:group name="Telekomunikacja AiR, III linia"/><ns0:group name="PC Analiza i Rozw??j, III linia"/><ns0:group name="PC Zesp???? Bezpiecze??stwa Syst"/><ns0:group name="Oracle i Unix Administracja, III Linia"/><ns0:group name="Operatorzy, Sekcja Obs??ugi System??w"/><ns0:group name="Administratorzy Siec Syst Komp, III linia"/><ns0:group name="Billing & CustomerCare Support, II linia"/><ns0:group name="Sekcja Nadzoru Aplikacji, III Linia"/><ns0:group name="TIBCO Analiza i Rozw??j, III linia"/><ns0:group name="Region Katowice"/><ns0:group name="Region Gda??sk"/><ns0:group name="Region Pozna??"/><ns0:group name="Region Warszawa"/><ns0:group name="Sekcja Ochrony Danych, Pion Administracji"/><ns0:group name="PC Helpdesk, II linia"/></ns0:groupList></ns0:fetchAtmosferaRejectableGroupsResponse></SOAP-ENV:Body></SOAP-ENV:Envelope></faultstring>
    <detail>
    <bea_fault:stacktrace xmlns:bea_fault="http://www.bea.com/servers/wls70/webservice/fault/1.0.0">java.io.IOException: Error reading the response from: http://fire.unx.era.pl:7778/adPrm/ServicesForPRM/WS-Impl/FetchAtmosferaRejectableGroups. Please ensure that this is a valid SOAP response. The message was:
    <?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Body><ns0:fetchAtmosferaRejectableGroupsResponse xmlns:ns0="http://www.computerland.pl/xsd/matrix/ws/"><ns0:result><ns0:errCode>0</ns0:errCode><ns0:errDesc>OK</ns0:errDesc></ns0:result><ns0:groupList><ns0:group name="Poczta/Domena/Terminale/CIS/DokE/Intranet, II linia"/><ns0:group name="IPS HelpDesk, II linia"/><ns0:group name="Telekomunikacja Help, II linia"/><ns0:group name="SAP Help, II linia"/><ns0:group name="CS Technical Support"/><ns0:group name="Interfejsy z Sieci?? Telekom, III linia"/><ns0:group name="Billing Analiza i Rozw??j, III linia"/><ns0:group name="Customer Care Analiza i Rozw??j, III Linia"/><ns0:group name="SAP Analiza i Rozw??j Admin, III linia"/><ns0:group name="Systemy Wspomagania Sieci ERA AiR, III linia"/><ns0:group name="CIS Sekcja Budowy Hurtowni Danych, III linia"/><ns0:group name="CIS Sekcja Budowy Aplikacji Analitycznych, III linia"/><ns0:group name="Intranet Analiza i Rozw??j, III linia"/><ns0:group name="Dok Elektr i Workflow AiR, III linia"/><ns0:group name="Sekcja Nadzoru Operacyjnego, III Linia"/><ns0:group name="Sekcja Test??w System??w, III Linia"/><ns0:group name="Telekomunikacja AiR, III linia"/><ns0:group name="PC Analiza i Rozw??j, III linia"/><ns0:group name="PC Zesp???? Bezpiecze??stwa Syst"/><ns0:group name="Oracle i Unix Administracja, III Linia"/><ns0:group name="Operatorzy, Sekcja Obs??ugi System??w"/><ns0:group name="Administratorzy Siec Syst Komp, III linia"/><ns0:group name="Billing & CustomerCare Support, II linia"/><ns0:group name="Sekcja Nadzoru Aplikacji, III Linia"/><ns0:group name="TIBCO Analiza i Rozw??j, III linia"/><ns0:group name="Region Katowice"/><ns0:group name="Region Gda??sk"/><ns0:group name="Region Pozna??"/><ns0:group name="Region Warszawa"/><ns0:group name="Sekcja Ochrony Danych, Pion Administracji"/><ns0:group name="PC Helpdesk, II linia"/></ns0:groupList></ns0:fetchAtmosferaRejectableGroupsResponse></SOAP-ENV:Body></SOAP-ENV:Envelope>
    at weblogic.webservice.binding.soap.HttpClientBinding.receive(HttpClientBinding.java:195)
    at weblogic.webservice.core.handler.ClientHandler.handleResponse(ClientHandler.java:57)
    at weblogic.webservice.core.HandlerChain.handleResponse(HandlerChain.java:199)
    at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:456)
    at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:377)
    at weblogic.webservice.core.rpc.StubImpl._invoke(StubImpl.java:244)
    at weblogic.jws.proxies.FetchAtmosferaRejectableGroups_PortType_Stub.fetchAtmosferaRejectableGroups(FetchAtmosferaRejectableGroups_PortType_Stub.java:33)
    at pl.era.prime.integration.client.AtmPCHS2PrimeBean.FetchAtmosferaRejectableGroups(AtmPCHS2PrimeBean.java:167)
    at pl.era.prime.integration.client.AtmPCHS2PrimeSession_lm80md_EOImpl.FetchAtmosferaRejectableGroups(AtmPCHS2PrimeSession_lm80md_EOImpl.java:46)
    at pl.era.prime.integration.client.AtmPCHS2PrimeSession_lm80md_EOImpl_WLSkel.invoke(Unknown Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:455)
    at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:114)
    at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:396)
    at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:726)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:391)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:251)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:219)
    </bea_fault:stacktrace>
    </detail>
    </env:Fault>
    </env:Body>
    </env:Envelope>
    I suppose the problem is in setting end point for back response, has any one similar problem ??

  • Help: SOAP Response Fault when big string is returned

    Hello all, I'm quite newbie on Flex and SOAP, so sorry if I'm making an obvious question
    I  have an application in Flex that consumes a webservice, and everything  runs smoothly until I try to return a big string, which I find to be  odd. In my tests, when the string is over 490 characters, I get the  following message:
    SOAP Response cannot be decoded. Raw response: faultCode="DecodingError" faultDetail="null"
    I  made a PHP client, just for testing, to consume the same webservice,  that calls the same operation. But in this other client, I get no errors  and the string is returned complete, with no problems.
    Sorry for my english, and any help will be very appreciated! Thanks!
    Here is my script:
    <?xml version="1.0" encoding="utf-8"?>
    <s:Application xmlns:fx="http://ns.adobe.com/mxml/2009"
                   xmlns:s="library://ns.adobe.com/flex/spark"
                   xmlns:mx="library://ns.adobe.com/flex/mx" minWidth="955" minHeight="600">
        <fx:Script>
            <![CDATA[
                import mx.collections.ArrayCollection;
                import mx.rpc.events.ResultEvent;           
                [Bindable]private var testValue:String;
                protected function floappService_variableTestResultHandler(event:ResultEvent):void
                    this.testValue = event.result as String;
            ]]>
        </fx:Script>
        <fx:Declarations>
            <s:WebService id="ws"
                          wsdl="mywebservice?wsdl"
                <s:operation name="variableTest"
                             result="floappService_variableTestResultHandler(event)"
                             fault="mx.controls.Alert.show(event.fault.faultString)"/>
            </s:WebService>
        </fx:Declarations>
        <mx:VBox width="100%" height="100%">
            <mx:Form width="100%" height="100%">
                <mx:FormItem>
                    <mx:HBox>
                        <s:Button label="Variable Test" click="ws.variableTest()"/>
                        <mx:Text text="{testValue}"/>
                    </mx:HBox>
                </mx:FormItem>
            </mx:Form>
        </mx:VBox>
    </s:Application>

    Here is the raw response in the case that I get no faults (string with 490 'A's)
    HTTP/1.1 200 OK
    Date: Tue, 21 Sep 2010 17:36:46 GMT
    Server: Apache/2.2.14 (Ubuntu)
    X-Powered-By: PHP/5.3.2-1ubuntu4.2
    X-SOAP-Server: NuSOAP/0.7.3 (1.114)
    Content-Length: 1027
    Vary: Accept-Encoding
    Connection: close
    Content-Type: text/xml; charset=ISO-8859-1
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns="http://fusionforge.inteligis.paqtc.org.br">
    <SOAP-ENV:Body>
    <ns1:variableTestResponse xmlns:ns1="http://fusionforge.inteligis.paqtc.org.br">
    <myReturn xsi:type="xsd:string">AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA</myReturn>
    </ns1:variableTestResponse>
    </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
    And here is the case when I get the fault (string with 491 - or more - 'A's):
    HTTP/1.1 200 OK
    Date: Tue, 21 Sep 2010 17:40:40 GMT
    Server: Apache/2.2.14 (Ubuntu)
    X-Powered-By: PHP/5.3.2-1ubuntu4.2
    X-SOAP-Server: NuSOAP/0.7.3 (1.114)
    Content-Length: 1028
    Vary: Accept-Encoding
    Connection: close
    Content-Type: text/xml; charset=ISO-8859-1
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns="http://fusionforge.inteligis.paqtc.org.br">
    <SOAP-ENV:Body>
    <ns1:variableTestResponse xmlns:ns1="http://fusionforge.inteligis.paqtc.org.br">
    <myReturn xsi:type="xsd:string">AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA</myReturn>
    </ns1:variableTestResponse>
    </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
    I checked both XMLs "well-formedness" on W3 XML Validator (
    http://www.w3schools.com/XML/xml_validator.asp), and got no errors.
    The  only difference between both responses is the Content-Length, so I'm  guessing that it has something to do with it (don't have any idea of  what/why)

Maybe you are looking for