XSLT Problem with soap namespace

Hi there,
I have a problem transforming an XML doc with soap elements, using XSLT (Xalan).
Here's the input:
<?xml version = "1.0" encoding = "ISO-8859-1"?>
<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/" xmlns="http://www.ean.nl">
  <testthis>123456</testthis>
</soap:Envelope>and here's the XSL:
<?xml version="1.0"?>
<xsl:transform xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" exclude-result-prefixes="soap">
<xsl:output method="xml" indent="yes"/>
<xsl:template match="soap:Envelope">
<Orders>
     <H01>
          <xsl:value-of select="testthis"/>
     </H01>
</Orders>
</xsl:template>
</xsl:transform>I expect to get something like:
<?xml version="1.0" encoding="UTF-8"?>
<Orders>
<H01>123456<H01>
<Orders>But instead I get:
<?xml version="1.0" encoding="UTF-8"?>
<Orders>
<H01/>
</Orders>I've tried a lot of things and I'm probably overseeing something stupid, but I'm stuck.
It seems as if anything without soap: namespace cannot be processed by my XSL (when I add it in the input XML and XSL it works).
Any help would be greatly appreciated.
Greetings,
Erik

Yes, I found it!
The following XSL for the same XML doc works!
<?xml version="1.0"?>
<xsl:transform xmlns:ean="http://www.ean.nl" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" exclude-result-prefixes="soap">
<xsl:output method="xml" indent="yes"/>
<xsl:template match="soap:Envelope">
<Orders>
     <H01>
          <xsl:value-of select="ean:testthis"/>
     </H01>
</Orders>
</xsl:template>
</xsl:transform>Thanks, you pointed me in the right direction :-)
Erik

Similar Messages

  • Another problem with SOAP sender

    I have another problem with SOAP scenario in a different environment (PI 7.0) from my earlier post.
    Scenario:
    Soap Sender -> PI -> Soap Receiver
    Following steps from GoogleSearch SOAP scenario in the SAP How-to Guide for SAP NetWeaver '04 entitled: "How To... Use the XI 3.0 SOAP Adapter" version 1.00 - March 2006.
    I have loaded in the api.google.com/GoogleSearch.wsdl file as an External definition and created the SOAP receiver as described in the How-to guide.  It takes a doGoogleSearch as input and sends back a doGoogleSearchResponse (Sync Call). 
    Note that the GoogleSearch.wsdl contains a complex type ResultElementArray that refers to ResultElement\[\], and a DirectoryCategoryArray that refers to DirectoryCategory\[\].  The ResultElement and DirectoryCategory types are defined in the GoogleSearch.wsdl file.
    Problem One:
    The generated WSDL for the SOAP sender contains the ResultElementArray and DirectoryCategoryArray types but it DOES NOT contain the required ResultElement and DirectoryCategory types.  XML Spy complains that this WSDL is not valid because the type ResultElement\[\] is not defined.
    Problem Two:
    I generate a SOAP message in XML Spy, provide values for the doGoogleSearch fields, and send.  In SXMB_MONI, the SOAP sender payload contains only the <key> value from the doGoogleSearch message body, i.e. <part name="key" type="xsd:string" />
    The other doGoogleSearch fields seem to be missing, i.e.
      <part name="q" type="xsd:string" />
      <part name="start" type="xsd:int" />
      <part name="maxResults" type="xsd:int" />
      <part name="filter" type="xsd:boolean" />
      <part name="restrict" type="xsd:string" />
      <part name="safeSearch" type="xsd:boolean" />
      <part name="lr" type="xsd:string" />
      <part name="ie" type="xsd:string" />
      <part name="oe" type="xsd:string" />
    Does anyone know why:
    (1) PI/XI seems to leave out the ResultElement and DirectoryCategory types from the SOAP sender service WSDL file?
    (2) The doGoogleSearch message seen in SXMB_MONI contains only the first <key> field, and not the other fields?
    Thanks for any help with this.

    I have another problem with SOAP scenario in a different environment (PI 7.0) from my earlier post.
    Scenario:
    Soap Sender -> PI -> Soap Receiver
    Following steps from GoogleSearch SOAP scenario in the SAP How-to Guide for SAP NetWeaver '04 entitled: "How To... Use the XI 3.0 SOAP Adapter" version 1.00 - March 2006.
    I have loaded in the api.google.com/GoogleSearch.wsdl file as an External definition and created the SOAP receiver as described in the How-to guide.  It takes a doGoogleSearch as input and sends back a doGoogleSearchResponse (Sync Call). 
    Note that the GoogleSearch.wsdl contains a complex type ResultElementArray that refers to ResultElement\[\], and a DirectoryCategoryArray that refers to DirectoryCategory\[\].  The ResultElement and DirectoryCategory types are defined in the GoogleSearch.wsdl file.
    Problem One:
    The generated WSDL for the SOAP sender contains the ResultElementArray and DirectoryCategoryArray types but it DOES NOT contain the required ResultElement and DirectoryCategory types.  XML Spy complains that this WSDL is not valid because the type ResultElement\[\] is not defined.
    Problem Two:
    I generate a SOAP message in XML Spy, provide values for the doGoogleSearch fields, and send.  In SXMB_MONI, the SOAP sender payload contains only the <key> value from the doGoogleSearch message body, i.e. <part name="key" type="xsd:string" />
    The other doGoogleSearch fields seem to be missing, i.e.
      <part name="q" type="xsd:string" />
      <part name="start" type="xsd:int" />
      <part name="maxResults" type="xsd:int" />
      <part name="filter" type="xsd:boolean" />
      <part name="restrict" type="xsd:string" />
      <part name="safeSearch" type="xsd:boolean" />
      <part name="lr" type="xsd:string" />
      <part name="ie" type="xsd:string" />
      <part name="oe" type="xsd:string" />
    Does anyone know why:
    (1) PI/XI seems to leave out the ResultElement and DirectoryCategory types from the SOAP sender service WSDL file?
    (2) The doGoogleSearch message seen in SXMB_MONI contains only the first <key> field, and not the other fields?
    Thanks for any help with this.

  • Problem with old namespace in WSDL file

    I have a problem with my WSDL file.  My scenario is SOAP to IDOC. 
    Originally the ESB data types were configured under namespace urn:test1:xxx  for development purposes.  When it came time to implement and test, we copied the data types from the old name space to a new namespace http://company.com:interface.
    After the new objects were created, all the old test objects were deleted, including the old namespace definition.  Now when I generate the WSDL file, the top part of the WSDL file looks correct, but toward the bottom, there are references to the old namespace.
    Does anyone know why these reference are appearing, and is there any way to correct this without deleting all my objects and rebuilding everything?
    Thanks in advance for any help.  Will award points for help.
    Terri

    Found the problem....the XML namespace in the Message type still contained the old namespace.  When this was changed to the new namespace, second target namespace was no longer generated.

  • Newline problem with soap

    I'm having these weird problems with newlines. I'm sending \n in a message because I have a multi lined message i want parsed. Axis is receiving the message and throwing exceptions. I printed out the line it's parsing and it's giving this error that it can't parse:
    '2.5
    PID'
    The parser is not supposed to parse past the \n but it seems to be trying to. I've tested this without webservices and it works fine, adding webservices into the equation gives me these errors.

    Additional info: The problem is the same in the entire environment here (PI DEV, QAS and PRD) and on another PI machine.
    So I doubt very much if it's cache related.
    Edit: This is the 'application error':
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  XML Validation Inbound Channel Response
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>Application</SAP:Category>
      <SAP:Code area="UNKNOWN">APPLICATION_ERROR</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>application fault</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="http://xml.apache.org/axis/">hostname</SAP:ApplicationFaultMessage>
      <SAP:Stack />
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Edited by: Frederik-Jan Roose on Dec 7, 2009 11:11 AM

  • XSLT problem with img tag in Saxon

    Hi,
    Iam getting a problem with <img> tag when transforming a document using Saxon transformer. In the input XSLT I have proper closing tag for <img>, but the output of the transformation is not well formed as the closing tag for <img> does not appear. I need to feed the output to a FO object to generate a print preview, but the output is not well-formed.
    Kindly help to resolve the issue.
    Kind Regards,
    Abhinandan

    Perhaps that is because you are generating HTML as your output? As I recall, <img> tags don't have to be closed in HTML. So try generating XML instead if you need XML.

  • XSLT-problem with sequence attributes

    Hi,
    in my XSLT-program (i'm a real newbie!) i'm adding dynamically attributes and their values to a tag, by using the following code :
    <SUPPLIER>
      <xsl:attribute name="FUNLOC">
        <xsl:value-of select="SUPPLIER_FUNLOC" />
      </xsl:attribute>
      <xsl:attribute name="NAME">
        <xsl:value-of select="SUPPLIER_NAME" />
      </xsl:attribute>
      <xsl:attribute name="LOCATION">
        <xsl:value-of select="SUPPLIER_LOCATION" />
      </xsl:attribute>
      </SUPPLIER>
    The problem is that the attributes in the resulting xml-file are alphabetically ordered. For instance :
    <SUPPLIER FUNLOC="9522222" LOCATION="NL" NAME="Test vendor VMOI">
    How can i arrange that the result of the xml-file is a sequence of entrance is taken, so
    <SUPPLIER FUNLOC="9522222" NAME="Test vendor VMOI" LOCATION="NL" >
    regards,
    Hans
    [email protected]

    Hi Hans,
    I think you're using ABAP-XSLT?!
    If you do so, you can solve the sorting problem by using a 1:1 Message mapping after the ABAP-XSLT mapping. This resolves the problem that the nodes are not in the correct order.
    In your interface mapping you have to configure 2 mappings:
    1: ABAP-XSLT
    2: Message mapping.
    Of course this means that the total processing time increases a little bit.
    I had the same problem with the sequence of my (ACC_DOCUMENT) idoc nodes, the ABAP-XSLT screwed up the idoc, but the 1:1 message mapping solved the problem.
    Regards,
    Mark

  • Problem with SOAP Servlet

    Hi,
    I have a SOAP servlet, but It is the fist SOAPServlet as I use.
    I think that the vsd that developper of SOAP servlet provide is ok.
    But, I do not understand which is the XML that I could provide to it.
    It is posible that I have a problem with XML, SCHEMA and SOAP.
    Could you help me , I attach the VSD, but I need a tool or a sample file in order to call my SOAP servlet.
    <xsd:schema xmlns:xsd="http://schemas.xmlsoap.org/soap/encoding">
        <xsd:complexType name="STD_TRN1_I_PARM_V_TYPE">
          <xsd:sequence>
            <xsd:element name="COD_TX_DI">
                <xsd:simpleType base="xsd:string">
                    <maxLength value="00004"/>
                </xsd:simpleType>
            </xsd:element>
            <xsd:element name="ID_INTERNO_TERM_TN">
                <xsd:simpleType base="xsd:string">
                    <maxLength value="00008"/>
                </xsd:simpleType>
            </xsd:element>
            <xsd:element name="ID_EMPL_AUT">
                <xsd:simpleType base="xsd:string">
                    <maxLength value="00008"/>
                </xsd:simpleType>
            </xsd:element>
            <xsd:element name="NUM_SEC">
                <xsd:simpleType base="xsd:decimal">
                    <totalDigits value="00007"/>
                    <fractionDigits value="00"/>
                </xsd:simpleType>
            </xsd:element>
            <xsd:element name="COD_TX">
                <xsd:simpleType base="xsd:string">
                    <maxLength value="00008"/>
                </xsd:simpleType>
            </xsd:element>
          </xsd:sequence>
        </xsd:complexType>
        <xsd:complexType name="TR_CONS_SALDOS_VISTA_EVT_Y_TYPE">
          <xsd:sequence>
            <xsd:element name="COD_CENT_UO">
                <xsd:simpleType base="xsd:string">
                    <maxLength value="00004"/>
                </xsd:simpleType>
            </xsd:element>
            <xsd:element name="NUM_SEC_AC">
                <xsd:simpleType base="xsd:decimal">
                    <totalDigits value="00010"/>
                    <fractionDigits value="00"/>
                </xsd:simpleType>
            </xsd:element>
            <xsd:element name="COD_NRBE_EN">
                <xsd:simpleType base="xsd:string">
                    <maxLength value="00004"/>
                </xsd:simpleType>
            </xsd:element>
          </xsd:sequence>
        </xsd:complexType>
        <xsd:complexType name="STD_TRN1_O_PARM_V_TYPE">
          <xsd:sequence>
            <xsd:element name="HORA_OPRCN" type="xsd:time"/>
            <xsd:element name="FECHA_OPRCN" type="xsd:date"/>
          </xsd:sequence>
        </xsd:complexType>
        <xsd:complexType name="PSV_DISPO_V_TYPE">
          <xsd:sequence>
            <xsd:element name="STD_DEC_15Y2">
                <xsd:simpleType base="xsd:decimal">
                    <totalDigits value="00015"/>
                    <fractionDigits value="02"/>
                </xsd:simpleType>
            </xsd:element>
          </xsd:sequence>
        </xsd:complexType>
        <xsd:complexType name="PSV_SDO_CONTABLE_V_TYPE">
          <xsd:sequence>
            <xsd:element name="IMP_SDO">
                <xsd:simpleType base="xsd:decimal">
                    <totalDigits value="00015"/>
                    <fractionDigits value="02"/>
                </xsd:simpleType>
            </xsd:element>
          </xsd:sequence>
        </xsd:complexType>
        <xsd:complexType name="PSV_SDO_RETEN_V_TYPE">
          <xsd:sequence>
            <xsd:element name="IMP_SDO">
                <xsd:simpleType base="xsd:decimal">
                    <totalDigits value="00015"/>
                    <fractionDigits value="02"/>
                </xsd:simpleType>
            </xsd:element>
          </xsd:sequence>
        </xsd:complexType>
        <xsd:complexType name="PSV_SDO_AUT_V_TYPE">
          <xsd:sequence>
            <xsd:element name="IMP_SDO">
                <xsd:simpleType base="xsd:decimal">
                    <totalDigits value="00015"/>
                    <fractionDigits value="02"/>
                </xsd:simpleType>
            </xsd:element>
          </xsd:sequence>
        </xsd:complexType>
        <xsd:complexType name="PSV_SDO_INCID_V_TYPE">
          <xsd:sequence>
            <xsd:element name="IMP_SDO">
                <xsd:simpleType base="xsd:decimal">
                    <totalDigits value="00015"/>
                    <fractionDigits value="02"/>
                </xsd:simpleType>
            </xsd:element>
          </xsd:sequence>
        </xsd:complexType>
        <xsd:complexType name="PSV_BLOQUEOS_V_TYPE">
          <xsd:sequence>
            <xsd:element name="STD_CHAR_01">
                <xsd:simpleType base="xsd:string">
                    <maxLength value="00001"/>
                </xsd:simpleType>
            </xsd:element>
          </xsd:sequence>
        </xsd:complexType>
        <xsd:complexType name="PSV_SDO_CONECT_V_TYPE">
          <xsd:sequence>
            <xsd:element name="IMP_SDO">
                <xsd:simpleType base="xsd:decimal">
                    <totalDigits value="00015"/>
                    <fractionDigits value="02"/>
                </xsd:simpleType>
            </xsd:element>
          </xsd:sequence>
        </xsd:complexType>
        <xsd:complexType name="COD_IDIOMA_V_TYPE">
          <xsd:sequence>
            <xsd:element name="COD_IDIOMA">
                <xsd:simpleType base="xsd:string">
                    <maxLength value="00002"/>
                </xsd:simpleType>
            </xsd:element>
          </xsd:sequence>
        </xsd:complexType>
        <xsd:complexType name="PSV_ANOTACIONES_V_TYPE">
          <xsd:sequence>
            <xsd:element name="STD_CHAR_01">
                <xsd:simpleType base="xsd:string">
                    <maxLength value="00001"/>
                </xsd:simpleType>
            </xsd:element>
          </xsd:sequence>
        </xsd:complexType>
        <xsd:complexType name="TR_CONS_SALDOS_VISTA_EVT_Z_TYPE">
          <xsd:sequence>
            <xsd:element name="COD_NUMRCO_MONEDA">
                <xsd:simpleType base="xsd:string">
                    <maxLength value="00003"/>
                </xsd:simpleType>
            </xsd:element>
            <xsd:element name="PSV_DISPO_V" type="PSV_DISPO_V_TYPE"/>
            <xsd:element name="PSV_SDO_CONTABLE_V" type="PSV_SDO_CONTABLE_V_TYPE"/>
            <xsd:element name="PSV_SDO_RETEN_V" type="PSV_SDO_RETEN_V_TYPE"/>
            <xsd:element name="PSV_SDO_AUT_V" type="PSV_SDO_AUT_V_TYPE"/>
            <xsd:element name="PSV_SDO_INCID_V" type="PSV_SDO_INCID_V_TYPE"/>
            <xsd:element name="PSV_BLOQUEOS_V" type="PSV_BLOQUEOS_V_TYPE"/>
            <xsd:element name="PSV_SDO_CONECT_V" type="PSV_SDO_CONECT_V_TYPE"/>
            <xsd:element name="COD_CSB_OF">
                <xsd:simpleType base="xsd:string">
                    <maxLength value="00004"/>
                </xsd:simpleType>
            </xsd:element>
            <xsd:element name="NOMB_50">
                <xsd:simpleType base="xsd:string">
                    <maxLength value="00050"/>
                </xsd:simpleType>
            </xsd:element>
            <xsd:element name="COD_INTERNO_UO">
                <xsd:simpleType base="xsd:string">
                    <maxLength value="00004"/>
                </xsd:simpleType>
            </xsd:element>
            <xsd:element name="COD_IDIOMA_V" type="COD_IDIOMA_V_TYPE"/>
            <xsd:element name="PSV_ANOTACIONES_V" type="PSV_ANOTACIONES_V_TYPE"/>
          </xsd:sequence>
        </xsd:complexType>
        <xsd:complexType name="STD_TRN1_MSJ_PARM_V_TYPE">
          <xsd:sequence>
            <xsd:element name="TEXT_ARG1">
                <xsd:simpleType base="xsd:string">
                    <maxLength value="00018"/>
                </xsd:simpleType>
            </xsd:element>
            <xsd:element name="TEXT_CODE" type="xsd:int"/>
          </xsd:sequence>
        </xsd:complexType>
    <xsd:complexType name="TR_CONS_SALDOS_VISTA_TRN1">
        <xsd:complexType name="TR_CONS_SALDOS_VISTA_TRN1_O_TYPE">
          <xsd:sequence>
            <xsd:element name="RTRN_CD" type="xsd:int"/>
            <xsd:element name="STD_TRN1_O_PARM_V" type="STD_TRN1_O_PARM_V_TYPE"/>
            <xsd:element name="TR_CONS_SALDOS_VISTA_EVT_Z" type="TR_CONS_SALDOS_VISTA_EVT_Z_TYPE"/>
            <xsd:complexType name="STD_TRN1_MSJ_PARM_V_OCCURS">
                <xsd:element name="STD_TRN1_MSJ_PARM_V" type="STD_TRN1_MSJ_PARM_V_TYPE" maxOccurs="000005"/>
            </xsd:complexType>
          </xsd:sequence>
        </xsd:complexType>
        <xsd:complexType name="TR_CONS_SALDOS_VISTA_TRN1_I_TYPE">
          <xsd:sequence>
            <xsd:element name="STD_TRN1_I_PARM_V" type="STD_TRN1_I_PARM_V_TYPE"/>
            <xsd:element name="TR_CONS_SALDOS_VISTA_EVT_Y" type="TR_CONS_SALDOS_VISTA_EVT_Y_TYPE"/>
          </xsd:sequence>
        </xsd:complexType>
    </xsd:complexType>
    </xsd:schema>Thanks you

    Hi,
    I have a SOAP servlet, but It is the fist SOAPServlet as I use.
    I think that the vsd that developper of SOAP servlet provide is ok.
    But, I do not understand which is the XML that I could provide to it.
    It is posible that I have a problem with XML, SCHEMA and SOAP.
    Could you help me , I attach the VSD, but I need a tool or a sample file in order to call my SOAP servlet.
    <xsd:schema xmlns:xsd="http://schemas.xmlsoap.org/soap/encoding">
        <xsd:complexType name="STD_TRN1_I_PARM_V_TYPE">
          <xsd:sequence>
            <xsd:element name="COD_TX_DI">
                <xsd:simpleType base="xsd:string">
                    <maxLength value="00004"/>
                </xsd:simpleType>
            </xsd:element>
            <xsd:element name="ID_INTERNO_TERM_TN">
                <xsd:simpleType base="xsd:string">
                    <maxLength value="00008"/>
                </xsd:simpleType>
            </xsd:element>
            <xsd:element name="ID_EMPL_AUT">
                <xsd:simpleType base="xsd:string">
                    <maxLength value="00008"/>
                </xsd:simpleType>
            </xsd:element>
            <xsd:element name="NUM_SEC">
                <xsd:simpleType base="xsd:decimal">
                    <totalDigits value="00007"/>
                    <fractionDigits value="00"/>
                </xsd:simpleType>
            </xsd:element>
            <xsd:element name="COD_TX">
                <xsd:simpleType base="xsd:string">
                    <maxLength value="00008"/>
                </xsd:simpleType>
            </xsd:element>
          </xsd:sequence>
        </xsd:complexType>
        <xsd:complexType name="TR_CONS_SALDOS_VISTA_EVT_Y_TYPE">
          <xsd:sequence>
            <xsd:element name="COD_CENT_UO">
                <xsd:simpleType base="xsd:string">
                    <maxLength value="00004"/>
                </xsd:simpleType>
            </xsd:element>
            <xsd:element name="NUM_SEC_AC">
                <xsd:simpleType base="xsd:decimal">
                    <totalDigits value="00010"/>
                    <fractionDigits value="00"/>
                </xsd:simpleType>
            </xsd:element>
            <xsd:element name="COD_NRBE_EN">
                <xsd:simpleType base="xsd:string">
                    <maxLength value="00004"/>
                </xsd:simpleType>
            </xsd:element>
          </xsd:sequence>
        </xsd:complexType>
        <xsd:complexType name="STD_TRN1_O_PARM_V_TYPE">
          <xsd:sequence>
            <xsd:element name="HORA_OPRCN" type="xsd:time"/>
            <xsd:element name="FECHA_OPRCN" type="xsd:date"/>
          </xsd:sequence>
        </xsd:complexType>
        <xsd:complexType name="PSV_DISPO_V_TYPE">
          <xsd:sequence>
            <xsd:element name="STD_DEC_15Y2">
                <xsd:simpleType base="xsd:decimal">
                    <totalDigits value="00015"/>
                    <fractionDigits value="02"/>
                </xsd:simpleType>
            </xsd:element>
          </xsd:sequence>
        </xsd:complexType>
        <xsd:complexType name="PSV_SDO_CONTABLE_V_TYPE">
          <xsd:sequence>
            <xsd:element name="IMP_SDO">
                <xsd:simpleType base="xsd:decimal">
                    <totalDigits value="00015"/>
                    <fractionDigits value="02"/>
                </xsd:simpleType>
            </xsd:element>
          </xsd:sequence>
        </xsd:complexType>
        <xsd:complexType name="PSV_SDO_RETEN_V_TYPE">
          <xsd:sequence>
            <xsd:element name="IMP_SDO">
                <xsd:simpleType base="xsd:decimal">
                    <totalDigits value="00015"/>
                    <fractionDigits value="02"/>
                </xsd:simpleType>
            </xsd:element>
          </xsd:sequence>
        </xsd:complexType>
        <xsd:complexType name="PSV_SDO_AUT_V_TYPE">
          <xsd:sequence>
            <xsd:element name="IMP_SDO">
                <xsd:simpleType base="xsd:decimal">
                    <totalDigits value="00015"/>
                    <fractionDigits value="02"/>
                </xsd:simpleType>
            </xsd:element>
          </xsd:sequence>
        </xsd:complexType>
        <xsd:complexType name="PSV_SDO_INCID_V_TYPE">
          <xsd:sequence>
            <xsd:element name="IMP_SDO">
                <xsd:simpleType base="xsd:decimal">
                    <totalDigits value="00015"/>
                    <fractionDigits value="02"/>
                </xsd:simpleType>
            </xsd:element>
          </xsd:sequence>
        </xsd:complexType>
        <xsd:complexType name="PSV_BLOQUEOS_V_TYPE">
          <xsd:sequence>
            <xsd:element name="STD_CHAR_01">
                <xsd:simpleType base="xsd:string">
                    <maxLength value="00001"/>
                </xsd:simpleType>
            </xsd:element>
          </xsd:sequence>
        </xsd:complexType>
        <xsd:complexType name="PSV_SDO_CONECT_V_TYPE">
          <xsd:sequence>
            <xsd:element name="IMP_SDO">
                <xsd:simpleType base="xsd:decimal">
                    <totalDigits value="00015"/>
                    <fractionDigits value="02"/>
                </xsd:simpleType>
            </xsd:element>
          </xsd:sequence>
        </xsd:complexType>
        <xsd:complexType name="COD_IDIOMA_V_TYPE">
          <xsd:sequence>
            <xsd:element name="COD_IDIOMA">
                <xsd:simpleType base="xsd:string">
                    <maxLength value="00002"/>
                </xsd:simpleType>
            </xsd:element>
          </xsd:sequence>
        </xsd:complexType>
        <xsd:complexType name="PSV_ANOTACIONES_V_TYPE">
          <xsd:sequence>
            <xsd:element name="STD_CHAR_01">
                <xsd:simpleType base="xsd:string">
                    <maxLength value="00001"/>
                </xsd:simpleType>
            </xsd:element>
          </xsd:sequence>
        </xsd:complexType>
        <xsd:complexType name="TR_CONS_SALDOS_VISTA_EVT_Z_TYPE">
          <xsd:sequence>
            <xsd:element name="COD_NUMRCO_MONEDA">
                <xsd:simpleType base="xsd:string">
                    <maxLength value="00003"/>
                </xsd:simpleType>
            </xsd:element>
            <xsd:element name="PSV_DISPO_V" type="PSV_DISPO_V_TYPE"/>
            <xsd:element name="PSV_SDO_CONTABLE_V" type="PSV_SDO_CONTABLE_V_TYPE"/>
            <xsd:element name="PSV_SDO_RETEN_V" type="PSV_SDO_RETEN_V_TYPE"/>
            <xsd:element name="PSV_SDO_AUT_V" type="PSV_SDO_AUT_V_TYPE"/>
            <xsd:element name="PSV_SDO_INCID_V" type="PSV_SDO_INCID_V_TYPE"/>
            <xsd:element name="PSV_BLOQUEOS_V" type="PSV_BLOQUEOS_V_TYPE"/>
            <xsd:element name="PSV_SDO_CONECT_V" type="PSV_SDO_CONECT_V_TYPE"/>
            <xsd:element name="COD_CSB_OF">
                <xsd:simpleType base="xsd:string">
                    <maxLength value="00004"/>
                </xsd:simpleType>
            </xsd:element>
            <xsd:element name="NOMB_50">
                <xsd:simpleType base="xsd:string">
                    <maxLength value="00050"/>
                </xsd:simpleType>
            </xsd:element>
            <xsd:element name="COD_INTERNO_UO">
                <xsd:simpleType base="xsd:string">
                    <maxLength value="00004"/>
                </xsd:simpleType>
            </xsd:element>
            <xsd:element name="COD_IDIOMA_V" type="COD_IDIOMA_V_TYPE"/>
            <xsd:element name="PSV_ANOTACIONES_V" type="PSV_ANOTACIONES_V_TYPE"/>
          </xsd:sequence>
        </xsd:complexType>
        <xsd:complexType name="STD_TRN1_MSJ_PARM_V_TYPE">
          <xsd:sequence>
            <xsd:element name="TEXT_ARG1">
                <xsd:simpleType base="xsd:string">
                    <maxLength value="00018"/>
                </xsd:simpleType>
            </xsd:element>
            <xsd:element name="TEXT_CODE" type="xsd:int"/>
          </xsd:sequence>
        </xsd:complexType>
    <xsd:complexType name="TR_CONS_SALDOS_VISTA_TRN1">
        <xsd:complexType name="TR_CONS_SALDOS_VISTA_TRN1_O_TYPE">
          <xsd:sequence>
            <xsd:element name="RTRN_CD" type="xsd:int"/>
            <xsd:element name="STD_TRN1_O_PARM_V" type="STD_TRN1_O_PARM_V_TYPE"/>
            <xsd:element name="TR_CONS_SALDOS_VISTA_EVT_Z" type="TR_CONS_SALDOS_VISTA_EVT_Z_TYPE"/>
            <xsd:complexType name="STD_TRN1_MSJ_PARM_V_OCCURS">
                <xsd:element name="STD_TRN1_MSJ_PARM_V" type="STD_TRN1_MSJ_PARM_V_TYPE" maxOccurs="000005"/>
            </xsd:complexType>
          </xsd:sequence>
        </xsd:complexType>
        <xsd:complexType name="TR_CONS_SALDOS_VISTA_TRN1_I_TYPE">
          <xsd:sequence>
            <xsd:element name="STD_TRN1_I_PARM_V" type="STD_TRN1_I_PARM_V_TYPE"/>
            <xsd:element name="TR_CONS_SALDOS_VISTA_EVT_Y" type="TR_CONS_SALDOS_VISTA_EVT_Y_TYPE"/>
          </xsd:sequence>
        </xsd:complexType>
    </xsd:complexType>
    </xsd:schema>Thanks you

  • WLS 7.0 sp2 - Servlet Problems with SOAP messages

              I'm using Weblogic 7.0 SP2 and trying to create a Servlet to receive SOAP wrapped
              XML messages. I'm getting the following error. Is this a problem with WLS7.0sp2's
              support of JAXM? The System.out.println's indicate I have successfully received
              the incoming SOAP request and then successfully formatted the SOAP response, but
              upon returning saving the response it appears to blow up. Does anyone have any
              suggestions?
              I need to do the following in a servlet:
              - receive an incoming SOAP request with an embedded XML message
              - perform some processing
              - return a SOAP response with an embedded XML message
              Should I be using JAXM? Or can I do this same task easily with JAX-RPC?
              <Feb 24, 2004 4:10:42 PM AST> <Error> <HTTP> <101017> <[ServletContext(id=260434
              7,name=isd.war,context-path=)] Root cause of ServletException
              java.lang.Error: NYI
              at weblogic.webservice.core.soap.SOAPMessageImpl.saveRequired(SOAPMessag
              eImpl.java:360)
              at javax.xml.messaging.JAXMServlet.doPost(Unknown Source)
              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:1058)
              at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
              pl.java:401)
              at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
              pl.java:306)
              at weblogic.servlet.internal.WebAppServletContext$ServletInvocationActio
              n.run(WebAppServletContext.java:5445)
              at weblogic.security.service.SecurityServiceManager.runAs(SecurityServic
              eManager.java:780)
              at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
              rvletContext.java:3105)
              at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
              pl.java:2588)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
              >
              I've stripped the code down so that all it does is verifies the incoming SOAP/XML
              request and creates a hard-coded response... be gentle... I'm a novice at this
              import javax.xml.soap.*;
              import javax.servlet.*;
              import javax.servlet.http.*;
              // import javax.xml.transform.*;
              import java.util.*;
              import java.io.*;
              public class RegisterServlet extends HttpServlet
              static MessageFactory fac = null;
              static
              try
              fac = MessageFactory.newInstance();
              catch (Exception ex)
              ex.printStackTrace();
              public void init(ServletConfig servletConfig) throws ServletException
              super.init(servletConfig);
              public void doPost(HttpServletRequest req, HttpServletResponse resp) throws ServletException,
              IOException
              try
              System.out.println("** Note: doPost() Entering req = " + req);
              // Get all the headers from the HTTP request
              MimeHeaders headers = getHeaders(req);
              // Get the body of the HTTP request
              InputStream is = req.getInputStream();
              // Now internalize the contents of a HTTP request
              // and create a SOAPMessage
              SOAPMessage msg = fac.createMessage(headers, is);
              System.out.println("** Note: doPost() Step A");
              SOAPMessage reply = null;
              reply = onMessage(msg);
              System.out.println("** Note: doPost() Step B reply = " + reply);
              if (reply != null)
              * Need to call saveChanges because we're
              * going to use the MimeHeaders to set HTTP
              * response information. These MimeHeaders
              * are generated as part of the save.
              if (reply.saveRequired())
              System.out.println("** Note: doPost() Step C reply.saveRequired()");
              reply.saveChanges();
              resp.setStatus(HttpServletResponse.SC_OK);
              putHeaders(reply.getMimeHeaders(), resp);
              // Write out the message on the response stream
              OutputStream os = resp.getOutputStream();
              System.out.println("** Note: doPost() Step D os = " + os);
              reply.writeTo(os);
              os.flush();
              else
              resp.setStatus(HttpServletResponse.SC_NO_CONTENT);
              catch (Exception ex)
              throw new ServletException("** Error: SAAJ POST failed: " + ex.getMessage());
              static MimeHeaders getHeaders(HttpServletRequest req)
              Enumeration enum = req.getHeaderNames();
              MimeHeaders headers = new MimeHeaders();
              while (enum.hasMoreElements())
              String headerName = (String)enum.nextElement();
              String headerValue = req.getHeader(headerName);
              StringTokenizer values =
              new StringTokenizer(headerValue, ",");
              while (values.hasMoreTokens())
              headers.addHeader(headerName,
              values.nextToken().trim());
              return headers;
              static void putHeaders(MimeHeaders headers, HttpServletResponse res)
              Iterator it = headers.getAllHeaders();
              while (it.hasNext())
              MimeHeader header = (MimeHeader)it.next();
              String[] values = headers.getHeader(header.getName());
              if (values.length == 1)
              res.setHeader(header.getName(),
              header.getValue());
              else
              StringBuffer concat = new StringBuffer();
              int i = 0;
              while (i < values.length)
              if (i != 0)
              concat.append(',');
              concat.append(values[i++]);
              res.setHeader(header.getName(), concat.toString());
              // This is the application code for handling the message.
              public SOAPMessage onMessage(SOAPMessage message)
              SOAPMessage replymsg = null;
              try
              System.out.println("** Note: OnMessage() Entering msg = " + message);
              //Extract the ComputerPart element from request message and add to reply SOAP
              message.
              SOAPEnvelope reqse = message.getSOAPPart().getEnvelope();
              SOAPBody reqsb = reqse.getBody();
              //System.out.println("** Note: OnMessage() Step B");
              System.out.println("** Note: OnMessage () Step A Soap Request Message Body = "
              + reqsb);
              //Create a reply mesage from the msgFactory of JAXMServlet
              System.out.println("** Note: OnMessage () Step B");
              replymsg = fac.createMessage();
              SOAPPart sp = replymsg.getSOAPPart();
              SOAPEnvelope se = sp.getEnvelope();
              SOAPBody sb = se.getBody();
              System.out.println("** Note: OnMessage () Step C Soap Reply Before Message Body
              = " + sb);
              se.getBody().addBodyElement(se.createName("RegisterResponse")).addChildElement(se.createName("ErrorCode")).addTextNode("000");
              System.out.println("** Note: OnMessage () Step D Soap Reply After Message Body
              = " + sb);
              replymsg.saveChanges();
              System.out.println("** Note: OnMessage() Exiting replymsg = " + (replymsg));
              catch (Exception ex)
              ex.printStackTrace();
              return replymsg;
              

    Michael,
    I got the same error on WLS8.1/Win2K professional and apache FOP (old version).
    After digging into the WLS code and FOP(old version). i found the conflict happens
    on
    the "org.xml.sax.parser" system property. In WLS code, they hard coded like the
    following when startup weblogic server:
    System.setProperty("org.xml.sax.parser", "weblogic.xml.jaxp.RegistryParser");
    But the FOP code try to use the "org.xml.sax.parser" system property to find the
    sax parser then conlict happens.
    Here is the response from BEA support :
    "I consulted with our developers regarding the question of whether we can change
    the hard-coded value for the java system property: org.xml.sax.parser by using
    a configuration parameter and I found that unfortunately there is no specific
    setting to change the value. As you had mentioned in your note the org.xml.sax.parser
    system property can be changed programmatically in your application code."
    I solve my problem by using newer apache FOP (it never use the system property:org.xml.sax.parser
    any more) and XML Registy for WLS8.1.
    Good luck.
    David Liu
    Point2 Technologies Inc.
    "p_michael" <[email protected]> wrote:
    >
    Help.
    When we migrated from WLS 6.1 to WLS 7.0 SP2 when encountered a problem
    with XML
    parsing that did not previously exist.
    We get the error "weblogic.xml.jaxp.RegistryParser is not a SAX driver".
    What does this mean? And, what should we do about it.
    p_michael

  • [Castor] Problem with the namespace

    Hello,
    I'm using Castor for generate XML file with Java Object(generate with Castor with XSD).
    I have a problem with the syntax and particulary with the reference of the namespace.
    I obtain this :
    <?xml version="1.0" encoding="UTF-8"?>
    <TEST ID="">
    <ns1:PERSON xmlns:ns1="http://www.w3.org/a/">
    <ns1:CALCUL>
    <ns1:SOURCE>RED</ns1:SOURCE>
    <ns1:TIMESTAMP>2004-10-27-11.38.25.237113</ns1:TIMESTAMP>
    </ns1:CALCUL>
    <SIREN>666</SIREN>
    <ns1:DOSSIER>
    <ns1:TYPE>DN</ns1:TYPE>
    <ns1:IDENTIFIANT>333</ns1:IDENTIFIANT>
    </ns1:DOSSIER>
    </ns1:PERSON>
    <ENTITY>
    <COMMON>
    <ns2:ENTITY_ID xmlns:ns2="http://www.w3.org/a/">602449226</ns2:ENTITY_ID>
    <ns3:RATING xmlns:ns3="http://www.w3.org/a/">NDE</ns3:RATING>
    </COMMON>
    <SPECIFICS_DATA>
    <ns4:RATING_FC xmlns:ns4="http://www.w3.org/a/">2-</ns4:RATING_FC>
    </SPECIFICS_DATA>
    </ENTITY>
    </TEST>
    but I'd like to obtain :
    <TEST ID="">
    <PERSON >
    <CALCUL>
    <nSOURCE>RED</SOURCE>
    <TIMESTAMP>2004-10-27-11.38.25.237113</TIMESTAMP>
    </CALCUL>
    <SIREN>666</SIREN>
    <nDOSSIER>
    <TYPE>DN</TYPE>
    <IDENTIFIANT>333</IDENTIFIANT>
    </DOSSIER>
    </PERSON>
    <ENTITY>
    <COMMON>
    <ENTITY_ID >602449226</ENTITY_ID>
    <RATING>NDE</RATING>
    </COMMON>
    <SPECIFICS_DATA>
    <RATING_FC >2-</RATING_FC>
    </SPECIFICS_DATA>
    </ENTITY>
    </TEST>
    "http://www.w3.org/a/" is the namespace reference in the xsd, here the begin of the xsd:
    <xs:schema xmlns:FIN_Referential="http://www.w3.org/c/" xmlns:Rating_Referential="http://www.w3.org/f/" xmlns:Global_Referential="http://www.w3.org/a/" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified">
    To marshall I use this code :
    StringWriter fluxXmlSw = new StringWriter() ;
    Marshaller mar = new Marshaller(fluxXmlSw);
    mar.marshal(Test(),fluxXmlSw);
    //Test() is the root element of the file xml
    I hope somebody could help me, it's urgent I solve this problem.
    Thanks for all responses

    just a thought..... did u try removing xmlns:p1="http://ofcom.co.uk/unify/CustomerMaster" from your WSDL file ?
    Try to remove that and proceed in your development.

  • Problem with the namespace in the soap message ' xmlns:p1'

    Hi,
    I have released a WSDL file which the siebel system is consuming to send the data to SAP XI .
    the extract of the WSDL file is as below
    <b><?xml version="1.0" encoding="UTF-8"?>
    <wsdl:definitions name="MI_Customer" targetNamespace="http://ofcom.co.uk/unify/CustomerMaster" xmlns:p1="http://ofcom.co.uk/unify/CustomerMaster" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"><wsdl:types><xsd:schema targetNamespace="http://ofcom.co.uk/unify/CustomerMaster" xmlns="http://ofcom.co.uk/unify/CustomerMaster" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><xsd:element name="MT_Customer" </b>
    if we see in the there is a attribute called xmlns:p1 which is creaing the problem as data sent is as below
    <b>  <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Inbound Message
      -->
    - <MT_Customer xmlns="http://www.siebel.com/xml/MT_Customer" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    - <Customer>
      <Cust_No>0005000013</Cust_No>
      <Title>Mr.</Title>
    </b>
    due to this the XI system is not triggring the mapping.
    as XI expects the data in the below format which we generated with the stylus studio tool
    <b> <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Inbound Message
      -->
    - <p1:MT_Customer xmlns:p1="http://ofcom.co.uk/unify/CustomerMaster" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
    - <Customer>
      <Cust_No>1232</Cust_No>
      <Title>mr.</Title>
    </b>
    If anyone has any Idea as to how can we overcome this problem
    Thanks
    Nikhil

    just a thought..... did u try removing xmlns:p1="http://ofcom.co.uk/unify/CustomerMaster" from your WSDL file ?
    Try to remove that and proceed in your development.

  • XSLT mapping with SOAP Envelope

    Hi
    I'm trying map SOAP response (with Envelope) to pick two values into the target. Here's the data:
    Source (with data):
    <?xml version="1.0"?>
    <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">
         <soap:Body>
              <EnumerateResponse xmlns="http://www.approva.net/BizRights/Services">
                   <EnumerateResult>
                        <TaskID>-1</TaskID>
                        <Result>FinishedSuccessfully</Result>
                        <StatusInfo/>
                   </EnumerateResult>
                   <pageObject>
                        <startIndex>0</startIndex>
                        <pageSize>10</pageSize>
                        <totalRows>1</totalRows>
                        <moreRecords>false</moreRecords>
                        <rowsReturned>1</rowsReturned>
                   </pageObject>
                   <xmlObjects>(large string of valid data in here)</xmlObjects>
              </EnumerateResponse>
         </soap:Body>
    </soap:Envelope>
    Target:
    Only need Result and xmlObjects into target.
    Mapping:
    <?xml version="1.0"?>
    <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
         <xsl:template match="/">
              <poll_status_resp_r3>
                   <Result>
                        <xsl:value-of select="EnumerateResponse/Result"/>
                   </Result>
                   <xmlObjects>
                        <xsl:value-of select="EnumerateResponse/xmlObjects"/>
                   </xmlObjects>
              </poll_status_resp_r3>
         </xsl:template>
    </xsl:stylesheet>
    The values are not getting picked-up into the target.
    What am I missing here?
    Any help is appreciated.

    Hi,
    Save the following XSL file as RSpace.xsl
    <?xml version="1.0" encoding="utf-8"?>
    <xsl:stylesheet version="1.0"
      xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
      <xsl:output method="xml" indent="no"/>
      <xsl:template match="/|comment()|processing-instruction()">
        <xsl:copy>
          <xsl:apply-templates/>
        </xsl:copy>
      </xsl:template>
      <xsl:template match="*">
        <xsl:element name="{local-name()}">
          <xsl:apply-templates select="@*|node()"/>
        </xsl:element>
      </xsl:template>
      <xsl:template match="@*">
        <xsl:attribute name="{local-name()}">
          <xsl:value-of select="."/>
        </xsl:attribute>
      </xsl:template>
    </xsl:stylesheet>
    Zip it and import it under Imported Archive.
    In the interface mapping click "+" to add one more mapping.
    Use this XSL as first mapping and your XSL mapping as the second mapping.
    In your XSLT mapping you can use the XPath as
    "Envelope/Body/EnumerateResponse/Result".
    I mean remove the namespace and use the XPATH.
    Thanks,
    Prakash

  • Problem with SOAP receiver adapter? Please help!

    Hi experts
       I have the following scenario:
       SAP R/3 -ABAP Proxy>XI--->SOAP --webservice
       As you can see, I am sending data from R/3 system to XI via ABAP proxy. XI then sends data or calls a webservice via SOAP adapter.
    When I test this scenario I am getting a error in the sxmb_moni that is,
    "com.sap.aii.af.ra.ms.api.DeliveryException: TEXT/HTML; HTTP 504 Gateway Time-out"
    I have checked the webservice url and it is working fine.
    Can somebody tell me why am I getting this error message? How do I resolve this?
    Thanks
    Gopal

    Hi,
    Can you please check the  settings in Soap Adapter with Module Adapter setting with ModuleTranformBean parameters? There may be some problem. use HTTP Adapter and the message type 'HttpPostIn' to send as HTTP Post.
    Also
    There is the note 450226 gives an overview over error codes
    Probably below solution may help you.........
    As an administrator on your portal go to:
    System Configuration > Service Configuration >applications
    Under: com.sap.portal.ivs.httpservice > Services > Proxy
    If any proxy settings are configured you may end up with the problem, so you need to set the "nonProxyHosts" to include the trex host.
    regards
    Aashish Sinha
    PS : reward points if helpful

  • Problem with soap receiver adapter

    Hi All
    I have Idoc sender and soap receiver in my scenario.
    I am calling web service deployed on WAS.
    The web service is getting called but the acknowledgement message in xi contains following system error acknowledgement because of which xi changes the status of message to WAIT and starts retrying.
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Inbound Message
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIAdapterFramework</SAP:Category>
      <SAP:Code area="MESSAGE">GENERAL</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>com.sap.aii.af.ra.ms.api.MessagingException: java.net.SocketTimeoutException: Read timed out: com.sap.aii.af.ra.ms.api.RecoverableException: java.net.SocketTimeoutException: Read timed out</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack />
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Please anybody can help to resolve this problem. This scenario has worked without any error previously.
    Thanks in advance
    Beena

    Hi Bhavesh,
    It is an Async call where method does not return anything.
    I added entries in IDX_NOALE but still it is setting the message status to WAIT and does retry.
    Following is the Audit Log in Runtime workbench :
    Audit Log for Message: 22b3052d-c519-034e-85db-e65d541d6414
    Time Stamp Status Description
    2006-12-13 10:25:23 Error SOAP: error occured: java.net.SocketTimeoutException: Read timed out
    2006-12-13 10:25:23 Error Exception caught by adapter framework: Read timed out
    2006-12-13 10:25:24 Error Delivery of the message to the application using connection AFW failed, due to: Read timed out.
    2006-12-13 10:25:24 Success The asynchronous message was successfully scheduled to be delivered at Wed Dec 13 10:30:24 GMT+05:30 2006.
    2006-12-13 10:25:24 Success The message status set to WAIT.
    2006-12-13 10:30:25 Success Retrying to deliver message to the application. Retry: 1
    2006-12-13 10:30:25 Success The message was successfully retrieved from the receive queue.
    2006-12-13 10:30:25 Success The message status set to DLNG.
    2006-12-13 10:30:25 Success Delivering to channel: INSPWCCT_PVtoSAP_Ack
    2006-12-13 10:30:25 Success SOAP: request message entering the adapter
    2006-12-13 10:35:28 Success SOAP: call failed
    2006-12-13 10:35:28 Success SOAP: sending a delivery error ack ...
    2006-12-13 10:35:28 Success SOAP: sent a delivery error ack
    2006-12-13 10:35:28 Error SOAP: error occured: java.net.SocketTimeoutException: Read timed out
    2006-12-13 10:35:28 Error Exception caught by adapter framework: Read timed out
    2006-12-13 10:35:28 Error Delivery of the message to the application using connection AFW failed, due to: Read timed out.
    2006-12-13 10:35:28 Success The asynchronous message was successfully scheduled to be delivered at Wed Dec 13 10:40:28 GMT+05:30 2006.
    2006-12-13 10:35:28 Success The message status set to WAIT.
    I have tried this scenario earlier. I am sending the same Idoc from R3 which was processed successfully earlier.
    Thanks
    Beena.

  • Problem with SOAP Adapter receiver not receiving the proper string

    Hi friends
    I have a very simple scenario as follows using SOAP Syncronous Call
    SENDING SCENARIO
    ================
    ExternalClient --> SOAP ADAPTER --> XI -> RFC ADAPTER --> ZBAPI
    RECEIVING SCENARIO
    ==================
    ZBAPI  --> RFC ADAPTER   --> XI    -->   SOAP ADAPTER  --> ExternalClient
    Here External Client is sending a search ID and ZBAPI searches for that record and send the FirstName and LastName.
    I am using external Definitions in XSD format as follows.
    INPUT XSD is
    =========================================
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://cincom.com/xi/socrates/customerSearch" targetNamespace="http://cincom.com/xi/socrates/customerSearch">
         <xsd:element name="ZBAPI_GET_NAME">
              <xsd:complexType>
                   <xsd:all>
                        <xsd:element name="ID" type="xsd:integer" minOccurs="0" />
                   </xsd:all>
              </xsd:complexType>
         </xsd:element>
    </xsd:schema>
    ===========================================
    Reciving XSD file has
    ==============================================
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:socrates.cincom.com" targetNamespace="urn:socrates.cincom.com">
         <xsd:element name="ZBAPI_GET_NAME_RESPONSE">
         <xsd:complexType>
         <xsd:all>
         <xsd:element name="ADDRESSDATA" minOccurs="0">
         <xsd:complexType>
         <xsd:sequence>
         <xsd:element name="FNAME" minOccurs="0">
              <xsd:simpleType>
                   <xsd:restriction base="xsd:string">
                        <xsd:maxLength value="20" />
                   </xsd:restriction>
              </xsd:simpleType>
         </xsd:element>
         <xsd:element name="LNAME" minOccurs="0">
              <xsd:simpleType>
                   <xsd:restriction base="xsd:string">
                        <xsd:maxLength value="20" />
                   </xsd:restriction>
              </xsd:simpleType>
         </xsd:element>
         </xsd:sequence>
         </xsd:complexType>
         </xsd:element>
         </xsd:all>
         </xsd:complexType>
         </xsd:element>
    </xsd:schema>
    =========================================================
    I HAVE TESTED THE ZBAPI AND IT WORKS WELL ON ITS OWN. ALSO I HAVE TESTED THAT THE MESSAGE SENT FROM OUTSIDE CLIENT IS REACHING BAPI. HOWEVER WHEN I GOTO 'SXMB_MONI' AND CHECK THE
    XML STRING THAT THE RECIEVER IS GETTING, I SEE JUST THE FOLLOWING TWO LINES
    ===================================
      <?xml version="1.0" encoding="UTF-8" ?>
      <ns1:ZBAPI_GET_NAME_RESPONSE xmlns:ns1="urn:socrates.cincom.com" />
    ======================================
    IF YOU NEED ANY FURTHER INFO, PLEASE LET ME KNOW.
    HOPE SOME ONE CAN GUIDE ME WITH THIS PROBLEM.
    THANKS IN ADVANCE
    RAM

    Ram
    Can you pls. confirm whether the mapping of your XSD fields & BAPI fields are in same sequence. I mean hierarchy is same or not.
    Just to verify, as you said you are using Sync scenario that means you are using ONE Sender Soap & ONE Reciever RFC adapter.
    Regards
    Lalit

  • 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

Maybe you are looking for

  • Subcontracting: Picking Relevancy of service Line Item in Inbound Delivery

    Hi experts I have a challenge. There is a Subcontracting PO having 2 line items, 1st one is Trading product which is the physical finished product & 2nd line item is service line item( service material type). So Can we create a Inbound Delivery wrt P

  • Why doesn't customer support understand?

    I recently needed to reinstall windows xp.  I have saved everything I needed to reinstall all my software.  My photoshop CS2 is the only problem I've had.  Since it was an upgrade my installation pkge is looking for a previous version.  I have the se

  • Max open cursors exceedeed in SQL Developer 1.1 Patch 2.(1.1.2.25.79)

    While browsing the tables in a schema, I get an ORA-01000 after navigating back and forth between different tabs for a table. Example: logon and navigate to other users, schema1, tables show columns for table one counts in v$open_cursor for the sid s

  • Time Machine - Preparing backup - It's endless

    My C2D Mac Mini is hanging on Time Machine - Preparing Backup for the second time since "Upgrading" to 10.5.2 I had to re-format my backup disk last time and start all the backups again. Here is an extract from the console log: 29/04/2008 23:50:13 /S

  • Protecting a file

    I would like to protect a file. I would like to do this in the following manner: Accept the user's login and password Validate it with my web site If valid then invoke the reader plugin in C# with a password embedded in the program. In addition I wou