Problem invoking weservice of SOAP Document style with literal encoding in

I have a webservice with Document type and with literal encoding which is deployed in weblogic. This webservice has got two methods both with no argument. If I try to invoke using weblogic interface for testing the webservice, only one method is able to invoke.The other method gives invokation error.The Soap request which is going is to this webservice is with empty body.
the request looks like this
<!--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:Body>
</env:Body>
</env:Envelope>
If I am changing one method signatuer in such a way that it has one argument then both methods are able to invoke.
While I am using SAAJ api If I am trying to give the method name in the SOAP request it gives error.
Can anybody help on this.
tech gent

I have realised I was using saaj 1.1 (from jwsdp 1.3) and so have updated to use 1.2 now. But the problem is still there. Should saaj 1.2 support literal encoding? I got the impression from it saying it includes "support for ws-i".

Similar Messages

  • Found the problem (Re: ORA-01461 error in DB with char encoding = UTF8)

     

    Hi,
    Yes even i had this problem and setting this weblogic.oci.min_bind_size =660 solved.
    But the proble i face is this works if i get the connection through java code. Instead if i use Connection pool and edit the config.xml or do through admin console .This doesn't work even after setting this property. Any Help will be appreciated and it is pretty urgent.
    Thanx
    -Sugandha

  • Problem invoking document type webservices with SAAJ

    I cannot invoke document type webservices with SAAJ. No problems invoking rpc-style services. Can anyone help me to invoke doc-type webservices with SAAJ. Very urgent. Thank you.

    Siva Sankar
    You may use Field Exit to do this enhancement. You can create fieldexit from report RSMODPRF.
    In order to use field exit check/activate Profile Parameter abap/fieldexit using t code RZ11.
    Thanks & regards
    Amol Lohade

  • Document style Problem

    We have three issues when trying to implement a document-style service. I will
    document them all but I'd suggest you go through them all before attempting to
    answer any of them.
    We are trying to implement a service that has the following signature:
    public void echoDom(Document doc)
    We want the delivery of our message to be of style ("document"). Therefore, we
    modified our servicegen entry to include the style="document" under the service.
    It looks like the following:
    <servicegen
    destEar="${appDir}/dom.ear"
    warName="dom.war">
    <service
    javaClassComponents="examples.dom.EchoDom"
    targetNamespace="http://examples.org"
    serviceName="dom"
    serviceURI="/EchoDomService"
         generateTypes="True"
    expandMethods="True"
    style="document">
    <client
    packageName="examples.dom"
    clientJarName="client.jar"
    />
    </service>
    <classpath>
    <pathelement path="${temp_dir}"/>
    <pathelement path="${java.class.path}"/>
    </classpath>
    </servicegen>
    1. FIRST PROBLEM:
    The first problem we're having is that it does not compile with the combination
    of our signature being of type void (as shown above) and the style="document"
    in build.xml.
    The error is the following:
    [servicegen] Generating service "dom" ...
    [servicegen] Generating XML types and serializers from java classes (examples.do
    m.EchoDom) ...
    [servicegen] weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[  void:
    null ]
    [servicegen] at weblogic.utils.Debug.assertion(Debug.java:84)
    [servicegen] at weblogic.xml.schema.binding.internal.codegen.Compiler.compile
    (Compiler.java:111)
    [servicegen] at weblogic.xml.schema.binding.internal.XSDTypeMappingBuilder.ma
    pClass(XSDTypeMappingBuilder.java:88)
    [servicegen] at weblogic.xml.schema.binding.internal.TypeMappingBuilderBase.a
    ddMapping(TypeMappingBuilderBase.java:183)
    [servicegen] at weblogic.ant.taskdefs.webservices.autotype.ComponentAutoTyper
    .mapComponent(ComponentAutoTyper.java:155)
    [servicegen] at weblogic.ant.taskdefs.webservices.autotype.JavaAutoTyper.run(
    JavaAutoTyper.java:80)
    [servicegen] at weblogic.ant.taskdefs.webservices.autotype.AutoTypeTask.execu
    te(AutoTypeTask.java:353)
    [servicegen] at weblogic.ant.taskdefs.webservices.servicegen.ServiceGenTask.g
    enerateService(ServiceGenTask.java:251)
    [servicegen] at weblogic.ant.taskdefs.webservices.servicegen.ServiceGenTask.e
    xecute(ServiceGenTask.java:146)
    [servicegen] at org.apache.tools.ant.Task.perform(Task.java:217)
    [servicegen] at org.apache.tools.ant.Target.execute(Target.java:164)
    [servicegen] at org.apache.tools.ant.Target.performTasks(Target.java:182)
    [servicegen] at org.apache.tools.ant.Project.executeTarget(Project.java:601)
    [servicegen] at org.apache.tools.ant.Project.executeTargets(Project.java:560)
    [servicegen] at org.apache.tools.ant.Main.runBuild(Main.java:454)
    [servicegen] at org.apache.tools.ant.Main.start(Main.java:153)
    [servicegen] at org.apache.tools.ant.Main.main(Main.java:176)
    2. SECOND PROBLEM
    If we change the signature to become:
    public Document echoDom(Document doc)
    then the build works but when we try to test our service, it gives us the following:
    [java] java.rmi.RemoteException: web service invoke failed; nested exceptio
    n is:
    [java] javax.xml.soap.SOAPException: failed to serialize xml:weblogic.
    xml.schema.binding.SerializationException: type mapping lookup failure on class=
    class weblogic.apache.xerces.dom.DocumentImpl TypeMapping=TYPEMAPPING SIZE=6
    [java] ENTRY 1:
    [java] class: org.w3c.dom.Document
    [java] xsd_type: ['http://examples.org']:p3:echoDom
    [java] ser: weblogic.xml.schema.binding.internal.builtin.DocumentCode
    c@5973ea
    [java] deser: weblogic.xml.schema.binding.internal.builtin.DocumentCode
    c@49131c
    [java] ENTRY 2:
    [java] class: java.lang.Object
    [java] xsd_type: ['http://examples.org']:p1:echoDomResponse
    [java] ser: weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec@
    5b99f
    [java] deser: weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec@
    3. THIRD PROBLEM:
    Now, when we revert back to style="rpc" and everything works fine and dandy (although
    not as we want it because, as I mentioned above, we want a void signature and
    a document style), we get the following added tag around our body content, which
    we did not add ourselves, nor are we sure yet why it shows up:
    We pass it the following argument:
    <those dummy="hi">
    <this xmlns="mynamespace">
    <f:that xmlns:f="yournamespace">
    <or> a lot of random < </or>
    <f:the>
    </f:the>
    <f:other> foo bar blaz</f:other>
    </f:that>
    </this>
    </those>
    We get the following (notice the <document> tag around it):
    <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:Body>
    <m:echoDom xmlns:m="http://examples.org"
    env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
    <document>
    <those dummy="hi">
    <this xmlns="mynamespace">
    <f:that xmlns:f="yournamespace">
    <or> a lot of random < </or>
    <f:the>
    </f:the>
    <f:other> foo bar blaz</f:other>
    </f:that>
    </this>
    </those>
    </document>
    </m:echoDom>
    </env:Body>
    </env:Envelope>
    4. PROBLEM FOUR (just remembered this one):
    If we use the standard test page (provided with WLS), with (3) above, it chops
    off the "those" and it still wraps it within this new <document> element as show
    below:
    <!--REQUEST.................-->
    <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>
    <m:echoDom xmlns:m="http://examples.org"
    env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
    <document>
    <this xmlns="mynamespace">
    <f:that xmlns:f="yournamespace">
    <or> a lot of random < </or>
    <f:the>
    </f:the>
    <f:other> foo bar blaz</f:other>
    </f:that>
    </this>
    </document>
    </m:echoDom>
    </env:Body>
    </env:Envelope>
    We're not so worried about the fourth because it seems like a bug but the first
    three (especially the first) are most important. Any ideas would be appreciated.
    Thanks
    sami

    Ok I tried it out, DOM with document style web
    service is not working in WLS 7.0.2. I filed
    CR104719. Please contact support with this case
    number to get a patch.
    Sorry for the trouble.
    http://manojc.com
    "sami titi" <[email protected]> wrote in message
    news:[email protected]...
    >
    We're using WLS7 SP2, patch: CR102544_70sp2_v2.jar
    thanks
    "manoj cheenath" <[email protected]> wrote:
    Quick question, before i try this out.
    Which version of WLS? SP?
    http://manojc.com
    "sami titi" <[email protected]> wrote in message
    news:[email protected]...
    We have three issues when trying to implement a document-style service.I
    will
    document them all but I'd suggest you go through them all beforeattempting to
    answer any of them.
    We are trying to implement a service that has the following signature:
    public void echoDom(Document doc)
    We want the delivery of our message to be of style ("document").Therefore, we
    modified our servicegen entry to include the style="document" underthe
    service.
    It looks like the following:
    <servicegen
    destEar="${appDir}/dom.ear"
    warName="dom.war">
    <service
    javaClassComponents="examples.dom.EchoDom"
    targetNamespace="http://examples.org"
    serviceName="dom"
    serviceURI="/EchoDomService"
    generateTypes="True"
    expandMethods="True"
    style="document">
    <client
    packageName="examples.dom"
    clientJarName="client.jar"
    />
    </service>
    <classpath>
    <pathelement path="${temp_dir}"/>
    <pathelement path="${java.class.path}"/>
    </classpath>
    </servicegen>
    1. FIRST PROBLEM:
    The first problem we're having is that it does not compile with thecombination
    of our signature being of type void (as shown above) and thestyle="document"
    in build.xml.
    The error is the following:
    [servicegen] Generating service "dom" ...
    [servicegen] Generating XML types and serializers from java classes(examples.do
    m.EchoDom) ...
    [servicegen] weblogic.utils.AssertionError: ***** ASSERTION FAILED*****[  void:
    null ]
    [servicegen] at weblogic.utils.Debug.assertion(Debug.java:84)
    [servicegen] atweblogic.xml.schema.binding.internal.codegen.Compiler.compile
    (Compiler.java:111)
    [servicegen] atweblogic.xml.schema.binding.internal.XSDTypeMappingBuilder.ma
    pClass(XSDTypeMappingBuilder.java:88)
    [servicegen] atweblogic.xml.schema.binding.internal.TypeMappingBuilderBase.a
    ddMapping(TypeMappingBuilderBase.java:183)
    [servicegen] atweblogic.ant.taskdefs.webservices.autotype.ComponentAutoTyper
    mapComponent(ComponentAutoTyper.java:155)
    [servicegen] atweblogic.ant.taskdefs.webservices.autotype.JavaAutoTyper.run(
    JavaAutoTyper.java:80)
    [servicegen] atweblogic.ant.taskdefs.webservices.autotype.AutoTypeTask.execu
    te(AutoTypeTask.java:353)
    [servicegen] atweblogic.ant.taskdefs.webservices.servicegen.ServiceGenTask.g
    enerateService(ServiceGenTask.java:251)
    [servicegen] atweblogic.ant.taskdefs.webservices.servicegen.ServiceGenTask.e
    xecute(ServiceGenTask.java:146)
    [servicegen] at org.apache.tools.ant.Task.perform(Task.java:217)
    [servicegen] at org.apache.tools.ant.Target.execute(Target.java:164)
    [servicegen] atorg.apache.tools.ant.Target.performTasks(Target.java:182)
    [servicegen] atorg.apache.tools.ant.Project.executeTarget(Project.java:601)
    [servicegen] atorg.apache.tools.ant.Project.executeTargets(Project.java:560)
    [servicegen] at org.apache.tools.ant.Main.runBuild(Main.java:454)
    [servicegen] at org.apache.tools.ant.Main.start(Main.java:153)
    [servicegen] at org.apache.tools.ant.Main.main(Main.java:176)
    2. SECOND PROBLEM
    If we change the signature to become:
    public Document echoDom(Document doc)
    then the build works but when we try to test our service, it givesus the
    following:
    [java] java.rmi.RemoteException: web service invoke failed; nestedexceptio
    n is:
    [java] javax.xml.soap.SOAPException: failed to serializexml:weblogic.
    xml.schema.binding.SerializationException: type mapping lookup failureon
    class=
    class weblogic.apache.xerces.dom.DocumentImpl TypeMapping=TYPEMAPPINGSIZE=6
    [java] ENTRY 1:
    [java] class: org.w3c.dom.Document
    [java] xsd_type: ['http://examples.org']:p3:echoDom
    [java] ser:weblogic.xml.schema.binding.internal.builtin.DocumentCode
    c@5973ea
    [java] deser:weblogic.xml.schema.binding.internal.builtin.DocumentCode
    c@49131c
    [java] ENTRY 2:
    [java] class: java.lang.Object
    [java] xsd_type: ['http://examples.org']:p1:echoDomResponse
    [java] ser:weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec@
    5b99f
    [java] deser:weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec@
    3. THIRD PROBLEM:
    Now, when we revert back to style="rpc" and everything works fine anddandy (although
    not as we want it because, as I mentioned above, we want a void
    signature
    and
    a document style), we get the following added tag around our body
    content,
    which
    we did not add ourselves, nor are we sure yet why it shows up:
    We pass it the following argument:
    <those dummy="hi">
    <this xmlns="mynamespace">
    <f:that xmlns:f="yournamespace">
    <or> a lot of random < </or>
    <f:the>
    </f:the>
    <f:other> foo bar blaz</f:other>
    </f:that>
    </this>
    </those>
    We get the following (notice the <document> tag around it):
    <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:Body>
    <m:echoDom xmlns:m="http://examples.org"
    env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
    <document>
    <those dummy="hi">
    <this xmlns="mynamespace">
    <f:that xmlns:f="yournamespace">
    <or> a lot of random < </or>
    <f:the>
    </f:the>
    <f:other> foo bar blaz</f:other>
    </f:that>
    </this>
    </those>
    </document>
    </m:echoDom>
    </env:Body>
    </env:Envelope>
    4. PROBLEM FOUR (just remembered this one):
    If we use the standard test page (provided with WLS), with (3) above,it
    chops
    off the "those" and it still wraps it within this new <document>
    element
    as show
    below:
    <!--REQUEST.................-->
    <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>
    <m:echoDom xmlns:m="http://examples.org"
    env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
    <document>
    <this xmlns="mynamespace">
    <f:that xmlns:f="yournamespace">
    <or> a lot of random < </or>
    <f:the>
    </f:the>
    <f:other> foo bar blaz</f:other>
    </f:that>
    </this>
    </document>
    </m:echoDom>
    </env:Body>
    </env:Envelope>
    We're not so worried about the fourth because it seems like a bug butthe
    first
    three (especially the first) are most important. Any ideas would beappreciated.
    Thanks
    sami

  • Problem in Jdeveloper 10.1.3, web services and document style.possible bug?

    Hello!
    I would like to generate a document-style web service from a wsdl file. The problem is that when I use it I get the following error:
    "operation echoStruct must have exactly one parameter as part of the SOAP body when used with a document-bare binding. All other parameters must be mapped to headers."
    A similar message is shown with other wsdl file that I'm using.
    I'm attaching the file that use to test it.
    Could you help me and tell me how I can fix it, please? or is it a bug?
    Regards,
    Antonio.
    <definitions xmlns:s1="http://soapinterop.org" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:s0="http://soapinterop.org/xsd" xmlns:s2="http://soapinterop.org/AbstractTypes" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://soapinterop.org">
         <types>
              <s:schema elementFormDefault="qualified" targetNamespace="http://soapinterop.org/xsd">
                   <s:import namespace="http://soapinterop.org"/>
                   <s:element name="echoStructParam" type="s0:SOAPStruct"/>
                   <s:complexType name="SOAPStruct">
                        <s:sequence>
                             <s:element minOccurs="1" maxOccurs="1" name="varFloat" type="s:float"/>
                             <s:element minOccurs="1" maxOccurs="1" name="varInt" type="s:int"/>
                             <s:element minOccurs="0" maxOccurs="1" name="varString" type="s:string"/>
                        </s:sequence>
                   </s:complexType>
                   <s:element name="echoStructReturn" type="s0:SOAPStruct"/>
                   <s:element name="echoStringArrayParam" type="s1:ArrayOfString"/>
                   <s:element name="string" type="s:string"/>
                   <s:element name="echoStringArrayReturn" type="s1:ArrayOfString"/>
                   <s:element name="echoStringParam" type="s:string"/>
                   <s:element name="echoStringReturn" type="s:string"/>
              </s:schema>
              <s:schema elementFormDefault="qualified" targetNamespace="http://soapinterop.org">
                   <s:import namespace="http://soapinterop.org/xsd"/>
                   <s:complexType name="ArrayOfString">
                        <s:sequence>
                             <s:element minOccurs="0" maxOccurs="unbounded" ref="s0:string"/>
                        </s:sequence>
                   </s:complexType>
                   <s:element name="ArrayOfString1" nillable="true" type="s1:ArrayOfString1"/>
                   <s:complexType name="ArrayOfString1">
                        <s:sequence>
                             <s:element minOccurs="0" maxOccurs="unbounded" name="string" nillable="true" type="s:string"/>
                        </s:sequence>
                   </s:complexType>
                   <s:element name="string" nillable="true" type="s:string"/>
              </s:schema>
              <s:schema targetNamespace="http://soapinterop.org/AbstractTypes">
                   <s:complexType name="StringArray">
                        <s:complexContent mixed="false">
                             <s:restriction base="soapenc:Array">
                                  <s:sequence>
                                       <s:element minOccurs="0" maxOccurs="unbounded" name="String" type="s:string"/>
                                  </s:sequence>
                             </s:restriction>
                        </s:complexContent>
                   </s:complexType>
              </s:schema>
         </types>
         <message name="echoStructSoapIn">
              <part name="echoStructParam" element="s0:echoStructParam"/>
         </message>
         <message name="echoStructSoapOut">
              <part name="echoStructResult" element="s0:echoStructReturn"/>
         </message>
         <message name="echoStringArraySoapIn">
              <part name="echoStringArrayParam" element="s0:echoStringArrayParam"/>
         </message>
         <message name="echoStringArraySoapOut">
              <part name="echoStringArrayResult" element="s0:echoStringArrayReturn"/>
         </message>
         <message name="echoStringSoapIn">
              <part name="echoStringParam" element="s0:echoStringParam"/>
         </message>
         <message name="echoStringSoapOut">
              <part name="echoStringResult" element="s0:echoStringReturn"/>
         </message>
         <portType name="WSDLInteropTestDocLitSoap">
              <operation name="echoStruct">
                   <input message="s1:echoStructSoapIn"/>
                   <output message="s1:echoStructSoapOut"/>
              </operation>
              <operation name="echoStringArray">
                   <input message="s1:echoStringArraySoapIn"/>
                   <output message="s1:echoStringArraySoapOut"/>
              </operation>
              <operation name="echoString">
                   <input message="s1:echoStringSoapIn"/>
                   <output message="s1:echoStringSoapOut"/>
              </operation>
         </portType>
         <binding name="WSDLInteropTestDocLitSoap" type="s1:WSDLInteropTestDocLitSoap">
              <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
              <operation name="echoStruct">
                   <soap:operation soapAction="http://soapinterop.org/" style="document"/>
                   <input>
                        <soap:body use="literal"/>
                   </input>
                   <output>
                        <soap:body use="literal"/>
                   </output>
              </operation>
              <operation name="echoStringArray">
                   <soap:operation soapAction="http://soapinterop.org/" style="document"/>
                   <input>
                        <soap:body use="literal"/>
                   </input>
                   <output>
                        <soap:body use="literal"/>
                   </output>
              </operation>
              <operation name="echoString">
                   <soap:operation soapAction="http://soapinterop.org/" style="document"/>
                   <input>
                        <soap:body use="literal"/>
                   </input>
                   <output>
                        <soap:body use="literal"/>
                   </output>
              </operation>
         </binding>
         <service name="WSDLInteropTestDocLit">
              <port name="WSDLInteropTestDocLitSoap" binding="s1:WSDLInteropTestDocLitSoap">
                   <soap:address location="http://mssoapinterop.org/asmx/wsdl/InteropTestDocLit.asmx"/>
              </port>
         </service>
    </definitions>

    Dev update: WSDL file seems fine. The problem is that it's for a document-bare service and, by default, the Unwrap Wrapped Parameters option on step 2 of the top-down wizard is enabled and checked. This means that we try to pick apart the input message into a series of parameters, yielding the error shown because a document-bare operation must have only one input parameter.
    If the Unwrap Wrapped Parameters option is unchecked, creation of the top-down service will succeed. In future, we ought to disable the option completely for everything but document-wrapped services, as that's the only time it applies.
    This is covered by bug 4630382.

  • How to call a webservice with SOAP Binding Style RPC

    Hi Guys,
    I'm pretty new to the LiveCycle ES product and I'm trying to call a web service that is of SOAP binding style 'RPC'. After some research I found out that Adobe LC ES only support WSDL files of doc/literal type.
    My question is, is there a workaround for calling RPC style web services? can RPC style web services be converted into doc/literal type?
    Any information regarding this would be greatly appreciated.
    Kazz.

    Hello,
    I had the same problem and I've regenerated my WSDL ( Apache Axis ) with docu/litteral parameters.
    I think it's the only way...
    thomas

  • AxisFault seen while invoking document style web service

    I am seeing the following stacktrace when I try to invoke a document-style web service.
    <partnerRole name="MyWebService1_Role">
    <ServiceName>{http://idm.oracle.com/}MyWebService1</ServiceName>
    <PortType>{http://idm.oracle.com/}MyWebService1</PortType>
    <Address>null</Address>
    </partnerRole>
    <conversationId>bpel://localhost/default/ProvisioningFromDAS~1.0/4202-BpInv0-BpSeq0.3-3</conversationId>
    <properties>{}</properties>
    </partnerLink>
    <2005-09-06 09:23:37,650> <DEBUG> <default.collaxa.cube.ws> <WSIFInvocationHandler::invoke> Fault happened
    AxisFault
    faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Client
    faultSubcode:
    faultString: caught exception while handling request: expected element is missing: {http://idm.oracle.com/}attribute
    faultActor:
    faultNode:
    faultDetail:
    {http://xml.apache.org/axis/}stackTrace:caught exception while handling request: expected element is missing: {http://idm.oracle.com/}attribute
    at org.collaxa.thirdparty.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:221)
    at org.collaxa.thirdparty.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:128)
    at org.collaxa.thirdparty.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1083)
    at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
    at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)
    at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
    at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
    What could this mean ?

    Hi,
    I am getting a similar issue. I created a Document-style/literal webservice and deployed on Weblogic 9.2 . Then I generated client stubs using clientgen. I get the following exception stack trace:
    java.rmi.RemoteException: web service invoke failed: javax.xml.soap.SOAPException:
    failed to serialize class java.lang.Objectweblogic.xml.schema.binding.SerializationException: type mapping lookup failure on
    class=class com.sun.org.apache.xerces.internal.dom.DeferredDocumentImpl TypeMapping=TYPEMAPPING SIZE=3
    ENTRY 1:
    class: java.lang.Object
    xsd_type: ['http://xmlns.ozarkexpress.com/business/sell']:stns:echoDocumentResponse
    ser: weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec@1125127
    deser: weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec@18dfef8
    ENTRY 2:
    class: java.lang.Object
    xsd_type: ['http://xmlns.ozarkexpress.com/business/sell']:stns:echoDocument
    ser: weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec@15e83f9
    deser: weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec@2a5330
    ENTRY 3:
    class: java.lang.Object
    xsd_type: ['http://www.w3.org/2001/XMLSchema']:xsd:anyType
    ser: weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec@bb7465
    deser: weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec@d6c16c

  • SOAP adapter engine with system error, problem with fault message.

    HI,
    I have IDOC -> PI -> SOAP scenario.
    Idoc to PI is async. I have no problem in receiving the idoc in PI. The message mapping is carried out and sent to the adapter engine. I can also see the technical routing payload. It is sucessful at XML monitoring in SXMB_MONI.
    The error is at PI -> SOAP.
    I have wsdl provided by the receiver webservice. Which I have imported.
    And created a service interface against this wsdl. I tried changing it to both sync and async.
    I have also provided fault message.
    I have set a receiver soap communication channel and provided the target URL like "http://xxx/services" and soap
    action = processDocument. Also provided user id and password.
    I have a
    Sender Agreement
    Receiver determination
    Interface determination
    Receiver Agreement
    I check in RWB adapter engine, this message goes to system error. The error log is as shown at the bottom.
    When I see the message content, the SOap document shows me the details about IDOC, Instead I feel it should match
    with the wsdl, where they have specified the corresponding interface name and address location etc.Please correct me.
    How does the receiver know which service interface is it? The Service Interface which I created in the ER is
    different from the WSDL, Does this have to be same? I see that the soap document in the adapter engine has the
    Service interface name which I created in the  ER. Where in the document the Reciever interface name is sent?
    Where can I see the generated soap document for the receiver?
    Is there some setting/configuration required in PI for this to work?
    I tried using the tcpgw to see the error. If I dont provide the service interface name in the communication channel
    then I get the following error in the TCPGW. "The service cannot be found for the endpoint reference"
    When I provide the service interface name in the communication channel I get a valid fault message.
    Similarly
    When I use SOAPUI, I can see the fault exception being return. The adapter engine doesnot show an equivalent message
    instead it goes into system error as shown at the bottom. I guess this is expected, if so what is the work around? (I found this weblog /people/alessandro.guarneri/blog/2011/01/10/soap-fault-in-sap-pi-hijack-it, do I need to implement this? Or use ALEAUD?
    The fault message what I see in SOAPUI has the below format.
    <soapenv:Fault xmlns:axis2ns1="http://schemas.xmlsoap.org/soap/envelope/">
             <faultcode>axis2ns1:Server</faultcode>
             <faultstring>nested exception is: psdi.util.MXApplicationException: BMXAA7136E - Validation failed when the
                                database default values were set. See the associated message for more information.
               BMXAA4190E - Country NZ is not in the value list.</faultstring>
             <detail>
                <Exception>org.apache.axis2.AxisFault: nested exception is: psdi.util.MXApplicationException: BMXAA7136E
                          - Validation failed when the database default values were set. See the associated message for more information.
         BMXAA4190E - Country NZ is not in the value list.
                /Exception>
             </detail>
      </soapenv:Fault>
    And the fault message in my ER service interface is stanadard datatype ExchangeFaultData, which is different from
    the above. Is this the problem? Can I change the data type here to be the same as above?
    Audit log in the RWB adapter engine.
    Time Stamp Type Description
    30.09.2011 15:10:57 Information MP: processing local module Localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
    30.09.2011 15:10:57 Information SOAP: request message entering the adapter with user J2EE_GUEST
    30.09.2011 15:10:57 Information SOAP: completed the processing
    30.09.2011 15:10:57 Information SOAP: sending a delivery error ack ...
    30.09.2011 15:10:57 Information SOAP: sent a delivery error ack
    30.09.2011 15:10:57 Error MP: exception caught with cause
    com.sap.engine.interfaces.messaging.api.exception.MessagingException
    30.09.2011 15:10:57 Error Adapter Framework caught exception: null
    30.09.2011 15:10:57 Error Delivering the message to the application using connection
    SOAP_http://sap.com/xi/XI/System failed, due to:
    com.sap.engine.interfaces.messaging.api.exception.MessagingException.
    30.09.2011 15:10:57 Information The message status was set to WAIT.
    30.09.2011 15:10:57 Information The asynchronous message was successfully scheduled to be delivered at Fri Sep 30
    15:15:57 NZDT 2011.

    I tried changing it to both sync and async.
    I have also provided fault message.
    dont feel that you need to do above steps.
    I have a
    Sender Agreement
    ideally you dont need a sender agreement (and a channel) for IDOC --> PI flow.
    When I see the message content, the SOap document shows me the details about IDOC
    this is fine...you may see fields as seen in EDI_DC40 of the IDOC...
    How does the receiver know which service interface is it?
    receiver need not know about the SI created in PI.
    The Service Interface which I created in the ER is
    different from the WSDL, Does this have to be same?
    you should the WSDL (external definition) as the Request Message in your service interface.
    Is there some setting/configuration required in PI for this to work?
    nothing specific...AFAIK
    I have set a receiver soap communication channel and provided the target URL like "http://xxx/services" and soap action
    can you open the URL from Internet explorer...from your machine or from the machine which is in the same network as your PI server?
    Things to check:
    WSDL structure in PI and in target system is exactly the same.
    does the target system require mesage in SOAP format (SOAP envelope - SOAP Header + SOAP body)?
    target system is up and running?

  • Trouble Communicating with Document-Style Web Service

    I have a flash app that currently communicates with a
    RPC-style web service. I changed the web service to be
    document-style, and the flash app no longer sends valid requests. I
    was under the impression that one could simple swtich styles, and
    flash would play along. Apparently, this is not the case. Does
    anyone have an insight in this area?

    Clarified with Partick Calahan, who is maintaining this tool.
    Currently, doc style is not handled by this tool. I guess it will be
    supported in the future.
    Thanks.
    "Karthik V" <[email protected]> wrote in message
    news:[email protected]..
    I'm using WebLogic Webservice Explorer v.02 (WEX).
    I'm able to test rpc style web services without any problem.
    But whenever I try to open a document style web service WSDL, I get the
    following exception.
    I would appreciate if you have any suggestions for the to over come this
    issue.
    java.lang.IllegalArgumentException at
    weblogic.webservice.tools.wex.MessagePanel.<init>(MessagePanel.java:33)at
    >
    weblogic.webservice.tools.wex.ServicePanel.operationChanged(ServicePanel.jav
    a:153) at
    weblogic.webservice.tools.wex.ServicePanel.portChanged(ServicePanel.java:133
    ) at
    weblogic.webservice.tools.wex.ServicePanel.serviceChanged(ServicePanel.java:
    121) at
    weblogic.webservice.tools.wex.ServicePanel.<init>(ServicePanel.java:69)at
    >
    weblogic.webservice.tools.wex.tasks.FetchWsdlTask.perform(FetchWsdlTask.java
    :45) at
    weblogic.webservice.tools.wex.tasks.TaskQueue.run(TaskQueue.java:47) at
    java.lang.Thread.run(Unknown Source)

  • Problem deploying document style web service(urgent help required)

    I am getting this particular exception on my browser when I am trying to view the list of services after having deployed the service. The exception and complete stack trace is follows. I have also included the portion of the WSDD file giving details about the service.
    And now... Some Services
    AXIS error
    Sorry, something seems to have gone wrong... here are the details:
    Exception - org.apache.axis.ConfigurationException: java.lang.ClassCastException
    java.lang.ClassCastException
         at org.apache.axis.deployment.wsdd.WSDDDeployableItem.makeNewInstance(WSDDDeployableItem.java:302)
         at org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableItem.java:274)
         at org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem.java:260)
         at org.apache.axis.deployment.wsdd.WSDDDeployment.getHandler(WSDDDeployment.java:394)
         at org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableItem.java:276)
         at org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem.java:260)
         at org.apache.axis.deployment.wsdd.WSDDChain.makeNewInstance(WSDDChain.java:125)
         at org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableItem.java:274)
         at org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem.java:260)
         at org.apache.axis.deployment.wsdd.WSDDService.makeNewInstance(WSDDService.java:430)
         at org.apache.axis.deployment.wsdd.WSDDDeployment.getDeployedServices(WSDDDeployment.java:503)
         at org.apache.axis.configuration.FileProvider.getDeployedServices(FileProvider.java:296)
         at org.apache.axis.transport.http.AxisServlet.reportAvailableServices(AxisServlet.java:482)
         at org.apache.axis.transport.http.AxisServlet.doGet(AxisServlet.java:260)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:260)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
         at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
         at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415)
         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
         at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
         at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
         at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:432)
         at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:386)
         at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:534)
         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:530)
         at java.lang.Thread.run(Thread.java:534)
    org.apache.axis.ConfigurationException: java.lang.ClassCastException
    java.lang.ClassCastException
         at org.apache.axis.deployment.wsdd.WSDDDeployableItem.makeNewInstance(WSDDDeployableItem.java:302)
         at org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableItem.java:274)
         at org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem.java:260)
         at org.apache.axis.deployment.wsdd.WSDDDeployment.getHandler(WSDDDeployment.java:394)
         at org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableItem.java:276)
         at org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem.java:260)
         at org.apache.axis.deployment.wsdd.WSDDChain.makeNewInstance(WSDDChain.java:125)
         at org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableItem.java:274)
         at org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem.java:260)
         at org.apache.axis.deployment.wsdd.WSDDService.makeNewInstance(WSDDService.java:430)
         at org.apache.axis.deployment.wsdd.WSDDDeployment.getDeployedServices(WSDDDeployment.java:503)
         at org.apache.axis.configuration.FileProvider.getDeployedServices(FileProvider.java:296)
         at org.apache.axis.transport.http.AxisServlet.reportAvailableServices(AxisServlet.java:482)
         at org.apache.axis.transport.http.AxisServlet.doGet(AxisServlet.java:260)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:260)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
         at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
         at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415)
         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
         at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
         at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
         at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:432)
         at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:386)
         at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:534)
         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:530)
         at java.lang.Thread.run(Thread.java:534)
         at org.apache.axis.deployment.wsdd.WSDDDeployableItem.makeNewInstance(WSDDDeployableItem.java:304)
         at org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableItem.java:274)
         at org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem.java:260)
         at org.apache.axis.deployment.wsdd.WSDDDeployment.getHandler(WSDDDeployment.java:394)
         at org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableItem.java:276)
         at org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem.java:260)
         at org.apache.axis.deployment.wsdd.WSDDChain.makeNewInstance(WSDDChain.java:125)
         at org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableItem.java:274)
         at org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem.java:260)
         at org.apache.axis.deployment.wsdd.WSDDService.makeNewInstance(WSDDService.java:430)
         at org.apache.axis.deployment.wsdd.WSDDDeployment.getDeployedServices(WSDDDeployment.java:503)
         at org.apache.axis.configuration.FileProvider.getDeployedServices(FileProvider.java:296)
         at org.apache.axis.transport.http.AxisServlet.reportAvailableServices(AxisServlet.java:482)
         at org.apache.axis.transport.http.AxisServlet.doGet(AxisServlet.java:260)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:260)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
         at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
         at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415)
         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
         at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
         at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
         at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:432)
         at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:386)
         at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:534)
         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:530)
         at java.lang.Thread.run(Thread.java:534)
    The snippet from the WSDD is as follows:
    <handler name="RequestHandler" type="java:com.doc.service.DataHandler"/>
    <service name="AddCalcService" provider="java:MSG">
    <parameter name="allowedMethods" value="*"/>
    <parameter name="className" value="com.doc.service.AddCalcService"/>
    <requestFlow>     
         <handler type="RequestHandler"/>
    </requestFlow>
    <responseFlow>
         <handler type="RequestHandler"/>
    </responseFlow>
    </service>
    Could someone tell what the cause of this exception and how it could be resolved.

    Hi Bruce,
    Thanks for all the links - am trudging through them now.
    -Leena
    Bruce Stephens <[email protected]> wrote:
    Hi Lenna,
    You might take a look at the SOAPBuilders interop tests.
    See: http://www.whitemesa.com/r3/interop3.html and notice the DocLit
    tests.
    Our endpoints are http://webservice.bea.com:7001 and the code for the
    client and servers can be located here:
    http://webservice.bea.com/index.html#qz40
    The good folks with WS-I have spent many cycles on interop issues. You
    might have a look at their work:
    http://www.ws-i.org/Profiles/Basic/2003-08/BasicProfile-1.0a.html
    Hope this is of some value,
    Bruce
    leena wrote:
    Hi,
    I am trying to build a synchronous document-style web service, andthe bea
    site doesnt seem to have much documentation on it. I have a samplewritten with
    SOAPElement as the input and output of my method, no schemas, my reqand response
    are anyType, but im not sure if that is the best way to go. AND, itdoesnt work
    yet.
    Can anyone point me to a place where i can look for information ?i am on weblogic
    8.1. I would eventually also want my input/output xml to be definedby my schema.
    I see in examples that DOM Documents may also be passed as parameters(inand out)
    ? is there any place i can read up on this and decide what the bestoption for
    me is ? Also, i will be running a .Net client against this, so if thereis anything
    i need to keep in mind, i would appreciate it if anyone gave me anyinfo.
    Thanks in advance!
    leena.

  • Faults with document style operation

    I am getting the following error when attempting to generate stubs from my WSDL:
    warning: ignoring fault "TestError" of document-style operation "testOperationWithFault"
    Are faults not supported for document-style operations or is my WSDL incorrect. (I was able to succesfully generate stubs with exceptions with this same WSDL using Apache Axis).
    Also, you can see that I have commented out the attribute elements on my complex type definition. It seems that when I use attributes the generated stub has methods that take a javax.xml.soap.SOAPElement as an argument instead of an object of type TestInputType. Does the Sun wscompile tool not support attributes or again, is my WSDL incorrect?
    Thanks.
    Here is my test WSDL:
    <?xml version="1.0"?>
    <definitions
    targetNamespace="http://www.convergys.com/services/Test"
    xmlns:tns="http://www.convergys.com/services/Test"
              xmlns:xsd="http://www.w3.org/2001/XMLSchema"
              xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
              xmlns="http://schemas.xmlsoap.org/wsdl/">
    <types>
    <xsd:schema targetNamespace="http://www.convergys.com/services/Test">
         <xsd:simpleType name="ReportingLevel">
              <xsd:restriction base="xsd:string">
                   <xsd:enumeration value="S" />
              <xsd:enumeration value="D" />
              <xsd:enumeration value="M" />
              <xsd:enumeration value="" />
              </xsd:restriction>
         </xsd:simpleType>
    <xsd:element name="inputTest" type="tns:TestInputType" />
    <xsd:complexType name="TestInputType">
    <!--
              <xsd:attribute name="sbscrpId" type="xsd:string"
    use="required" />
              <xsd:attribute name="effDt" type="xsd:date" use="required" />
    -->
    <xsd:all>
    <xsd:element name="user" type="xsd:string" />
    <xsd:element name="passwd" type="xsd:string" />
    <xsd:element name="auditId" type="xsd:string"
    minOccurs="0" />
    <xsd:element name="intAttr" type="xsd:int" />
    <xsd:element name="shortAttr" type="xsd:short" />
    <xsd:element name="booleanAttr" type="xsd:boolean" />
    <xsd:element name="dateTimeAttr" type="xsd:dateTime" />
    <xsd:element name="dateAttr" type="xsd:date"/>
    <xsd:element name="base64BinaryAttr" type="xsd:base64Binary" />
    <xsd:element name= "anyAttr" type="xsd:anyType"
    minOccurs="0" maxOccurs="1" />
    <xsd:element name= "enumAttr" type="tns:ReportingLevel" />
    </xsd:all>
    </xsd:complexType>
    <xsd:element name="outputTest" type="tns:TestOutputType" />
    <xsd:complexType name="TestOutputType">
    <xsd:all>
    <xsd:element name="token" type="xsd:string" />
    <xsd:element name="roleUserId" type="xsd:string"
    minOccurs="0" />
    </xsd:all>
    </xsd:complexType>
    </xsd:schema>
    </types>
    <message name="TestRequest">
    <part name="parameters" element="tns:inputTest" />
    </message>
    <message name="TestResponse">
    <part name="result" element="tns:outputTest" />
    </message>
    <!--
    -->
    <message name="TestError">
    <part name="errorString" type="xsd:string" />
    </message>
    <portType name="MyServicePort">
    <operation name="testOperation">
    <input message="tns:TestRequest" />
    <output message="tns:TestResponse" />
    </operation>
    <!--
    -->
    <operation name="testOperationWithFault">
    <input message="tns:TestRequest" />
    <output message="tns:TestResponse" />
    <fault name="TestError" message="tns:TestError" />
    </operation>
    </portType>
    <binding name="MyServiceSOAPBinding" type="tns:MyServicePort">
    <soap:binding transport="http://schemas.xmlsoap.org/soap/http"
    style="document" />
    <operation name="testOperation">
    <soap:operation soapAction="" />
    <input>
    <soap:body use="literal" />
    </input>
    <output>
    <soap:body use="literal" />
    </output>
    </operation>
    <!--
    -->
    <operation name="testOperationWithFault">
    <soap:operation soapAction=""/>
    <input>
    <soap:body use="literal" />
    </input>
    <output>
    <soap:body use="literal" />
    </output>
    <fault name="TestError">
    <soap:fault name="TestError" use="literal" />
    </fault>
    </operation>
    </binding>
    <service name="MyServiceService">
    <port name="MyServicePort" binding="tns:MyServiceSOAPBinding">
    <soap:address location="http://azure:15481/MyTestWebApp/mysnoop" />
    </port>
    </service>
    </definitions>

    msauer, the JAXRPC-RI does not support faults in document/literal. JAXRPC does not support the xsd:date type, that is why you are getting SOAPElement. If you change this to be xsd:dateTime it should work for you.

  • Problems invoking SOAP method

    Greetings,
    Im having some problems invoking a .net web service from
    CFMX7. I have a service that is supposed to create a user.
    i've also tried passing the createuser method jusy
    MyNewUser.User as well with a similar result.

    This is the SOAP request
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:pub="http://xmlns.oracle.com/oxp/service/PublicReportService">
    <soapenv:Header/>
    <soapenv:Body>
    <pub:scheduleReport>
    <pub:scheduleRequest>
    <pub:deliveryRequest>
    <pub:emailOption>
    <pub:emailBody>testing whether BI publisher sends pdf file</pub:emailBody>
    <pub:emailFrom>[email protected]</pub:emailFrom>
    <pub:emailSubject>Sending Train cert from SoapUI</pub:emailSubject>
    <pub:emailTo>[email protected]</pub:emailTo>
    </pub:emailOption>
    </pub:deliveryRequest>
    <pub:notificationTo>[email protected]</pub:notificationTo>
    <pub:notifyWhenFailed>true</pub:notifyWhenFailed>
    <pub:notifyWhenSuccess>false</pub:notifyWhenSuccess>
    <pub:notifyWhenWarning>false</pub:notifyWhenWarning>
    <pub:reportRequest>
    <pub:attributeFormat>pdf</pub:attributeFormat>
              <pub:parameterNameValues>
    <!--Zero or more repetitions:-->
    <pub:item>
    <pub:multiValuesAllowed>true</pub:multiValuesAllowed>
    <pub:name>NAME</pub:name>
    <pub:values>
    <!--Zero or more repetitions:-->
    <pub:item>Kavitha</pub:item>               
    </pub:values>
    </pub:item>
    </pub:parameterNameValues>
    <pub:reportAbsolutePath>/TrainCert/TrainCert.xdo</pub:reportAbsolutePath>
    </pub:reportRequest>
    <pub:useUTF8Option>true</pub:useUTF8Option>
    <pub:userJobName>TrainCert</pub:userJobName>
    </pub:scheduleRequest>
    <pub:userID></pub:userID>
    <pub:password></pub:password>
    </pub:scheduleReport>
    </soapenv:Body>
    </soapenv:Envelope>
    Edited by: user6790640 on Feb 15, 2010 6:07 AM

  • I downloaded the 09 version without deleting the 0, and now I am having some problems : when I open a document, it opens with 09, and then when I try to re-open it with 08 it is not possible !

    I downloaded the 09 version without deleting the 08 (didn't know), and now I am having some problems : when I open a document, it opens with 09, and then when I try to re-open it with 08 it is not possible ! I have a message saying tha "the fichier index xml is absent" (my computer is in French. I want to work with pages 08 until I get familiar with the 09 version. What shall I do ? What does this happen?

    Once you open the files in the new version you can't open them in the old version. Pick one version to use (have to be 9 now as you already have converted files)

  • When I send open office documents to a PC user (even saved and sent in the word format), the document reaches with serious format changes and is rendered unusable to the PC user. How to overcome the problem??

    When I send open office documents to a PC user (even saved and sent in the word format), the document reaches with serious format changes and is rendered unusable to the PC user. How to overcome the problem??

    I don't use OpenOffice (I have it on my internal just to play around with, but seldom even open it). I do use MS Word and have few problems sharing files - it's usually a font issue so I tend to use MS fonts for documents that I know will need to be shared.
    Unless you need to make collaborative changed to the document, you could always save it as a pdf file. With Acrobat Pro you can even save a pdf file to a Word document with very little change in formatting.
    If I were you - and you have a need for .doc or .docx files to travel and play nicely - I'd just invest in MS Office. If you don't have to send a Word file, try pdf.
    Clinton

  • Problem in Web service - document style

    Hi,
    I want to create document style webservices using axis tool.
    so i need any sample codes and procedure for creating document style web services using axis tool . If any one help me in regarding this i will be thankfull to u.
    regards
    tuty.richard

    WSADMIN transaction is obsolete from SAP NetWeaver AS 7.00, SP14. and help documentation says following: The same you can get it from information pop-up.
    Start of Help Doc***************
    From SAP NetWeaver AS 7.00, SP14, new service definitions in the ABAP development environment are no longer administered using transactions WSADMIN and WSCONFIG.
    The transactions WSADMIN and WSCONFIG will remain active until all old web service configurations have been migrated, which means you can continue to configure web services from SAP NetWeaver AS 6.40, 7.00, and web service definitions from the XI 3.0 environment. You can also continue to access the runtime configurations of old service definitions using these transactions.
    However, new service definitions created in the ABAP development environment will be hidden in these transactions.
    End of Help Doc***************
    So, You have to use SOAMANAGER transaction if your release is more than whatever specified above.
    Regards,
    Siva.

Maybe you are looking for

  • FTP question for newbie -- How to access external volume?

    I have set up an old Mac (running Tiger) as a server on my LAN; attached to this Mac are several Firewire disks. I want to use FTP (with retrospect Express) to automatically back up from another computer to these disks. I can successfuly mount these

  • Changing BP data to different tabs in transaction BP

    Hi everyone, I'm trying to swap around some data in the bp screen. Mainly, when an account is entered I want some of the information that I currently have showing up under a tab 'marketing attributes' to show in a different tab 'customers', which I a

  • Products are not visible in webshop

    Hi all, i have created a product catalog,variants,views and assigned the products activated at all levels.To the view of the product catalog i have assigned Target group. and also i have initial replicated the same to Index server.Then i went to webs

  • Make imported jpg in Ai CS5 have transparent background instead of white

    I have been looking around the forums and help pages, but I can not seem to find my answer.  Maybe I am using the wrong terminology? In Adobe Illustrator CS5 I have imported a jpg into my artboard.  The jpg has a white background.  I would like to ma

  • I can't publish - iWeb crashes every time I try

    For the past 3 days, each time I try to publish, iWeb begins republishing all the pages and then just quits. I have been using the program for many months now and everything was fine. I added a lot of new photos. Could that be the problem? As far as