• RELEVANCY SCORE 5.57

    DB:5.57:Dii Call With Literal Xsi In Soap Request 9f






    I've got a DII client with:

    call.setProperty(Call.ENCODINGSTYLE_URI_PROPERTY, "");
    call.setOperationName(new QName(NS_URI, "myService"));
    call.addParameter("arrayOfbyte_1", XSD_BYTEARRAYB64, ParameterMode.IN);
    ...
    call.invoke(new Object[]{myValue});
    ...

    DB:5.57:Dii Call With Literal Xsi In Soap Request 9f


    A generated proxy is configured from the WSDl, which contains the style/use of the WS. There should be no additional configuration needed.

  • RELEVANCY SCORE 2.95

    DB:2.95:Using Soapelement With Dii ck





    Hi All,

    I would like use the DII interface of jax-rpc. I am using document/literal WebServices.

    Instead of providing the JAVA wrapper classes I would like to pass a SOAPElement to the CALL object and get a SOAPElement back.

    The jax-rpc spec says that the the jax-rpc implementations must provide a switch to allow using SOAPElements.

    For JWSDP 1.6: What exactly do I have to set in which class to use SOAPElements?

    Does anyone know how to do this?

    Best Regards,
    chzim

    DB:2.95:Using Soapelement With Dii ck

    Hi All,

    I would like use the DII interface of jax-rpc. I am using document/literal WebServices.

    Instead of providing the JAVA wrapper classes I would like to pass a SOAPElement to the CALL object and get a SOAPElement back.

    The jax-rpc spec says that the the jax-rpc implementations must provide a switch to allow using SOAPElements.

    For JWSDP 1.6: What exactly do I have to set in which class to use SOAPElements?

    Does anyone know how to do this?

    Best Regards,
    chzim

  • RELEVANCY SCORE 2.91

    DB:2.91:Calling Static Ws Dynamicaly (Dii) In Jax-Ws 2.0 f8





    Hello,

    is it possible to call static (stub generated) web service by using DII client?

    Thanks

    DB:2.91:Calling Static Ws Dynamicaly (Dii) In Jax-Ws 2.0 f8

    I am not sure I understand your question, but JAX-WS 2.0 defines a Dispatch interface that can be used to dynamically invoke a web service. Check out the JAX-WS documenatation (http://jax-ws.dev.java.net).

  • RELEVANCY SCORE 2.82

    DB:2.82:Soap Over Jms Problem s1


    I'm trying to call a SOAP over JMS Service form the BPEL process manager. For a simple example I use the Apache CXF example with Active MQ. The service has the following WSDL:

    ?xml version="1.0" encoding="UTF-8"?
    wsdl:definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:jms="http://cxf.apache.org/transports/jms" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://cxf.apache.org/jms_greeter" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:x1="http://cxf.apache.org/jms_greeter/types" name="JMSGreeterService" targetNamespace="http://cxf.apache.org/jms_greeter"
    wsdl:types
    schema targetNamespace="http://cxf.apache.org/jms_greeter/types" xmlns="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified"
    element name="sayHi"
    complexType/
    /element
    element name="sayHiResponse"
    complexType
    sequence
    element name="responseType" type="xsd:string"/
    /sequence
    /complexType
    /element
    element name="greetMe"
    complexType
    sequence
    element name="requestType" type="xsd:string"/
    /sequence
    /complexType
    /element
    element name="greetMeResponse"
    complexType
    sequence
    element name="responseType" type="xsd:string"/
    /sequence
    /complexType
    /element
    element name="greetMeOneWay"
    complexType
    sequence
    element name="requestType" type="xsd:string"/
    /sequence
    /complexType
    /element
    /schema
    /wsdl:types
    wsdl:message name="sayHiRequest"
    wsdl:part name="in" element="x1:sayHi"/
    /wsdl:message
    wsdl:message name="sayHiResponse"
    wsdl:part name="out" element="x1:sayHiResponse"/
    /wsdl:message
    wsdl:message name="greetMeRequest"
    wsdl:part name="in" element="x1:greetMe"/
    /wsdl:message
    wsdl:message name="greetMeResponse"
    wsdl:part name="out" element="x1:greetMeResponse"/
    /wsdl:message
    wsdl:message name="greetMeOneWayRequest"
    wsdl:part name="in" element="x1:greetMeOneWay"/
    /wsdl:message
    wsdl:portType name="JMSGreeterPortType"
    wsdl:operation name="sayHi"
    wsdl:input name="sayHiRequest" message="tns:sayHiRequest"/
    wsdl:output name="sayHiResponse" message="tns:sayHiResponse"/
    /wsdl:operation
    wsdl:operation name="greetMe"
    wsdl:input name="greetMeRequest" message="tns:greetMeRequest"/
    wsdl:output name="greetMeResponse" message="tns:greetMeResponse"/
    /wsdl:operation
    wsdl:operation name="greetMeOneWay"
    wsdl:input name="greetMeOneWayRequest" message="tns:greetMeOneWayRequest"/
    /wsdl:operation
    /wsdl:portType
    wsdl:binding name="JMSGreeterPortBinding" type="tns:JMSGreeterPortType"
    soap:binding style="document" transport="http://cxf.apache.org/transports/jms"/
    wsdl:operation name="greetMe"
    soap:operation soapAction="" style="document"/
    wsdl:input name="greetMeRequest"
    soap:body use="literal"/
    /wsdl:input
    wsdl:output name="greetMeResponse"
    soap:body use="literal"/
    /wsdl:output
    /wsdl:operation
    wsdl:operation name="sayHi"
    soap:operation soapAction="" style="document"/
    wsdl:input name="sayHiRequest"
    soap:body use="literal"/
    /wsdl:input
    wsdl:output name="sayHiResponse"
    soap:body use="literal"/
    /wsdl:output
    /wsdl:operation
    wsdl:operation name="greetMeOneWay"
    soap:operation style="document" soapaction=""/
    wsdl:input name="greetMeOneWayRequest"
    soap:body use="literal"/
    /wsdl:input
    /wsdl:operation
    /wsdl:binding
    wsdl:service name="JMSGreeterService"
    wsdl:port name="GreeterPort" binding="tns:JMSGreeterPortBinding"
    jms:address destinationStyle="queue" jndiConnectionFactoryName="ConnectionFactory" jndiDestinationName="dynamicQueues/test.cxf.jmstransport.queue"
    jms:JMSNamingProperty name="java.naming.factory.initial" value="org.apache.activemq.jndi.ActiveMQInitialContextFactory"/
    jms:JMSNamingProperty name="java.naming.provider.url" value="tcp://localhost:61616"/
    /jms:address
    jms:clientConfig useConduitIdSelector="false"/
    /wsdl:port
    /wsdl:service
    /wsdl:definitions

    When trying to call the service i get the follwing errror:

    messages
    input
    Invoke_2_greetMeOneWay_InputVariable
    part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="in"
    greetMeOneWay xmlns="http://cxf.apache.org/jms_greeter/types"
    requestType
    sdfsdf!
    /requestType
    /greetMeOneWay
    /part
    /Invoke_2_greetMeOneWay_InputVariable
    /input
    fault
    bindingFault xmlns="http://schemas.oracle.com/bpel/extension"
    part name="summary"
    summary
    Unable to find an available port
    /summary
    /part
    /bindingFault
    /fault
    /messages

    When using a JMS Adapter Service i can access the queue without any problems.

    Any ideas? Thanks!

    DB:2.82:Soap Over Jms Problem s1

    I'm trying to call a SOAP over JMS Service form the BPEL process manager. For a simple example I use the Apache CXF example with Active MQ. The service has the following WSDL:

    ?xml version="1.0" encoding="UTF-8"?
    wsdl:definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:jms="http://cxf.apache.org/transports/jms" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://cxf.apache.org/jms_greeter" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:x1="http://cxf.apache.org/jms_greeter/types" name="JMSGreeterService" targetNamespace="http://cxf.apache.org/jms_greeter"
    wsdl:types
    schema targetNamespace="http://cxf.apache.org/jms_greeter/types" xmlns="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified"
    element name="sayHi"
    complexType/
    /element
    element name="sayHiResponse"
    complexType
    sequence
    element name="responseType" type="xsd:string"/
    /sequence
    /complexType
    /element
    element name="greetMe"
    complexType
    sequence
    element name="requestType" type="xsd:string"/
    /sequence
    /complexType
    /element
    element name="greetMeResponse"
    complexType
    sequence
    element name="responseType" type="xsd:string"/
    /sequence
    /complexType
    /element
    element name="greetMeOneWay"
    complexType
    sequence
    element name="requestType" type="xsd:string"/
    /sequence
    /complexType
    /element
    /schema
    /wsdl:types
    wsdl:message name="sayHiRequest"
    wsdl:part name="in" element="x1:sayHi"/
    /wsdl:message
    wsdl:message name="sayHiResponse"
    wsdl:part name="out" element="x1:sayHiResponse"/
    /wsdl:message
    wsdl:message name="greetMeRequest"
    wsdl:part name="in" element="x1:greetMe"/
    /wsdl:message
    wsdl:message name="greetMeResponse"
    wsdl:part name="out" element="x1:greetMeResponse"/
    /wsdl:message
    wsdl:message name="greetMeOneWayRequest"
    wsdl:part name="in" element="x1:greetMeOneWay"/
    /wsdl:message
    wsdl:portType name="JMSGreeterPortType"
    wsdl:operation name="sayHi"
    wsdl:input name="sayHiRequest" message="tns:sayHiRequest"/
    wsdl:output name="sayHiResponse" message="tns:sayHiResponse"/
    /wsdl:operation
    wsdl:operation name="greetMe"
    wsdl:input name="greetMeRequest" message="tns:greetMeRequest"/
    wsdl:output name="greetMeResponse" message="tns:greetMeResponse"/
    /wsdl:operation
    wsdl:operation name="greetMeOneWay"
    wsdl:input name="greetMeOneWayRequest" message="tns:greetMeOneWayRequest"/
    /wsdl:operation
    /wsdl:portType
    wsdl:binding name="JMSGreeterPortBinding" type="tns:JMSGreeterPortType"
    soap:binding style="document" transport="http://cxf.apache.org/transports/jms"/
    wsdl:operation name="greetMe"
    soap:operation soapAction="" style="document"/
    wsdl:input name="greetMeRequest"
    soap:body use="literal"/
    /wsdl:input
    wsdl:output name="greetMeResponse"
    soap:body use="literal"/
    /wsdl:output
    /wsdl:operation
    wsdl:operation name="sayHi"
    soap:operation soapAction="" style="document"/
    wsdl:input name="sayHiRequest"
    soap:body use="literal"/
    /wsdl:input
    wsdl:output name="sayHiResponse"
    soap:body use="literal"/
    /wsdl:output
    /wsdl:operation
    wsdl:operation name="greetMeOneWay"
    soap:operation style="document" soapaction=""/
    wsdl:input name="greetMeOneWayRequest"
    soap:body use="literal"/
    /wsdl:input
    /wsdl:operation
    /wsdl:binding
    wsdl:service name="JMSGreeterService"
    wsdl:port name="GreeterPort" binding="tns:JMSGreeterPortBinding"
    jms:address destinationStyle="queue" jndiConnectionFactoryName="ConnectionFactory" jndiDestinationName="dynamicQueues/test.cxf.jmstransport.queue"
    jms:JMSNamingProperty name="java.naming.factory.initial" value="org.apache.activemq.jndi.ActiveMQInitialContextFactory"/
    jms:JMSNamingProperty name="java.naming.provider.url" value="tcp://localhost:61616"/
    /jms:address
    jms:clientConfig useConduitIdSelector="false"/
    /wsdl:port
    /wsdl:service
    /wsdl:definitions

    When trying to call the service i get the follwing errror:

    messages
    input
    Invoke_2_greetMeOneWay_InputVariable
    part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="in"
    greetMeOneWay xmlns="http://cxf.apache.org/jms_greeter/types"
    requestType
    sdfsdf!
    /requestType
    /greetMeOneWay
    /part
    /Invoke_2_greetMeOneWay_InputVariable
    /input
    fault
    bindingFault xmlns="http://schemas.oracle.com/bpel/extension"
    part name="summary"
    summary
    Unable to find an available port
    /summary
    /part
    /bindingFault
    /fault
    /messages

    When using a JMS Adapter Service i can access the queue without any problems.

    Any ideas? Thanks!

  • RELEVANCY SCORE 2.77

    DB:2.77:Problem Invoking Weservice Of Soap Document Style With Literal Encoding In 7z


    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

    DB:2.77:Problem Invoking Weservice Of Soap Document Style With Literal Encoding In 7z

    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

  • RELEVANCY SCORE 2.76

    DB:2.76:Client Agent With Dii Client 1x


    Hi All,

    In the deployment guide of OWSM it is given that client agent can be configured 3 types of service clients
    1. Proxy client
    2. J2EE client
    3. Axis client
    4. BPEL or ESB client

    I was wondering how can I configure the client agent with standalone DII client ?

    DB:2.76:Client Agent With Dii Client 1x

    Hi All,

    In the deployment guide of OWSM it is given that client agent can be configured 3 types of service clients
    1. Proxy client
    2. J2EE client
    3. Axis client
    4. BPEL or ESB client

    I was wondering how can I configure the client agent with standalone DII client ?

  • RELEVANCY SCORE 2.74

    DB:2.74:[Note] Adding Xsi Type To Soap Messages 8x


    Here is a quick 2.0.10 note.

    Some older SOAP stack require xsi type information embedded in the SOAP message to unmarshall the XML message into the appropriate object representation.

    Most customers do no want the overhead of xsi type definition into the SOAP message given that most modern SOAP stack perform the unmarshalling based on the WSDL/XML Schema.

    To address both requirements, we now by default do not add the xsi:type information to the SOAP traffic that the BPEL PM server generates.

    But we have added a new configuration property to the partnerLinkBinding element of the bpel.xml deployment descriptor so that you can ask the BPEL PM server to selectively decorate the SOAP messages targeted at a specific partnerLink. Here is how this looks like:

    partnerLinkBinding name="XXXXX"
    ....
    property name="sendXSIType"true/property
    /partnerLinkBinding

    Note: the challenge here is that if you invoke a service that requires XSI type information and you forget to set that flag in the deployment descriptor you will get a BindingFault with no detail :-( We are very aware of this limitation and are working very diligently towards addressing this problem with a much nicer error message in the 2.1 (aka end of September release).

    Edwin

    DB:2.74:[Note] Adding Xsi Type To Soap Messages 8x

    Here is a quick 2.0.10 note.

    Some older SOAP stack require xsi type information embedded in the SOAP message to unmarshall the XML message into the appropriate object representation.

    Most customers do no want the overhead of xsi type definition into the SOAP message given that most modern SOAP stack perform the unmarshalling based on the WSDL/XML Schema.

    To address both requirements, we now by default do not add the xsi:type information to the SOAP traffic that the BPEL PM server generates.

    But we have added a new configuration property to the partnerLinkBinding element of the bpel.xml deployment descriptor so that you can ask the BPEL PM server to selectively decorate the SOAP messages targeted at a specific partnerLink. Here is how this looks like:

    partnerLinkBinding name="XXXXX"
    ....
    property name="sendXSIType"true/property
    /partnerLinkBinding

    Note: the challenge here is that if you invoke a service that requires XSI type information and you forget to set that flag in the deployment descriptor you will get a BindingFault with no detail :-( We are very aware of this limitation and are working very diligently towards addressing this problem with a much nicer error message in the 2.1 (aka end of September release).

    Edwin

  • RELEVANCY SCORE 2.74

    DB:2.74:Pi 7.31 Aex (Sp05): Handle Xsi:Nil="True" In Soap Response 33


    HiI'm currently working on sync-proxy to SOAP scenario. Target webservice expects xsi:nil="true" for a few null fields in the request and in the response also it sends the same for some of the null fields. Source system (ECC) wants blank whereever xsi:nil="true" is present in the response message.I'm using the constant function xsi:nil in message mapping (graphical) and able to send xsi:nil="true" in the request to WS.In the response mapping, I'm using isNil boolean function. But the SOAP response mapping is failing because webservice sends the namespace associated with xsi (xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance") in the SOAP envelope and PI discards the envelope message.Below is the response sent by webservice. Below is the SOAP response received by PI at mapping step. As xsi namespace is missing in the payload, PI throws mapping error: Error: The prefix "xsi" for attribute "xsi:nil" associated with an element type "errorField" is not bound.I've also tried creating an xslt mapping to insert xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" at the root node createWorkOrderResponse. But as the message fails before executing the mapping (while parsing the response xml), it didnt work.I've also used "Do not use SOAP envelope" option and xmlanonymizerbean but nothing worked. The message fails at adapter level.Please let me know my options to resolve this issue. As it's a sync-scenario, I'm trying to implement a simple solution to handle this error.RegardsPraveen.

    DB:2.74:Pi 7.31 Aex (Sp05): Handle Xsi:Nil="True" In Soap Response 33

    Wow!!! It worked. Thanks a lot Mark! I was banging my head from past 1 week. Atlast the issue got resolved today. Very happy I've asked basis to implement the SAP note today and after implementing the note 1786611, I found that the xml message now contains all the related namespaces which are missing earlier. Hence the response message mapping is now successfull and the webservice response message reached the sender.FYI - Below is the response xml at mapping step after implementing the note. RegardsPraveen.

  • RELEVANCY SCORE 2.73

    DB:2.73:Document/Literal Soap Format Generation Using Jdeveloper 10.1.2.0.0 pc


    Hi,

    Can anyone tell me please how to create Document/Literal SOAP format using jdeveloper 10.1.2.0.0 ??

    Thanks in advance,

    Khalil

    DB:2.73:Document/Literal Soap Format Generation Using Jdeveloper 10.1.2.0.0 pc

    The method that you call must take a org.w3c.dom.Element as an argument, and must also return an Element.
    In the web.xml file, the servlet-class for your webservice must be changed to oracle.j2ee.ws.StatelessJavaDocWebService.
    You can then either modify your WSDL by hand, or deploy your webservice to an OC4J container, which will then generate a Doc/Literal WSDL for you, and then use that.
    When deploying, make sure that the JDeveloper-generated WSDL file is not included in the WAR file.

  • RELEVANCY SCORE 2.70

    DB:2.70:Document Literal Wrapped Wsdl-First Webmethod Call Parameter Mismatch Error 1z



    I'm new to web services and I'm fighting a wsdl-first doc/literal/wrapped web method implementation which includes headers in the soap request/responses. I'm specifically having trouble w/ webmethods that have no arguments and void return type webmethods.

    I "feel" that I have a firm grasp on how doc/literal/wrapped soap style is handled in regards to complex type elements becoming input parameters to the method and output response object and headers being of type "Holder".

    I've attached on of many complete wsdl(s) that I'm starting with.

    Can someone please shed some light on my troubles?

    DB:2.70:Document Literal Wrapped Wsdl-First Webmethod Call Parameter Mismatch Error 1z


    Hi,

    I have run your wsdl through wsdl2java -validate and this indicates no problems. we were also able to build a dummy client and server impl using the -all flag and these services invoked on each other without any exceptions.

    Can you please explain what specific troubles you are having?

    There are a number of wsdl_first samples with different styles of wsdl in the FUSE Services framework which may help.

    Regards,

    Sen.

  • RELEVANCY SCORE 2.70

    DB:2.70:Wcf Soap Envelope - Namespace Xsi And Xsd kk


    Hello Experts,
    in my SOAP envelope i am getting following s:body
    s:Body xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance xmlns:xsd=http://www.w3.org/2001/XMLSchema
    but my requirement is to get only node with out namespace
    s:Body
    can you please suggest what would be best way for resolving this.
    please help
    Thanks

  • RELEVANCY SCORE 2.70

    DB:2.70:Xmloptions.Setloadadditionalnamespaces Does Not Appear To Work dk



    I am using Document Literal form of argument passing in my weblogic webservice.
    An Axis client is creating a soap message such that the xsi schema declaration
    is in the soapenv:Envelope tag. Prior to parsing of my document, I configure
    XmlOptions.setLoadAdditionalNamespaces to add a proper reference to the xsi namespace.
    Even after doing this, I still get an exception indicating that xsi is not a
    bound namespace.

    Here is an example of the XML that the client is sending:

    soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    soapenv:Body
    requestArray xmlns="http://www.overture.com/service/display"
    ..... document that uses xsi......

    As you can see, the document it's self does not define the xsi schema. It is
    defined in the soapenv:Envelope tag.

    The particular exception occurs in the following code from Root.load (xmlbeans
    v1):

    catch ( SAXParseException e )
    {
    context.abort();

    XmlError err =
    XmlError.forLocation(
    e.getMessage(),
    (String) XmlOptions.safeGet( options, XmlOptions.DOCUMENT_SOURCE_NAME
    ),
    e.getLineNumber(), e.getColumnNumber(), -1 );

    throw new XmlException( err.toString(), e, err );
    }

    Any ideas?

    Thanks.

    -AP_

    (crossposted to xmlbeans-user@xml.apache.org)
    (crossposted to weblogic.developer.interest.xmlbeans)

    DB:2.70:Xmloptions.Setloadadditionalnamespaces Does Not Appear To Work dk


    I am using Document Literal form of argument passing in my weblogic webservice.
    An Axis client is creating a soap message such that the xsi schema declaration
    is in the soapenv:Envelope tag. Prior to parsing of my document, I configure
    XmlOptions.setLoadAdditionalNamespaces to add a proper reference to the xsi namespace.
    Even after doing this, I still get an exception indicating that xsi is not a
    bound namespace.

    Here is an example of the XML that the client is sending:

    soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    soapenv:Body
    requestArray xmlns="http://www.overture.com/service/display"
    ..... document that uses xsi......

    As you can see, the document it's self does not define the xsi schema. It is
    defined in the soapenv:Envelope tag.

    The particular exception occurs in the following code from Root.load (xmlbeans
    v1):

    catch ( SAXParseException e )
    {
    context.abort();

    XmlError err =
    XmlError.forLocation(
    e.getMessage(),
    (String) XmlOptions.safeGet( options, XmlOptions.DOCUMENT_SOURCE_NAME
    ),
    e.getLineNumber(), e.getColumnNumber(), -1 );

    throw new XmlException( err.toString(), e, err );
    }

    Any ideas?

    Thanks.

    -AP_

    (crossposted to xmlbeans-user@xml.apache.org)
    (crossposted to weblogic.developer.interest.xmlbeans)

  • RELEVANCY SCORE 2.68

    DB:2.68:Dynamic Client Performance Enhancement xc



    Hi ,

    I am using DII to invoke web services. I know there is a performance overhead
    with DII but I need it to use it as it suits my requirement .

    How could the performance be improved when DII is used ?

    Are client side stubs created when web service is invoked using DII ( i did not
    see any stub classes created on my file sysyem, is it stored in memory). If yes
    which method creates it,
    service.createCall() or call.invoke(parmas).

    I was also thinking whether the call object which is not serialisable could be
    cached.So that I can invoke just the call.inovke(different parameters) method
    for the subsequent requests.

    Please let me know.
    Your help will be highly apreciated.

    -Amol

    DB:2.68:Dynamic Client Performance Enhancement xc

    You need to use DII only if the web service that
    is invoked is not described using a WSDL.

    If WSDL is available than clientgen can generate
    a stub from it. A generated stub is type safe and
    easy to use.

    Regards,
    -manoj

    --
    http://manojc.com

    "Amol Desai" amolsdesai@yahoo.com wrote in message
    news:3f02d601$1@newsgroups.bea.com...

    Hi Neal,

    If the two approaches are simiilar in performance , then

    why/where should stub based call be used.

    Thanks,

    -Amol

    "Neal Yin" nyin@bea.com wrote:
    Hi Amol,

    Each service.createCall() creates a new call instance. You can reuse
    the
    same call for multiple invocations. Did you compare the DII performance
    and
    stub performance? There should no significant performance difference.

    Thanks,

    -Neal

    "Amol Desai" amolsdesai@yahoo.com wrote in message
    news:3f019f3e$1@newsgroups.bea.com...
    Hi ,

    I am using DII to invoke web services. I know there is a performanceoverhead
    with DII but I need it to use it as it suits my requirement .

    How could the performance be improved when DII is used ?

    Are client side stubs created when web service is invoked using DII( i
    did not
    see any stub classes created on my file sysyem, is it stored inmemory).
    If yes
    which method creates it,
    service.createCall() or call.invoke(parmas).

    I was also thinking whether the call object which is not serialisablecould be
    cached.So that I can invoke just the call.inovke(differentparameters)
    method
    for the subsequent requests.

    Please let me know.
    Your help will be highly apreciated.

    -Amol

  • RELEVANCY SCORE 2.66

    DB:2.66:Php Using Soap To Call Ejb jk



    Hello everybody,

    I've a problem to call a EJB form a PHP script.

    There is a Apache with PHP 5.2.0 and a SAP NetWeaver Application Server 7.10 / AS Java 7.10 running on the system.

    I wanted to use soap to call a method in an EJB. It's only a test EJB:

    [code]

    package beans;

    import javax.ejb.Stateless;

    import javax.jws.WebService;

    import javax.jws.WebMethod;

    @WebService(name="HelloWorldEARBean",serviceName="HelloWorldEARBeanService",targetNamespace="http://beans/",portName="HelloWorldEARBeanPort") @Stateless public class HelloWorldEARBean {

    @WebMethod public String sayHello(String testStr){

    return "Hello Mr. "+testStr;

    }

    @WebMethod public String getReturn(String inputStr){

    return "the return value is"+inputStr;

    }

    }

    [/code]

    I tried it with the PEAR SOAP in the following script:

    [code]

    ?php

    require_once 'SOAP/Client.php';

    $wsdl_url= 'http://localhost:50000/HelloWorldEARBeanService/HelloWorldEARBean?wsdl';

    $WSDL = new SOAP_WSDL($wsdl_url);

    $client = $WSDL-getProxy();

    $client-__trace(1);

    $options=array('namespace' = 'http://beans/',

    'style' = 'rpc',

    'soapaction' = 'sayHello');

    $NAME = "Bob";

    $parameters=array(

    'parameters', $NAME

    );

    $result = $client-getReturn($parameters);

    echo "pre";

    print_r($params);

    echo "/pre";

    echo "h2return/h2";

    echo "pre";

    print_r($result);

    echo "/pre";

    echo 'h2Request/h2';

    echo 'pre' . htmlspecialchars($client-__getlastrequest(), ENT_QUOTES) . '/pre';

    echo 'h2Response/h2';

    echo 'pre' . htmlspecialchars($client-__getlastresponse(), ENT_QUOTES). '/pre';

    ?

    [/code]

    The AS distributes the following WSDL:

    [code]

    - wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://beans/" xmlns:tns="http://beans/"

    - wsdl:types

    - xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" version="1.0" targetNamespace="http://beans/"

    xs:element name="getReturn" type="tns:getReturn" /

    xs:element name="getReturnResponse" type="tns:getReturnResponse" /

    xs:element name="sayHello" type="tns:sayHello" /

    xs:element name="sayHelloResponse" type="tns:sayHelloResponse" /

    - xs:complexType name="sayHello"

    - xs:sequence

    xs:element name="arg0" type="xs:string" minOccurs="0" /

    /xs:sequence

    /xs:complexType

    - xs:complexType name="sayHelloResponse"

    - xs:sequence

    xs:element name="return" type="xs:string" minOccurs="0" /

    /xs:sequence

    /xs:complexType

    - xs:complexType name="getReturn"

    - xs:sequence

    xs:element name="arg0" type="xs:string" minOccurs="0" /

    /xs:sequence

    /xs:complexType

    - xs:complexType name="getReturnResponse"

    - xs:sequence

    xs:element name="return" type="xs:string" minOccurs="0" /

    /xs:sequence

    /xs:complexType

    /xs:schema

    /wsdl:types

    - wsdl:message name="sayHelloIn"

    wsdl:part name="parameters" element="tns:sayHello" /

    /wsdl:message

    - wsdl:message name="sayHelloOut"

    wsdl:part name="sayHelloResponse" element="tns:sayHelloResponse" /

    /wsdl:message

    - wsdl:message name="getReturnIn"

    wsdl:part name="parameters" element="tns:getReturn" /

    /wsdl:message

    - wsdl:message name="getReturnOut"

    wsdl:part name="getReturnResponse" element="tns:getReturnResponse" /

    /wsdl:message

    - wsdl:portType name="HelloWorldEARBean"

    - wsdl:operation name="sayHello" parameterOrder="parameters"

    wsdl:input message="tns:sayHelloIn" /

    wsdl:output message="tns:sayHelloOut" /

    /wsdl:operation

    - wsdl:operation name="getReturn" parameterOrder="parameters"

    wsdl:input message="tns:getReturnIn" /

    wsdl:output message="tns:getReturnOut" /

    /wsdl:operation

    /wsdl:portType

    - wsdl:binding name="HelloWorldEARBeanBinding" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" type="tns:HelloWorldEARBean"

    soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" /

    - wsdl:operation name="sayHello"

    soap:operation soapAction="" /

    - wsdl:input

    soap:body parts="parameters" use="literal" /

    /wsdl:input

    - wsdl:output

    soap:body use="literal" /

    /wsdl:output

    /wsdl:operation

    - wsdl:operation name="getReturn"

    soap:operation soapAction="" /

    - wsdl:input

    soap:body parts="parameters" use="literal" /

    /wsdl:input

    - wsdl:output

    soap:body use="literal" /

    /wsdl:output

    /wsdl:operation

    /wsdl:binding

    - wsdl:service name="HelloWorldEARBeanService"

    - wsdl:port name="HelloWorldEARBeanPort" binding="tns:HelloWorldEARBeanBinding"

    soap:address xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" location="http://localhost:50000/HelloWorldEARBeanService/HelloWorldEARBean" /

    /wsdl:port

    /wsdl:service

    /wsdl:definitions

    [/code]

    By the following output it's obvious that the AS or the EJB (webservice) doesn't receive the parameter send by the PHP script. Look at the output:

    return value:

    the return value is null

    [code]

    Request:

    POST /HelloWorldEARBeanService/HelloWorldEARBean HTTP/1.0

    User-Agent: PEAR-SOAP 0.8.0RC4-devel

    Host: localhost

    Content-Type: text/xml; charset=UTF-8

    Content-Length: 438

    SOAPAction: ""

    ?xml version="1.0" encoding="UTF-8"?

    SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"

    xmlns:xsd="http://www.w3.org/2001/XMLSchema"

    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

    xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"

    SOAP-ENV:Body

    getReturn xmlns="http://beans/"

    itemparameters/item

    itemBob/item/getReturn

    /SOAP-ENV:Body

    /SOAP-ENV:Envelope

    Response:

    HTTP/1.1 200 OK

    server: SAP NetWeaver Application Server 7.10 / AS Java 7.10

    content-type: text/xml; charset=utf-8

    date: Wed, 14 Feb 2007 15:51:53 GMT

    connection: close

    ?xml version="1.0" encoding="utf-8"?

    SOAP-ENV:Envelope xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

    SOAP-ENV:Headerwsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"

    wsu:Timestamp xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"

    wsu:Created2007-02-14T15:51:53Z/wsu:Created

    wsu:Expires2007-02-14T15:52:23Z/wsu:Expires/wsu:Timestamp/wsse:Security/SOAP-ENV:Header

    SOAP-ENV:Bodyns2:getReturnResponse xmlns:ns2='http://beans/'

    returnthe return value is null/return/ns2:getReturnResponse/SOAP-ENV:Body/SOAP-ENV:Envelope

    [/code]

    I used different soap interfaces for PHP like nusoap and the integrated soap interface of PHP 5.

    Further I experimented with different parameters inside the function call

    that results in small differencies at the xml-request.

    Thanks.

    DB:2.66:Php Using Soap To Call Ejb jk


    hi,

    AFAIK you don't need that namespace/datatype information on an XML instance. This information is mainly useful in the schema definition, where you describe the instance data to be sent based on that definition.

    The information(xml attribute) is pretty surely being discarded at runtime by the receiving service runtime or maybe - more severely - raising an error, because the WSDL doesn't define an attribute to be in that element .

    anton

  • RELEVANCY SCORE 2.66

    DB:2.66:Re: Hopefully Easy Question z9


    As per the Oracle BPEL Process Manager Developer's Guide 10g (10.1.3.1.0) Section 3.15.4.:

    SOAP-Encoded Arrays Not Supported.

    Oracle BPEL Process Manager does not support SOAP-encoded arrays (soapenc:arrayType).

    Use one of the following workarounds:

    * Apache Axis supports document-literal style services. This means you can change the service to not use soapenc:arrayType.
    * A wrapper can be placed around the service (also using Apache Axis) so that the BPEL process talks to the document literal wrapper service, which in turn calls the underlying service with soapenc:arrayType.
    * Call a service with soapenc:arrayType from BPEL, but construct the XML message more manually in the BPEL code. This enables you to avoid changing or wrapping the service. However, each time you want to call that service from BPEL, you must take extra steps.

    HTH,
    Nilanshu

    DB:2.66:Re: Hopefully Easy Question z9

    Whit reference my other posts in this thread. Any thoughts in this case?
    Is there anything wrong with the codingsyntax in the xslfile, since the problem seems to be in transformation.

    The webserviceprovider delivers two interfaces (WSDL files) to the webservice. Both are RPC/encoded except the response from the method getMetDataValues (in Alt.1) which is RPC/Literal.
    Alt.1-http://sharki.oslo.dnmi.no/metdata/MetDataService?WSDL
    Alt.2-http://sharki.oslo.dnmi.no/wsKlima/doc/MetDataService.wsdl
    Both fails!

    In my case I'm calling the method getStationProperties which I assume is using RPC/encoded binding on the response.

    What bindingstyle is supported by BPEL?
    I understand the RPC/encoding is not WS-I compliant, so perhaps the serviceprovider should offer something WS-I compliant like RPC/Literal or Document/Literal?

    brgds
    Jrn Eirik

  • RELEVANCY SCORE 2.66

    DB:2.66:Problems Invoking Literal Web Services 87


    Hi all,
    I'm trying to invoke a document style web service.
    I've succesfully deployed a service using soap:body use="literal" namespace="MyWebService1"/

    as for all literal service i've declared it as
    public org.w3c.dom.Element MyService(org.w3c.dom.Element e){...

    in my WSDL i've changed message type from xsd:any or xsd:anyType to an element I've declared in the types section, cause BPEL do not accept these kind of types:

    message name="MyServiceRequest"
    part name="e" element="tns:MyElement"/
    /message

    i've called the service succesfully with a self-written client and then i've tried to invoke it throught a Bpel process... and it fail :(

    I've used a TCP monitor to compare XML envelopes and I've noticed a difference wich let BPEL invocation fail

    with my pure java client the mex produced is:
    ?xml version='1.0' encoding='UTF-8'?
    SOAP-ENV:Envelope
    xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    SOAP-ENV:Body
    ns1:docStyle xmlns:ns1="MyWebService1" SOAP-ENV:encodingStyle="http://xml.apache.org/xml-soap/literalxml"
    elem
    numbersnumber11/number/numbers
    /elem
    /ns1:docStyle
    /SOAP-ENV:Body

    with BPEL call i get

    soapenv:Envelope
    xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    soapenv:Body
    ns1:docStyle soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="MyWebService1"
    numbers xmlns="http://prova/DocStyleService.wsdl"
    number45/number
    /numbers
    /ns1:docStyle
    /soapenv:Body
    /soapenv:Envelope

    the problem is the encodingStyle one = http://schemas.xmlsoap.org/soap/encoding/
    the other = http://xml.apache.org/xml-soap/literalxml

    but i cannot figure how to change this, how to use the invoke activity to send in literal encoding style!!

    any ideas

    thank Lisa

    DB:2.66:Problems Invoking Literal Web Services 87

    Hi Lisa,

    I am having very similar problem :) (RPC web service, but Element as parameter and literal encoding), so if you, or someone else knows the solution, please help...

    regards,
    Vlado

  • RELEVANCY SCORE 2.64

    DB:2.64:Using Studio To Develop Dii Client For Diningguide Example ma


    Hi,

    I am trying to develop a DII client to the DiningGuide example from the Java Studio Enterprise Tutorials and Code Camps:
    http://developers.sun.com/prodtech/javatools/jsenterprise/learning/tutorials/index.html
    I am using Studio6 with Application Server 7 update 3 with Java WSDP 1.3 [JAX-RPC 1.1 support]

    The question is how does Studio support JAX-RPC DII client development ? I understand that the config.xml file is different between Static stub based client and a DII client. Please let me know as to how to configure
    Studio to do this.

    Below is the code that is new in the DIIClient shown in 3 sections:
    - imports area in CustomerReviewTable.java
    - getCustomerReviewByName method in CustomerReviewTable.java
    [Basically taking the code from
    http://java.sun.com/webservices/docs/1.0/tutorial/doc/JAXRPC6.html#75222
    and modifying this to use this service and make appropriate
    changes for the return value (Vector).
    I suspect that this is where the problem is but need help to fix
    it. - Thanks!!]
    - Variables declaration new for DIIClient

    - The WSDL for the DGWebService service is also shown

    I tried it with both JAXRPC 1.0 and JAXRPC 1.1 [Setting this for the
    Service in Studio 6] and regenerating the Service code
    but did not see any difference.

    Right now, with the code shown below, I do not get any exceptions, but
    it doesnot show any reviews [Vector returned is null].

    Really appreciate your help,
    Sridhar.

    ============ imports area in CustomerReviewTable.java ===============
    package DIIClient;
    import javax.swing.table.*;
    import java.util.*;
    import WebService.DGWebServiceClientGenClient.*;

    /* New for DII */
    import javax.xml.rpc.Call;
    import javax.xml.rpc.Service;
    import javax.xml.rpc.JAXRPCException;
    import javax.xml.namespace.QName;
    import javax.xml.rpc.ServiceFactory;
    import javax.xml.rpc.ParameterMode;

    ========= getCustomerReviewByName method in CustomerReviewTable.java
    =========
    private Vector getCustomerReviewByName(java.lang.String
    restaurantname) {
    Vector custList = new Vector();
    try {
    /* Old Static Stub in the Swing Client that works:
    WebService.DGWebServiceClientGenClient.DGWebService service2
    = new
    WebService.DGWebServiceClientGenClient.DGWebService_Impl();

    WebService.DGWebServiceClientGenClient.DGWebServiceServantInterface
    port = service2.getDGWebServiceServantInterfacePort();
    custList =
    (java.util.Vector)port.getCustomerreviewsByRestaurant(restaurantname);
    */
    /* New DII Code below ... */
    System.out.println("Now using DII Code ...");
    ServiceFactory factory = ServiceFactory.newInstance();
    Service service = factory.createService(new
    QName(qnameService));

    QName port = new QName(qnamePort);

    Call call = service.createCall(port);

    call.setTargetEndpointAddress(endPointAddress);
    call.setProperty(Call.SOAPACTION_USE_PROPERTY, new
    Boolean(true));
    call.setProperty(Call.SOAPACTION_URI_PROPERTY, "");
    call.setProperty(ENCODING_STYLE_PROPERTY, URI_ENCODING);
    QName QNAME_TYPE_STRING = new QName(NS_XSD, "string");
    QName QNAME_TYPE_VECTOR = new QName(NS_XSD, "vector");

    call.setReturnType(QNAME_TYPE_VECTOR);

    call.setOperationName(new QName(BODY_NAMESPACE_VALUE,
    "getCustomerreviewsByRestaurant"));
    call.addParameter("String_1", QNAME_TYPE_STRING,
    ParameterMode.IN);
    String[] params = { restaurantname };

    custList = (java.util.Vector) call.invoke (params);

    System.out.println(custList);
    }
    catch (Exception ex) {
    System.err.println("Caught an exception." );
    ex.printStackTrace();
    }
    return custList;
    }

    ============ Variables declaration new for DIIClient ====================
    //Variables declaration new for DIIClient
    private static String qnameService = "DGWebService";
    private static String qnamePort = "DGWebServiceServantInterface";
    private static String endPointAddress =
    "http://localhost:80/DGWebService/DGWebService";

    private static String BODY_NAMESPACE_VALUE = "urn:DGWebService/wsdl";
    private static String ENCODING_STYLE_PROPERTY =
    "javax.xml.rpc.encodingstyle.namespace.uri";
    // private static String NS_XSD = "http://www.w3.org/2001/XMLSchema";
    private static String NS_XSD =
    "http://java.sun.com/jax-rpc-ri/internal";
    private static String URI_ENCODING =
    "http://schemas.xmlsoap.org/soap/encoding/";
    //http://schemas.xmlsoap.org/soap/encoding/
    //http://java.sun.com/jax-rpc-ri/internal

    ============ The WSDL for the DGWebService service =================
    ?xml version="1.0" encoding="UTF-8"?

    definitions name="DGWebService" targetNamespace="urn:DGWebService/wsdl"
    xmlns:tns="urn:DGWebService/wsdl"
    xmlns="http://schemas.xmlsoap.org/wsdl/"
    xmlns:ns2="http://java.sun.com/jax-rpc-ri/internal"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
    xmlns:ns3="urn:DGWebService/types"
    types
    schema targetNamespace="http://java.sun.com/jax-rpc-ri/internal"
    xmlns:tns="http://java.sun.com/jax-rpc-ri/internal"
    xmlns:soap11-enc="http://schemas.xmlsoap.org/soap/encoding/"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
    xmlns="http://www.w3.org/2001/XMLSchema"
    import namespace="http://schemas.xmlsoap.org/soap/encoding/"/
    import namespace="urn:DGWebService/types"/
    complexType name="vector"
    complexContent
    extension base="tns:list"
    sequence//extension/complexContent/complexType
    complexType name="list"
    complexContent
    extension base="tns:collection"
    sequence//extension/complexContent/complexType
    complexType name="collection"
    complexContent
    restriction base="soap11-enc:Array"
    attribute ref="soap11-enc:arrayType"
    wsdl:arrayType="anyType[]"//restriction/complexContent/complexType/schema
    schema targetNamespace="urn:DGWebService/types"
    xmlns:tns="urn:DGWebService/types"
    xmlns:soap11-enc="http://schemas.xmlsoap.org/soap/encoding/"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
    xmlns="http://www.w3.org/2001/XMLSchema"
    import namespace="http://schemas.xmlsoap.org/soap/encoding/"/
    import namespace="http://java.sun.com/jax-rpc-ri/internal"/
    complexType name="CustomerreviewDetail"
    sequence
    element name="customername" type="string"/
    element name="restaurantname" type="string"/
    element name="review" type="string"/
    element name="sampleProperty"
    type="string"//sequence/complexType
    complexType name="RestaurantDetail"
    sequence
    element name="address" type="string"/
    element name="cuisine" type="string"/
    element name="description" type="string"/
    element name="neighborhood" type="string"/
    element name="phone" type="string"/
    element name="rating" type="int"/
    element name="restaurantname" type="string"/
    element name="sampleProperty"
    type="string"//sequence/complexType/schema/types
    message name="DGWebServiceServantInterface_createCustomerreview"
    part name="String_1" type="xsd:string"/
    part name="String_2" type="xsd:string"/
    part name="String_3" type="xsd:string"//message
    message
    name="DGWebServiceServantInterface_createCustomerreviewResponse"/
    message name="DGWebServiceServantInterface_getAllRestaurants"/
    message name="DGWebServiceServantInterface_getAllRestaurantsResponse"
    part name="result" type="ns2:vector"//message
    message name="DGWebServiceServantInterface_getCustomerreviewDetail"/
    message
    name="DGWebServiceServantInterface_getCustomerreviewDetailResponse"
    part name="result" type="ns3:CustomerreviewDetail"//message
    message
    name="DGWebServiceServantInterface_getCustomerreviewsByRestaurant"
    part name="String_1" type="xsd:string"//message
    message
    name="DGWebServiceServantInterface_getCustomerreviewsByRestaurantResponse"
    part name="result" type="ns2:vector"//message
    message name="DGWebServiceServantInterface_getRestaurantDetail"/
    message name="DGWebServiceServantInterface_getRestaurantDetailResponse"
    part name="result" type="ns3:RestaurantDetail"//message
    portType name="DGWebServiceServantInterface"
    operation name="createCustomerreview" parameterOrder="String_1
    String_2 String_3"
    input
    message="tns:DGWebServiceServantInterface_createCustomerreview"/
    output
    message="tns:DGWebServiceServantInterface_createCustomerreviewResponse"//operation
    operation name="getAllRestaurants"
    input message="tns:DGWebServiceServantInterface_getAllRestaurants"/
    output
    message="tns:DGWebServiceServantInterface_getAllRestaurantsResponse"//operation
    operation name="getCustomerreviewDetail"
    input
    message="tns:DGWebServiceServantInterface_getCustomerreviewDetail"/
    output
    message="tns:DGWebServiceServantInterface_getCustomerreviewDetailResponse"//operation
    operation name="getCustomerreviewsByRestaurant"
    parameterOrder="String_1"
    input
    message="tns:DGWebServiceServantInterface_getCustomerreviewsByRestaurant"/
    output
    message="tns:DGWebServiceServantInterface_getCustomerreviewsByRestaurantResponse"//operation
    operation name="getRestaurantDetail"
    input
    message="tns:DGWebServiceServantInterface_getRestaurantDetail"/
    output
    message="tns:DGWebServiceServantInterface_getRestaurantDetailResponse"//operation/portType
    binding name="DGWebServiceServantInterfaceBinding"
    type="tns:DGWebServiceServantInterface"
    soap:binding transport="http://schemas.xmlsoap.org/soap/http"
    style="rpc"/
    operation name="createCustomerreview"
    soap:operation soapAction=""/
    input
    soap:body
    encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded"
    namespace="urn:DGWebService/wsdl"//input
    output
    soap:body
    encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded"
    namespace="urn:DGWebService/wsdl"//output/operation
    operation name="getAllRestaurants"
    soap:operation soapAction=""/
    input
    soap:body
    encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded"
    namespace="urn:DGWebService/wsdl"//input
    output
    soap:body
    encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded"
    namespace="urn:DGWebService/wsdl"//output/operation
    operation name="getCustomerreviewDetail"
    soap:operation soapAction=""/
    input
    soap:body
    encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded"
    namespace="urn:DGWebService/wsdl"//input
    output
    soap:body
    encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded"
    namespace="urn:DGWebService/wsdl"//output/operation
    operation name="getCustomerreviewsByRestaurant"
    soap:operation soapAction=""/
    input
    soap:body
    encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded"
    namespace="urn:DGWebService/wsdl"//input
    output
    soap:body
    encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded"
    namespace="urn:DGWebService/wsdl"//output/operation
    operation name="getRestaurantDetail"
    soap:operation soapAction=""/
    input
    soap:body
    encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded"
    namespace="urn:DGWebService/wsdl"//input
    output
    soap:body
    encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded"
    namespace="urn:DGWebService/wsdl"//output/operation/binding
    service name="DGWebService"
    port name="DGWebServiceServantInterfacePort"
    binding="tns:DGWebServiceServantInterfaceBinding"
    soap:address
    location="http://localhost:80/DGWebService/DGWebService"//port/service/definitions

    =================================================================

    DB:2.64:Using Studio To Develop Dii Client For Diningguide Example ma

    Hi,

    I am trying to develop a DII client to the DiningGuide example from the Java Studio Enterprise Tutorials and Code Camps:
    http://developers.sun.com/prodtech/javatools/jsenterprise/learning/tutorials/index.html
    I am using Studio6 with Application Server 7 update 3 with Java WSDP 1.3 [JAX-RPC 1.1 support]

    The question is how does Studio support JAX-RPC DII client development ? I understand that the config.xml file is different between Static stub based client and a DII client. Please let me know as to how to configure
    Studio to do this.

    Below is the code that is new in the DIIClient shown in 3 sections:
    - imports area in CustomerReviewTable.java
    - getCustomerReviewByName method in CustomerReviewTable.java
    [Basically taking the code from
    http://java.sun.com/webservices/docs/1.0/tutorial/doc/JAXRPC6.html#75222
    and modifying this to use this service and make appropriate
    changes for the return value (Vector).
    I suspect that this is where the problem is but need help to fix
    it. - Thanks!!]
    - Variables declaration new for DIIClient

    - The WSDL for the DGWebService service is also shown

    I tried it with both JAXRPC 1.0 and JAXRPC 1.1 [Setting this for the
    Service in Studio 6] and regenerating the Service code
    but did not see any difference.

    Right now, with the code shown below, I do not get any exceptions, but
    it doesnot show any reviews [Vector returned is null].

    Really appreciate your help,
    Sridhar.

    ============ imports area in CustomerReviewTable.java ===============
    package DIIClient;
    import javax.swing.table.*;
    import java.util.*;
    import WebService.DGWebServiceClientGenClient.*;

    /* New for DII */
    import javax.xml.rpc.Call;
    import javax.xml.rpc.Service;
    import javax.xml.rpc.JAXRPCException;
    import javax.xml.namespace.QName;
    import javax.xml.rpc.ServiceFactory;
    import javax.xml.rpc.ParameterMode;

    ========= getCustomerReviewByName method in CustomerReviewTable.java
    =========
    private Vector getCustomerReviewByName(java.lang.String
    restaurantname) {
    Vector custList = new Vector();
    try {
    /* Old Static Stub in the Swing Client that works:
    WebService.DGWebServiceClientGenClient.DGWebService service2
    = new
    WebService.DGWebServiceClientGenClient.DGWebService_Impl();

    WebService.DGWebServiceClientGenClient.DGWebServiceServantInterface
    port = service2.getDGWebServiceServantInterfacePort();
    custList =
    (java.util.Vector)port.getCustomerreviewsByRestaurant(restaurantname);
    */
    /* New DII Code below ... */
    System.out.println("Now using DII Code ...");
    ServiceFactory factory = ServiceFactory.newInstance();
    Service service = factory.createService(new
    QName(qnameService));

    QName port = new QName(qnamePort);

    Call call = service.createCall(port);

    call.setTargetEndpointAddress(endPointAddress);
    call.setProperty(Call.SOAPACTION_USE_PROPERTY, new
    Boolean(true));
    call.setProperty(Call.SOAPACTION_URI_PROPERTY, "");
    call.setProperty(ENCODING_STYLE_PROPERTY, URI_ENCODING);
    QName QNAME_TYPE_STRING = new QName(NS_XSD, "string");
    QName QNAME_TYPE_VECTOR = new QName(NS_XSD, "vector");

    call.setReturnType(QNAME_TYPE_VECTOR);

    call.setOperationName(new QName(BODY_NAMESPACE_VALUE,
    "getCustomerreviewsByRestaurant"));
    call.addParameter("String_1", QNAME_TYPE_STRING,
    ParameterMode.IN);
    String[] params = { restaurantname };

    custList = (java.util.Vector) call.invoke (params);

    System.out.println(custList);
    }
    catch (Exception ex) {
    System.err.println("Caught an exception." );
    ex.printStackTrace();
    }
    return custList;
    }

    ============ Variables declaration new for DIIClient ====================
    //Variables declaration new for DIIClient
    private static String qnameService = "DGWebService";
    private static String qnamePort = "DGWebServiceServantInterface";
    private static String endPointAddress =
    "http://localhost:80/DGWebService/DGWebService";

    private static String BODY_NAMESPACE_VALUE = "urn:DGWebService/wsdl";
    private static String ENCODING_STYLE_PROPERTY =
    "javax.xml.rpc.encodingstyle.namespace.uri";
    // private static String NS_XSD = "http://www.w3.org/2001/XMLSchema";
    private static String NS_XSD =
    "http://java.sun.com/jax-rpc-ri/internal";
    private static String URI_ENCODING =
    "http://schemas.xmlsoap.org/soap/encoding/";
    //http://schemas.xmlsoap.org/soap/encoding/
    //http://java.sun.com/jax-rpc-ri/internal

    ============ The WSDL for the DGWebService service =================
    ?xml version="1.0" encoding="UTF-8"?

    definitions name="DGWebService" targetNamespace="urn:DGWebService/wsdl"
    xmlns:tns="urn:DGWebService/wsdl"
    xmlns="http://schemas.xmlsoap.org/wsdl/"
    xmlns:ns2="http://java.sun.com/jax-rpc-ri/internal"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
    xmlns:ns3="urn:DGWebService/types"
    types
    schema targetNamespace="http://java.sun.com/jax-rpc-ri/internal"
    xmlns:tns="http://java.sun.com/jax-rpc-ri/internal"
    xmlns:soap11-enc="http://schemas.xmlsoap.org/soap/encoding/"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
    xmlns="http://www.w3.org/2001/XMLSchema"
    import namespace="http://schemas.xmlsoap.org/soap/encoding/"/
    import namespace="urn:DGWebService/types"/
    complexType name="vector"
    complexContent
    extension base="tns:list"
    sequence//extension/complexContent/complexType
    complexType name="list"
    complexContent
    extension base="tns:collection"
    sequence//extension/complexContent/complexType
    complexType name="collection"
    complexContent
    restriction base="soap11-enc:Array"
    attribute ref="soap11-enc:arrayType"
    wsdl:arrayType="anyType[]"//restriction/complexContent/complexType/schema
    schema targetNamespace="urn:DGWebService/types"
    xmlns:tns="urn:DGWebService/types"
    xmlns:soap11-enc="http://schemas.xmlsoap.org/soap/encoding/"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
    xmlns="http://www.w3.org/2001/XMLSchema"
    import namespace="http://schemas.xmlsoap.org/soap/encoding/"/
    import namespace="http://java.sun.com/jax-rpc-ri/internal"/
    complexType name="CustomerreviewDetail"
    sequence
    element name="customername" type="string"/
    element name="restaurantname" type="string"/
    element name="review" type="string"/
    element name="sampleProperty"
    type="string"//sequence/complexType
    complexType name="RestaurantDetail"
    sequence
    element name="address" type="string"/
    element name="cuisine" type="string"/
    element name="description" type="string"/
    element name="neighborhood" type="string"/
    element name="phone" type="string"/
    element name="rating" type="int"/
    element name="restaurantname" type="string"/
    element name="sampleProperty"
    type="string"//sequence/complexType/schema/types
    message name="DGWebServiceServantInterface_createCustomerreview"
    part name="String_1" type="xsd:string"/
    part name="String_2" type="xsd:string"/
    part name="String_3" type="xsd:string"//message
    message
    name="DGWebServiceServantInterface_createCustomerreviewResponse"/
    message name="DGWebServiceServantInterface_getAllRestaurants"/
    message name="DGWebServiceServantInterface_getAllRestaurantsResponse"
    part name="result" type="ns2:vector"//message
    message name="DGWebServiceServantInterface_getCustomerreviewDetail"/
    message
    name="DGWebServiceServantInterface_getCustomerreviewDetailResponse"
    part name="result" type="ns3:CustomerreviewDetail"//message
    message
    name="DGWebServiceServantInterface_getCustomerreviewsByRestaurant"
    part name="String_1" type="xsd:string"//message
    message
    name="DGWebServiceServantInterface_getCustomerreviewsByRestaurantResponse"
    part name="result" type="ns2:vector"//message
    message name="DGWebServiceServantInterface_getRestaurantDetail"/
    message name="DGWebServiceServantInterface_getRestaurantDetailResponse"
    part name="result" type="ns3:RestaurantDetail"//message
    portType name="DGWebServiceServantInterface"
    operation name="createCustomerreview" parameterOrder="String_1
    String_2 String_3"
    input
    message="tns:DGWebServiceServantInterface_createCustomerreview"/
    output
    message="tns:DGWebServiceServantInterface_createCustomerreviewResponse"//operation
    operation name="getAllRestaurants"
    input message="tns:DGWebServiceServantInterface_getAllRestaurants"/
    output
    message="tns:DGWebServiceServantInterface_getAllRestaurantsResponse"//operation
    operation name="getCustomerreviewDetail"
    input
    message="tns:DGWebServiceServantInterface_getCustomerreviewDetail"/
    output
    message="tns:DGWebServiceServantInterface_getCustomerreviewDetailResponse"//operation
    operation name="getCustomerreviewsByRestaurant"
    parameterOrder="String_1"
    input
    message="tns:DGWebServiceServantInterface_getCustomerreviewsByRestaurant"/
    output
    message="tns:DGWebServiceServantInterface_getCustomerreviewsByRestaurantResponse"//operation
    operation name="getRestaurantDetail"
    input
    message="tns:DGWebServiceServantInterface_getRestaurantDetail"/
    output
    message="tns:DGWebServiceServantInterface_getRestaurantDetailResponse"//operation/portType
    binding name="DGWebServiceServantInterfaceBinding"
    type="tns:DGWebServiceServantInterface"
    soap:binding transport="http://schemas.xmlsoap.org/soap/http"
    style="rpc"/
    operation name="createCustomerreview"
    soap:operation soapAction=""/
    input
    soap:body
    encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded"
    namespace="urn:DGWebService/wsdl"//input
    output
    soap:body
    encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded"
    namespace="urn:DGWebService/wsdl"//output/operation
    operation name="getAllRestaurants"
    soap:operation soapAction=""/
    input
    soap:body
    encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded"
    namespace="urn:DGWebService/wsdl"//input
    output
    soap:body
    encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded"
    namespace="urn:DGWebService/wsdl"//output/operation
    operation name="getCustomerreviewDetail"
    soap:operation soapAction=""/
    input
    soap:body
    encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded"
    namespace="urn:DGWebService/wsdl"//input
    output
    soap:body
    encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded"
    namespace="urn:DGWebService/wsdl"//output/operation
    operation name="getCustomerreviewsByRestaurant"
    soap:operation soapAction=""/
    input
    soap:body
    encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded"
    namespace="urn:DGWebService/wsdl"//input
    output
    soap:body
    encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded"
    namespace="urn:DGWebService/wsdl"//output/operation
    operation name="getRestaurantDetail"
    soap:operation soapAction=""/
    input
    soap:body
    encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded"
    namespace="urn:DGWebService/wsdl"//input
    output
    soap:body
    encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded"
    namespace="urn:DGWebService/wsdl"//output/operation/binding
    service name="DGWebService"
    port name="DGWebServiceServantInterfacePort"
    binding="tns:DGWebServiceServantInterfaceBinding"
    soap:address
    location="http://localhost:80/DGWebService/DGWebService"//port/service/definitions

    =================================================================

  • RELEVANCY SCORE 2.63

    DB:2.63:Not Able To Get Return Value From Dii Client For Document/Literal Service f3


    I am Not able to get return value from DII client for Document/literal service.It works fine for rpc/encoded service.
    Here is the code
    -----------------------
    System.setProperty("javax.xml.rpc.ServiceFactory",
    "weblogic.webservice.core.rpc.ServiceFactoryImpl");
    ServiceFactory sf = ServiceFactory.newInstance();
    QName serviceQname = new QName("http://batchrecord.webservices.sums.cfm.com","CFMBatchRecordService");
    Service service = sf.createService(serviceQname);
    QName portQname = new QName("http://batchrecord.webservices.sums.cfm.com","CFMBatchRecordServicePort");
    QName QNAME_TYPE_STRING = new QName(NS_XSD, "string");
    Call call = service.createCall(portQname);
    call.setProperty(Call.OPERATION_STYLE_PROPERTY, "rpc");
    call.setTargetEndpointAddress(endpoint);
    call.setProperty(Call.SOAPACTION_USE_PROPERTY, new Boolean(true));
    call.setProperty(Call.SOAPACTION_URI_PROPERTY, "");
    call.setProperty(ENCODING_STYLE_PROPERTY, URI_ENCODING);
    call.setReturnType(QNAME_TYPE_STRING);
    call.setOperationName(new QName("http://batchrecord.webservices.sums.cfm.com", "processBREditForAlerts"));
    call.addParameter("xmlMessage", new QName("http://www.w3.org/2001/XMLSchema", "string"), ParameterMode.IN);
    String params[] = {
    "testtest"};
    String result = (String) call.invoke(params);
    System.out.println(result);

    DB:2.63:Not Able To Get Return Value From Dii Client For Document/Literal Service f3

    I am Not able to get return value from DII client for Document/literal service.It works fine for rpc/encoded service.
    Here is the code
    -----------------------
    System.setProperty("javax.xml.rpc.ServiceFactory",
    "weblogic.webservice.core.rpc.ServiceFactoryImpl");
    ServiceFactory sf = ServiceFactory.newInstance();
    QName serviceQname = new QName("http://batchrecord.webservices.sums.cfm.com","CFMBatchRecordService");
    Service service = sf.createService(serviceQname);
    QName portQname = new QName("http://batchrecord.webservices.sums.cfm.com","CFMBatchRecordServicePort");
    QName QNAME_TYPE_STRING = new QName(NS_XSD, "string");
    Call call = service.createCall(portQname);
    call.setProperty(Call.OPERATION_STYLE_PROPERTY, "rpc");
    call.setTargetEndpointAddress(endpoint);
    call.setProperty(Call.SOAPACTION_USE_PROPERTY, new Boolean(true));
    call.setProperty(Call.SOAPACTION_URI_PROPERTY, "");
    call.setProperty(ENCODING_STYLE_PROPERTY, URI_ENCODING);
    call.setReturnType(QNAME_TYPE_STRING);
    call.setOperationName(new QName("http://batchrecord.webservices.sums.cfm.com", "processBREditForAlerts"));
    call.addParameter("xmlMessage", new QName("http://www.w3.org/2001/XMLSchema", "string"), ParameterMode.IN);
    String params[] = {
    "testtest"};
    String result = (String) call.invoke(params);
    System.out.println(result);

  • RELEVANCY SCORE 2.62

    DB:2.62:Problem When Calling Bpel Process (Ws) From Apex mz


    I am trying to add a web service call to a BPEL process I have created (tried a few others aswell), but every time I try to add the WDSL file I get the following error:

    -----------------------
    *1 error has occurred*

    The WSDL document contains multiple SOAP bindings. Application Express only supports WSDL's with one SOAP binding. Click Create Web Service Reference Manually to continue creating a reference for this service.
    ---------------

    It is a simple BPEL process which works fine when called from the BPEL Console, however I have no success when calling it from APEX.

    Am I doing something wrong, or is there a bug in BPEL/APEX?

    Oracle BPEL Console v10.1.3.1.0
    Apex: 3.2

    ----------------------

    The WDSL looks like this:
    definitions name="BPELProcess9" targetNamespace="http://xmlns.oracle.com/BPELProcess9"

    types

    schema
    import namespace="http://xmlns.oracle.com/BPELProcess9" schemaLocation="BPELProcess9.xsd"/
    /schema

    schema
    import namespace="http://schemas.xmlsoap.org/ws/2003/03/addressing" schemaLocation="http://xxx:8888/orabpel/xmllib/ws-addressing.xsd"/
    /schema
    /types

    message name="BPELProcess9ResponseMessage"
    part name="payload" element="tns:BPELProcess9ProcessResponse"/
    /message

    message name="BPELProcess9RequestMessage"
    part name="payload" element="tns:BPELProcess9ProcessRequest"/
    /message

    message name="WSAReplyToHeader"
    part name="ReplyTo" element="wsa:ReplyTo"/
    /message

    message name="WSARelatesToHeader"
    part name="RelatesTo" element="wsa:RelatesTo"/
    /message

    message name="WSAMessageIDHeader"
    part name="MessageID" element="wsa:MessageID"/
    /message

    portType name="BPELProcess9Callback"

    operation name="onResult"
    input message="tns:BPELProcess9ResponseMessage"/
    /operation
    /portType

    portType name="BPELProcess9"

    operation name="initiate"
    input message="tns:BPELProcess9RequestMessage"/
    /operation
    /portType

    binding name="BPELProcess9Binding" type="tns:BPELProcess9"
    soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/

    operation name="initiate"
    soap:operation style="document" soapAction="initiate"/

    input
    soap:header message="tns:WSAReplyToHeader" part="ReplyTo" use="literal" encodingStyle=""/
    soap:header message="tns:WSAMessageIDHeader" part="MessageID" use="literal" encodingStyle=""/
    soap:body use="literal"/
    /input
    /operation
    /binding

    binding name="BPELProcess9CallbackBinding" type="tns:BPELProcess9Callback"
    soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/

    operation name="onResult"
    soap:operation style="document" soapAction="onResult"/

    input
    soap:header message="tns:WSARelatesToHeader" part="RelatesTo" use="literal" encodingStyle=""/
    soap:body use="literal"/
    /input
    /operation
    /binding

    service name="BPELProcess9"

    port name="BPELProcess9Port" binding="tns:BPELProcess9Binding"
    soap:address location="http://xxxx:8888/orabpel/default/BPELProcess9/1.1"/
    /port
    /service

    service name="BPELProcess9CallbackService"

    port name="BPELProcess9CallbackPort" binding="tns:BPELProcess9CallbackBinding"
    soap:address location="http://set.by.caller"/
    /port
    /service

    plnk:partnerLinkType name="BPELProcess9"

    plnk:role name="BPELProcess9Requester"
    plnk:portType name="tns:BPELProcess9Callback"/
    /plnk:role

    plnk:role name="BPELProcess9Provider"
    plnk:portType name="tns:BPELProcess9"/
    /plnk:role
    /plnk:partnerLinkType
    /definitions

    DB:2.62:Problem When Calling Bpel Process (Ws) From Apex mz

    Allow me to reply to my own thread, for the benefit of any others who might want to invoke a BPEL WS from APEX facing the same problem:

    Apex does not seem to like asynchronous BPEL processes so the trick is to make a synchronous BPEL process call the asynchronous BPEL process.

  • RELEVANCY SCORE 2.62

    DB:2.62:Need Help - Simple Api Issue - Footprints Service Core / Java xc



    I'm attempting to run a simple java program to get details on a ticket in Footprints Service Core. I need to know:

    1. Where do I insert the username I need to authenticate?

    2. Where do I insert the password I need to authenticate?

    3. Do I need to specify a ticket number that I want to get the details on or does this program pull multiple tickets?

    4. Is there anything else I need to get a "hello world" version of this working?

    The program is an example from the user guide. I'm using version 11.6 of FPSC. The class is below:

    Thanks for your help!

    import javax.xml.soap.*;

    //enable soap functionality

    public class GetIssueDetails

    {

    public static String GetIndent( int num )

    {

    String s = "";

    for( int i = 0; i num; i++ )

    {

    s = s + " ";

    }

    return s;

    }

    public static void DumpSOAPElement(SOAPElement el, int indent) throws Exception

    {

    java.util.Iterator it = el.getChildElements();

    while( it.hasNext())

    {

    String indstr = GetIndent( indent );

    Object obj = it.next();

    if( obj instanceof SOAPElement )

    {

    SOAPElement ele = (SOAPElement)obj;

    System.out.println( indstr + "-----------------------------" );

    System.out.println( indstr + ele.getElementName().getLocalName() );

    System.out.println( indstr + "-----------------------------" );

    DumpSOAPElement( ele, indent + 4 );

    }

    else if( obj instanceof Text )

    {

    Text txt = (Text)obj;

    System.out.println( indstr + txt.getValue() + "\n" );

    }

    }

    }

    public static void main( String[] args )

    {

    try

    {

    // Comment this out for NO proxy.

    /*java.util.Properties props = System.getProperties();

    props.put( "http.proxyHost", "localhost" );

    props.put( "http.proxyPort", "8888" );

    */

    // Setup SOAP message.

    SOAPConnectionFactory scf = SOAPConnectionFactory.newInstance();

    SOAPConnection connection = scf.createConnection();

    MessageFactory msgFactory = MessageFactory.newInstance();

    SOAPMessage msg = msgFactory.createMessage();

    SOAPEnvelope env = msg.getSOAPPart().getEnvelope();

    env.addNamespaceDeclaration( "xsi", "http://www.w3.org/1999/XMLSchema-instance" );

    env.addNamespaceDeclaration( "xsd", "http://www.w3.org/1999/XMLSchema" );

    env.addNamespaceDeclaration( "namesp2", "http://xml.apache.org/xml-soap" );

    env.addNamespaceDeclaration( "SOAP-ENC", "http://schemas.xmlsoap.org/soap/encoding/" );

    // Compose SOAP body.

    SOAPBody body = env.getBody();

    SOAPElement invoke = body.addChildElement(

    env.createName("MRWebServices__getIssueDetails", "namesp1","MRWebServices") );

    SOAPElement arg1 = invoke.addChildElement( env.createName("user") );

    arg1.addAttribute( env.createName("type","xsi",""), "xsd:string" );

    arg1.addTextNode("WebServices");

    SOAPElement arg2 = invoke.addChildElement( env.createName("password") );

    arg2.addAttribute( env.createName("type","xsi",""), "xsd:string" );

    arg2.addTextNode("fakepassword");

    SOAPElement arg3 = invoke.addChildElement( env.createName("extrainfo") );

    arg3.addAttribute( env.createName("type","xsi",""), "xsd:string" );

    SOAPElement arg4 = invoke.addChildElement( env.createName("projectnumber") );

    arg4.addAttribute( env.createName("type","xsi",""), "xsd:int" );

    arg4.addTextNode("78");

    SOAPElement arg5 = invoke.addChildElement( env.createName("mrid") );

    arg5.addAttribute( env.createName("type","xsi",""), "xsd:int" );

    arg5.addTextNode("1");

    msg.saveChanges();

    //System.out.println("Request Message ----------\n");

    //msg.writeTo( System.out );

    // Make SOAP call

    SOAPMessage reply = connection.call( msg, "http://fakeserver/MRcgi/MRWebServices.pl" );

    connection.close();

    //System.out.println("Reply Message ----------\n");

    //reply.writeTo( System.out );

    // Get result

    SOAPBody replybody = reply.getSOAPPart().getEnvelope().getBody();

    // Check for error

    if( replybody.hasFault() )

    {

    throw new Exception( replybody.getFault().getFaultString() );

    }

    DumpSOAPElement( replybody, 0 );

    }

    catch( Exception ex )

    {

    ex.printStackTrace();

    }

    }

    }

    DB:2.62:Need Help - Simple Api Issue - Footprints Service Core / Java xc


    I'm attempting to run a simple java program to get details on a ticket in Footprints Service Core. I need to know:

    1. Where do I insert the username I need to authenticate?

    2. Where do I insert the password I need to authenticate?

    3. Do I need to specify a ticket number that I want to get the details on or does this program pull multiple tickets?

    4. Is there anything else I need to get a "hello world" version of this working?

    The program is an example from the user guide. I'm using version 11.6 of FPSC. The class is below:

    Thanks for your help!

    import javax.xml.soap.*;

    //enable soap functionality

    public class GetIssueDetails

    {

    public static String GetIndent( int num )

    {

    String s = "";

    for( int i = 0; i num; i++ )

    {

    s = s + " ";

    }

    return s;

    }

    public static void DumpSOAPElement(SOAPElement el, int indent) throws Exception

    {

    java.util.Iterator it = el.getChildElements();

    while( it.hasNext())

    {

    String indstr = GetIndent( indent );

    Object obj = it.next();

    if( obj instanceof SOAPElement )

    {

    SOAPElement ele = (SOAPElement)obj;

    System.out.println( indstr + "-----------------------------" );

    System.out.println( indstr + ele.getElementName().getLocalName() );

    System.out.println( indstr + "-----------------------------" );

    DumpSOAPElement( ele, indent + 4 );

    }

    else if( obj instanceof Text )

    {

    Text txt = (Text)obj;

    System.out.println( indstr + txt.getValue() + "\n" );

    }

    }

    }

    public static void main( String[] args )

    {

    try

    {

    // Comment this out for NO proxy.

    /*java.util.Properties props = System.getProperties();

    props.put( "http.proxyHost", "localhost" );

    props.put( "http.proxyPort", "8888" );

    */

    // Setup SOAP message.

    SOAPConnectionFactory scf = SOAPConnectionFactory.newInstance();

    SOAPConnection connection = scf.createConnection();

    MessageFactory msgFactory = MessageFactory.newInstance();

    SOAPMessage msg = msgFactory.createMessage();

    SOAPEnvelope env = msg.getSOAPPart().getEnvelope();

    env.addNamespaceDeclaration( "xsi", "http://www.w3.org/1999/XMLSchema-instance" );

    env.addNamespaceDeclaration( "xsd", "http://www.w3.org/1999/XMLSchema" );

    env.addNamespaceDeclaration( "namesp2", "http://xml.apache.org/xml-soap" );

    env.addNamespaceDeclaration( "SOAP-ENC", "http://schemas.xmlsoap.org/soap/encoding/" );

    // Compose SOAP body.

    SOAPBody body = env.getBody();

    SOAPElement invoke = body.addChildElement(

    env.createName("MRWebServices__getIssueDetails", "namesp1","MRWebServices") );

    SOAPElement arg1 = invoke.addChildElement( env.createName("user") );

    arg1.addAttribute( env.createName("type","xsi",""), "xsd:string" );

    arg1.addTextNode("WebServices");

    SOAPElement arg2 = invoke.addChildElement( env.createName("password") );

    arg2.addAttribute( env.createName("type","xsi",""), "xsd:string" );

    arg2.addTextNode("fakepassword");

    SOAPElement arg3 = invoke.addChildElement( env.createName("extrainfo") );

    arg3.addAttribute( env.createName("type","xsi",""), "xsd:string" );

    SOAPElement arg4 = invoke.addChildElement( env.createName("projectnumber") );

    arg4.addAttribute( env.createName("type","xsi",""), "xsd:int" );

    arg4.addTextNode("78");

    SOAPElement arg5 = invoke.addChildElement( env.createName("mrid") );

    arg5.addAttribute( env.createName("type","xsi",""), "xsd:int" );

    arg5.addTextNode("1");

    msg.saveChanges();

    //System.out.println("Request Message ----------\n");

    //msg.writeTo( System.out );

    // Make SOAP call

    SOAPMessage reply = connection.call( msg, "http://fakeserver/MRcgi/MRWebServices.pl" );

    connection.close();

    //System.out.println("Reply Message ----------\n");

    //reply.writeTo( System.out );

    // Get result

    SOAPBody replybody = reply.getSOAPPart().getEnvelope().getBody();

    // Check for error

    if( replybody.hasFault() )

    {

    throw new Exception( replybody.getFault().getFaultString() );

    }

    DumpSOAPElement( replybody, 0 );

    }

    catch( Exception ex )

    {

    ex.printStackTrace();

    }

    }

    }

  • RELEVANCY SCORE 2.62

    DB:2.62:How To Work With Xsl 7f



    Hi

    I have a scenario RFC - RFC Adapter - XI - SOAP Adapter - Web Service scenario.

    What we see is that the external vendor wants the SOAP to be in "documet-literal wrapped" whereas XI is returning is as "document literal".

    We dont want to change wsdl, the operation soap body are going as two parts we want the soap body in operation,i think this can be achieved by xsl stylesheet,Can any one please brief us about xsl stylesheet as a second mapping step in interface maping.I dint work on xsl before......

    Advance thanx for ur help

    Sriram

    DB:2.62:How To Work With Xsl 7f


    Hi Sriram,

    I had this problem before in an identical scenario!

    I fix it using XSLT extension (ABAP Engine). All I did was following the steps provided in the Robert Eijpe weblog /people/r.eijpe/blog/2005/11/04/using-abap-xslt-extensions-for-xi-mapping

    In my case I didnt need a second mapping, I did only one mapping between outbound and inbound interface.

    Follow this tutorial; it helps you

    Cheers,

    Ricardo.

  • RELEVANCY SCORE 2.61

    DB:2.61:Xsi, Python And Pyqt ja


    Hello o/I would like to know if anyone of you tried to write some tools in Python with PyQT interface in XSI?

    DB:2.61:Xsi, Python And Pyqt ja

    Thanx Scaron, I'll give a look at your tools :cool2:

  • RELEVANCY SCORE 2.61

    DB:2.61:Dynamic Client For Document Styled Webservice 18


    Hi ,
    I created a document styled webservice when I try to run it using DII client I am getting the following problem

    Exception in thread "Main Thread" javax.xml.rpc.JAXRPCException: failed to invoke operation 'testOperation' due to an error in the soap layer (SAAJ); nested exception is: Message[ failed to serialize interface javax.xml.soap.SOAPElementweblogic.xml.schema.binding.SerializationException: mapping lookup failure. class=interface javax.xml.soap.SOAPElement class context=TypedClassContext{schemaType=['http://www.examples.com/types']:testOperation}]StackTrace[

    Can anybody give me a simple example of creating document styled webservice and DII client using weblogic workshop 9.2

    Thanks
    Sksrinu

    DB:2.61:Dynamic Client For Document Styled Webservice 18

    Hi ,
    I created a document styled webservice when I try to run it using DII client I am getting the following problem

    Exception in thread "Main Thread" javax.xml.rpc.JAXRPCException: failed to invoke operation 'testOperation' due to an error in the soap layer (SAAJ); nested exception is: Message[ failed to serialize interface javax.xml.soap.SOAPElementweblogic.xml.schema.binding.SerializationException: mapping lookup failure. class=interface javax.xml.soap.SOAPElement class context=TypedClassContext{schemaType=['http://www.examples.com/types']:testOperation}]StackTrace[

    Can anybody give me a simple example of creating document styled webservice and DII client using weblogic workshop 9.2

    Thanks
    Sksrinu

  • RELEVANCY SCORE 2.61

    DB:2.61:Soap Headers And Jax-Rpc Dii ff


    Hi,

    I'm trying to call a web service using the DII stuff. The web-service returns an response object as you'd expect, but also returns some values in the SOAP-Header. These values need to be used by my client as they contain session related data that is required in subsequent calls to the web service. The problem I'm having is that I cannot work out how to obtain these values from the header using the DII client - the Call object seems only to return the contents of the response object. Likewise, there seems to be no way to set the headers (which I have to do on subsequent calls). I was wondering if there is something more complex that I need to do, or maybe if I have to create my own SOAP Envelope and pass that into the Call.
    The one option that is definately not possible is to generate stubs for my web-service - it has to be totally dynamic with the Call based entirely on the WSDL.

    Grateful for any help.

    DB:2.61:Soap Headers And Jax-Rpc Dii ff

    Hi ,

    have you already solve ya problem? =)

    I would liek to knwo how to make DII dynamic. =)

    Thanks

  • RELEVANCY SCORE 2.60

    DB:2.60:Document Style Web Service Example? z7


    Hi,

    Can somebody from SUN please post a document style web service example? I'm running JWSDP-12.

    In one of my previous posts titled "wscompile trouble" (unanswered) I mentioned I was having trouble with the document style soap binding.
    I was using JWSDP 1.1 and apparently that version did not support the document style soap binding. That's fine. I've upgraded to version 1.2.

    I did some experimentation and the results are confusing. I started with a wsdl that looks like the following.

    wsdl:message name="callTXLifeRequest"
    wsdl:part name="txLifeMessage" element="txlife:TXLife"/
    /wsdl:message

    wsdl:message name="callTXLifeResponse"
    wsdl:part name="return" element="txlife:TXLife"/
    /wsdl:message

    wsdl:portType name="MyIntf"
    wsdl:operation name="callTXLife" parameterOrder="txLifeMessage"
    wsdl:input message="tns:callTXLifeRequest"/
    wsdl:output message="tns:callTXLifeResponse"/
    /wsdl:operation
    /wsdl:portType

    wsdl:binding name="MySoapBinding" type="tns:MyIntf"
    wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/
    wsdl:operation name="callTXLife"
    wsdlsoap:operation soapAction=""/
    wsdl:input
    wsdlsoap:body use="literal"/
    /wsdl:input
    wsdl:output
    wsdlsoap:body use="literal"/
    /wsdl:output
    /wsdl:operation
    /wsdl:binding

    The TXLife schema is pretty big and about 4 level deep using imports. The first problem is that when I run this through wscompile it fails with a stack overflow exception.

    wscompile -keep -verbose -import -f:documentliteral -f:nodatabinding config.xml

    java.lang.reflect.InvocationTargetException
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
    Caused by: java.lang.StackOverflowError

    If I use a smaller element as the value for the element attribute in the part definition it works BUT, it generates an interface that looks like this:

    public interface MyIntf extends java.rmi.Remote {
    public javax.xml.soap.SOAPElement callTXLife(javax.xml.soap.SOAPElement txLifeMessage) throws
    java.rmi.RemoteException;
    }

    The fun part begins when I try to generate the server stuff. This is what the output for wscompile is:

    wscompile -cp . -keep -verbose -gen:server serverconfig.xml

    [creating model: test]
    [creating service: Test]
    [creating port: MyIntf]
    [creating operation: callTXLife]
    error: Type "javax.xml.soap.SOAPElement" implements more than one interface, interfaces: "javax.xml.soap.Node", "org.w3c
    .dom.Element" ...

    Can somebody see what I'm doing wrong? How am I supposed to define either the WSDL or the service remote interface for a document style webservice.

    And the icing on the cake: this is from the release notes for JWSDP 1.2.

    In the what's new section:
    "DII and dynamic proxy support for rpc/literal and document/literal"
    and a couple of lines down in the known problems section:
    "4855319: This release does not support DII and dynamic proxy for the document literal and wrapper style. It is conformant with the WS-I Basic Profile Document literal mappings."
    Can somebody please enlighten me?

    DB:2.60:Document Style Web Service Example? z7

    Hi

    I also have the same problem with document-style literal encoding (Using JWSDP 1.3) and on wscompile I get the message:

    error: Type "javax.xml.soap.SOAPElement" implements more than one interface, interfaces: javax.xml.soap.Node", "org.w3c.dom.Element" ...I am desparately in need of a solution to this problem, as I have a deadline! (don't we all :-)

  • RELEVANCY SCORE 2.60

    DB:2.60:Generating Soap/Xml Via Wsdl Without Actually Making Call To The Service 88


    I'm fairly new to web services so forgive me if I say something stupid. :) Currently my employer has web services that get called by using Glue to bind to a service / create a proxy and then make the call (passing in the appropriate objects that need to be serialized to XML) to the web service. When Glue generates the SOAP/XML message, it provides lots of namespace information and xsi/xsd information for each element, all based off of the WSDL.

    We're now tasked with generating the same type of SOAP/XML information and putting the resulting SOAP messages on a queue to be sent to some middleware that will process the SOAP/XML instead of making a call to the webservice directly. Is there any way to emulate a call to a webservice by referencing the .WSDL and then capturing the SOAP/XML that Glue (or Axis, or...) would generate? I can use Glue to serialize the objects I'm working with, but the resulting XML doesn't get the descriptive information (namespaces prefixes, xsi/xsd info) that is generated when using Glue or Axis. I've thought about trying to create a listener or some sort and capturing the SOAP message before it would be sent to the server, but since we're not even supposed to be making a call to a service that won't really help. Any suggestions on the best way to serialize an object to XML based off of WSDL information without actually making a call to the service?

    DB:2.60:Generating Soap/Xml Via Wsdl Without Actually Making Call To The Service 88

    I'm fairly new to web services so forgive me if I say something stupid. :) Currently my employer has web services that get called by using Glue to bind to a service / create a proxy and then make the call (passing in the appropriate objects that need to be serialized to XML) to the web service. When Glue generates the SOAP/XML message, it provides lots of namespace information and xsi/xsd information for each element, all based off of the WSDL.

    We're now tasked with generating the same type of SOAP/XML information and putting the resulting SOAP messages on a queue to be sent to some middleware that will process the SOAP/XML instead of making a call to the webservice directly. Is there any way to emulate a call to a webservice by referencing the .WSDL and then capturing the SOAP/XML that Glue (or Axis, or...) would generate? I can use Glue to serialize the objects I'm working with, but the resulting XML doesn't get the descriptive information (namespaces prefixes, xsi/xsd info) that is generated when using Glue or Axis. I've thought about trying to create a listener or some sort and capturing the SOAP message before it would be sent to the server, but since we're not even supposed to be making a call to a service that won't really help. Any suggestions on the best way to serialize an object to XML based off of WSDL information without actually making a call to the service?

  • RELEVANCY SCORE 2.60

    DB:2.60:How To Effectively Send Large Strings Over Soap 8a



    I have to provide a Jboss web service which returns documents. The clients are standalone java apps that use JWSDP/JAXRPC stack to DII into the JBoss WS.Basically I have to return large strings and can be in several MBytes in size. What is the most effective way of returning such Strings? Note that the clients are standalone Java Apps using JWSDP/JAXRPC, so any solution should take that into account.Has anybody done that before? Any help/pointers on this issue is appreciated.Server : JBOSS 4.0.1 SP1Client : Java 1.4.1 with JAXRPC [JWSDP 1.5 stack]OS : Linux [Server]ThanksDhaval

    DB:2.60:How To Effectively Send Large Strings Over Soap 8a


    I have to provide a Jboss web service which returns documents. The clients are standalone java apps that use JWSDP/JAXRPC stack to DII into the JBoss WS.Basically I have to return large strings and can be in several MBytes in size. What is the most effective way of returning such Strings? Note that the clients are standalone Java Apps using JWSDP/JAXRPC, so any solution should take that into account.Has anybody done that before? Any help/pointers on this issue is appreciated.Server : JBOSS 4.0.1 SP1Client : Java 1.4.1 with JAXRPC [JWSDP 1.5 stack]OS : Linux [Server]ThanksDhaval

  • RELEVANCY SCORE 2.59

    DB:2.59:Calling Dynamic Sharepoint Web Service In Java 1.4 sd


    I am trying to call a dynamic sharepoint web service in Java using DII (Dynamic Invocation Interface)but I kept getting error:unexpected encoding style:  after the invoke expected=http://schemas.xmlsoap.org/soap/encoding/, actual=I am trying to call web service - GetWebCollection()
                String endPoint=http://%SPSERVER/_vti_bin/Webs.asmx;            String nameSpaceUri = xmlns:xsi;            String serviceName = Webs;            String porttype=WebsSoap;             String NS_XSD = http://www.w3.org/2001/XMLSchema;                                     ServiceFactory factory =                 ServiceFactory.newInstance();            Service service =factory.createService(new QName(serviceName));             QName qport = new QName(porttype);                        hpsharepoint.Webs webs = new hpsharepoint.Webs_Impl();            Call call = (Call) webs.createCall(qport);                       call.setProperty(call.USERNAME_PROPERTY,kuser);            call.setProperty(call.PASSWORD_PROPERTY,password);            call.setProperty(Call.ENCODINGSTYLE_URI_PROPERTY, http://schemas.xmlsoap.org/soap/encoding/);            call.setProperty(Call.SOAPACTION_USE_PROPERTY,                 new Boolean(true));            call.setProperty(Call.SOAPACTION_URI_PROPERTY,http://schemas.microsoft.com/sharepoint/soap/GetWebCollection);                        call.setTargetEndpointAddress(endPoint);                      
                            call.setOperationName(                new QName(nameSpaceUri,GetWebCollection));             String[] params = {};
                NodeList list=(NodeList)call.invoke(params);==========================This is the soap 1.1==========================POST /_vti_bin/Webs.asmx HTTP/1.1 Host: server Content-Type: text/xml; charset=utf-8 Content-Length: length SOAPAction: http://schemas.microsoft.com/sharepoint/soap/GetWebCollection ?xml version=1.0 encoding=utf-8? soap:Envelope xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance xmlns:xsd=http://www.w3.org/2001/XMLSchema xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/ soap:Body GetWebCollection xmlns=http://schemas.microsoft.com/sharepoint/soap/ / /soap:Body /soap:Envelope

    DB:2.59:Calling Dynamic Sharepoint Web Service In Java 1.4 sd

    I am trying to call a dynamic sharepoint web service in Java using DII (Dynamic Invocation Interface)but I kept getting error:unexpected encoding style:  after the invoke expected=http://schemas.xmlsoap.org/soap/encoding/, actual=I am trying to call web service - GetWebCollection()
                String endPoint=http://%SPSERVER/_vti_bin/Webs.asmx;            String nameSpaceUri = xmlns:xsi;            String serviceName = Webs;            String porttype=WebsSoap;             String NS_XSD = http://www.w3.org/2001/XMLSchema;                                     ServiceFactory factory =                 ServiceFactory.newInstance();            Service service =factory.createService(new QName(serviceName));             QName qport = new QName(porttype);                        hpsharepoint.Webs webs = new hpsharepoint.Webs_Impl();            Call call = (Call) webs.createCall(qport);                       call.setProperty(call.USERNAME_PROPERTY,kuser);            call.setProperty(call.PASSWORD_PROPERTY,password);            call.setProperty(Call.ENCODINGSTYLE_URI_PROPERTY, http://schemas.xmlsoap.org/soap/encoding/);            call.setProperty(Call.SOAPACTION_USE_PROPERTY,                 new Boolean(true));            call.setProperty(Call.SOAPACTION_URI_PROPERTY,http://schemas.microsoft.com/sharepoint/soap/GetWebCollection);                        call.setTargetEndpointAddress(endPoint);                      
                            call.setOperationName(                new QName(nameSpaceUri,GetWebCollection));             String[] params = {};
                NodeList list=(NodeList)call.invoke(params);==========================This is the soap 1.1==========================POST /_vti_bin/Webs.asmx HTTP/1.1 Host: server Content-Type: text/xml; charset=utf-8 Content-Length: length SOAPAction: http://schemas.microsoft.com/sharepoint/soap/GetWebCollection ?xml version=1.0 encoding=utf-8? soap:Envelope xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance xmlns:xsd=http://www.w3.org/2001/XMLSchema xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/ soap:Body GetWebCollection xmlns=http://schemas.microsoft.com/sharepoint/soap/ / /soap:Body /soap:Envelope

  • RELEVANCY SCORE 2.58

    DB:2.58:Question About Ws Consuming zk



    Hello,I have only the following WSDL file: ?xml version="1.0" encoding="utf-8" ?- definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:xs="http://www.w3.org/2001/XMLSchema" name="IBatValuesservice" targetNamespace="http://tempuri.org/" xmlns:tns="http://tempuri.org/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"----- soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http" /- soap:operation soapAction="urn:BatValuesIntf-IBatValues#GetValoriBat" style="rpc" /- soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:BatValuesIntf-IBatValues" /- soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:BatValuesIntf-IBatValues" /-- soap:address location="http://erg8074.casaccia.enea.it/cgi-bin/getbat.exe/soap/IBatValues" /I would like to know how I can consume this WS from within an EJB. I know I can do a DII call but I would like to know I can consume the WS using the service-ref in the DD starting from a WSDL file.Thank you for the help.

    DB:2.58:Question About Ws Consuming zk


    Hello,I have only the following WSDL file: ?xml version="1.0" encoding="utf-8" ?- definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:xs="http://www.w3.org/2001/XMLSchema" name="IBatValuesservice" targetNamespace="http://tempuri.org/" xmlns:tns="http://tempuri.org/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"----- soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http" /- soap:operation soapAction="urn:BatValuesIntf-IBatValues#GetValoriBat" style="rpc" /- soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:BatValuesIntf-IBatValues" /- soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:BatValuesIntf-IBatValues" /-- soap:address location="http://erg8074.casaccia.enea.it/cgi-bin/getbat.exe/soap/IBatValues" /I would like to know how I can consume this WS from within an EJB. I know I can do a DII call but I would like to know I can consume the WS using the service-ref in the DD starting from a WSDL file.Thank you for the help.

  • RELEVANCY SCORE 2.57

    DB:2.57:Where Do You Set Soap Encodings In Wcf Web Service ... pd


    In standard ASMX Web Services you could set the SOAP Encodings to doc-literal, doc-literal wrapped, and others.  Where do you set this SOAP Encoding in WCF Services?  I've not been successful in locating this in the documentation.
     
    Thanks.

    DB:2.57:Where Do You Set Soap Encodings In Wcf Web Service ... pd

    Hi Madhu,
    I checked out the sample.  I'm trying to get the encoding to be doc-literal. It seems that setting the following attributes on the service should do the trick:
    [ServiceContract(),XmlSerializerFormat(Style = OperationFormatStyle.Document, Use = OperationFormatUse.Literal)]
    However, the encoding of the message is still set to doc-literal wrapped which is the default.  So am I misreading something or is there some other knob I need to tweak?
    Thanks.

  • RELEVANCY SCORE 2.57

    DB:2.57:I Need To Access A Soap Service Which Is Using Rpc/Literal Encoding Instead Of Document/Literal With Wsdl.Exe. But Getting Error When Using Wsdl.Exe To Get The Soap Schema. ck


    i need to access a soap 1.1 webservice using rpc/literal format instead of document/literal with wsdl.exe.
    But .net only supports document/literal formats for soap webservices, and using wsdl.exe gives error that the soapservice is not in the correct format.what is the workaround with this, so i can get the procedures described in the soap wsdl in
    .net.
    thanks
    waqar

    DB:2.57:I Need To Access A Soap Service Which Is Using Rpc/Literal Encoding Instead Of Document/Literal With Wsdl.Exe. But Getting Error When Using Wsdl.Exe To Get The Soap Schema. ck

    Please don't ask the same question twice.John Saunders
    WCF is Web Services. They are not two separate things.
    Use WCF for All New Web Service Development, instead of legacy ASMX or obsolete WSE
    Use File-New Project to create Web Service Projects

  • RELEVANCY SCORE 2.56

    DB:2.56:Exceptions In Invoking Webservice Using Jax-Rpc Dii Client mk


    hi all
    i am trying to invoke a webservice in http://xmethods.net using JAX-RPC DII client
    the client code is

    import javax.xml.namespace.QName;
    import javax.xml.rpc.Call;
    import javax.xml.rpc.ParameterMode;
    import javax.xml.rpc.Service;
    import javax.xml.rpc.ServiceFactory;
    import javax.xml.rpc.encoding.XMLType;
    public class TestClient2{
    public static void main(String args[]) {
    try {
    QName serviceName = new QName("http://www.xmethods.net/sd/BNQuoteService.wsdl","BNQuoteService");
    ServiceFactory factory = ServiceFactory.newInstance();
    Service service = factory.createService(serviceName);
    Call call = (Call)service.createCall();
    QName operationName = new QName("urn:xmethods-BNPriceCheck","getPrice");
    call.setOperationName(operationName);
    call.addParameter("isbn",XMLType.XSD_STRING,String.class,ParameterMode.IN);
    call.setReturnType(XMLType.XSD_FLOAT);
    call.setProperty(Call.OPERATION_STYLE_PROPERTY,"rpc");
    call.setProperty(Call.ENCODINGSTYLE_URI_PROPERTY,"http://schemas.xmlsoap.org/soap/encoding/");
    call.setTargetEndpointAddress("http://services.xmethods.net:80/soap/servlet/rpcrouter");
    Object[] actualArgs = {"0672324229"};
    Float price = (Float) call.invoke(actualArgs);
    System.out.println("price = " + price);
    }
    catch (Throwable t) {
    t.printStackTrace();
    }
    }
    }but i am getting the following Exceptions

    Exception in thread "main" java.lang.NoClassDefFoundError: org.apache.commons.logging.LogFactor
    at org.apache.axis.components.logger.LogFactory.class$(LogFactory.java:84)
    at org.apache.axis.components.logger.LogFactory$1.run(LogFactory.java:84)
    at java.security.AccessController.doPrivileged(Native Method)
    at org.apache.axis.components.logger.LogFactory.getLogFactory(LogFactory.java:80)
    at org.apache.axis.components.logger.LogFactory.clinit(LogFactory.java:72)
    at org.apache.axis.handlers.BasicHandler.clinit(BasicHandler.java:81)
    at org.apache.axis.client.Service.getAxisClient(Service.java:143)
    at org.apache.axis.client.Service.init(Service.java:162)
    at org.apache.axis.client.ServiceFactory.createService(ServiceFactory.java:248)
    at TestClient2.main(TestClient1.java:13)i deployed AXIS in tomcat4.1 in webapps directiory and tested all JARs also by using "happyaxis" servlet

    thanks in advance

    DB:2.56:Exceptions In Invoking Webservice Using Jax-Rpc Dii Client mk

    what could be the reason?
    i did everything rightYou really think so? You think the program just decided to throw an exception even though your code is correct?

    Are there any exceptions chained to this one? Further down in the stack trace it might say "root cause." I ask that because the error you posted doesn't contain much information.

  • RELEVANCY SCORE 2.56

    DB:2.56:Newscene() Crashes Xsi If Called From C# f7


    Using the executeCommand function to call NewScene (or OpenScene) from a C# customProperty causes XSI to crash.If I create the property in jScript this does not happen, but I would like to keep my plugins in c#. The crash probably have something to do with XSI suddently clearing the scene with C# code running (no change for the code to exit properly)Does anyone have a solution or suggestion?Thanks

    DB:2.56:Newscene() Crashes Xsi If Called From C# f7

    I call it on a button press from a customProperty (using the 'executeCommand' function obviously).I have set up the exact same customProperty using jScript and here it does'nt crash (my workaround solution for the moment)

  • RELEVANCY SCORE 2.55

    DB:2.55:Calling A Business Service Based On Operation-Soap Action In Proxy Service 3a


    Hi,
    I have a requirement in which I have to call a business service based on operation-soap action defined in Proxy service wsdl.

    Like in below mentioned wsdl GetPartCostDelta and GetCurrencyList operations are there.But which ever operation I select,It just goes to one business service.
    Is there any way,I can route to some another business service based on the soap action

    proxy service WSDL

    ?xml version="1.0" encoding="UTF-8"?
    wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:ewopcd="urn:com:gm:gpd:schema:ewopartcostdelta" xmlns:gen="urn:com:gm:gpd:schema:genericfault" xmlns:tns="urn:com:gm:gpd:services:ewopartcostdeltaservice" targetNamespace="urn:com:gm:gpd:services:ewopartcostdeltaservice"
    wsdl:types
    xs:schema
    xs:import namespace="urn:com:gm:gpd:schema:ewopartcostdelta" schemaLocation="ewocostdelta.xsd"/
    xs:import namespace="urn:com:gm:gpd:schema:genericfault" schemaLocation="servicefault.xsd"/
    /xs:schema
    /wsdl:types
    wsdl:message name="EWOCurrencyListRequest"
    wsdl:part name="CurrencyListRequest" element="ewopcd:EWOCostDeltaInput"/
    /wsdl:message
    wsdl:message name="EWOCurrencyListResponse"
    wsdl:part name="CurrencyListResponse" element="ewopcd:EWOCurrencyList"/
    /wsdl:message
    wsdl:message name="EWOPartCostDeltaRequest"
    wsdl:part name="PartCostDeltaRequest" element="ewopcd:EWOCostDeltaInput"/
    /wsdl:message
    wsdl:message name="EWOPartCostDeltaResponse"
    wsdl:part name="PartCostDeltaResponse" element="ewopcd:EWOCostDeltaResult"/
    /wsdl:message
    wsdl:message name="EWOPartCostDeltaServiceFault"
    wsdl:part name="PartCostDeltaServiceFault" element="gen:ServiceFault"/
    /wsdl:message
    wsdl:portType name="EWOPartCostDeltaPortType"
    wsdl:operation name="GetCurrencyList"
    wsdl:input name="EWOCurrencyListRequest" message="tns:EWOCurrencyListRequest"/
    wsdl:output name="EWOCurrencyListResponse" message="tns:EWOCurrencyListResponse"/
    wsdl:fault name="EWOPartCostDeltaServiceFault" message="tns:EWOPartCostDeltaServiceFault"/
    /wsdl:operation
    wsdl:operation name="GetPartCostDelta"
    wsdl:input name="EWOPartCostDeltaRequest" message="tns:EWOPartCostDeltaRequest"/
    wsdl:output name="EWOPartCostDeltaResponse" message="tns:EWOPartCostDeltaResponse"/
    wsdl:fault name="EWOPartCostDeltaServiceFault" message="tns:EWOPartCostDeltaServiceFault"/
    /wsdl:operation
    /wsdl:portType
    wsdl:binding name="EWOPartCostDeltaBinding" type="tns:EWOPartCostDeltaPortType"
    soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/
    wsdl:operation name="GetCurrencyList"
    soap:operation soapAction="GetCurrencyList" style="document"/
    wsdl:input
    soap:body use="literal"/
    /wsdl:input
    wsdl:output
    soap:body use="literal"/
    /wsdl:output
    wsdl:fault name="EWOPartCostDeltaServiceFault"
    soap:fault name="EWOCostDeltaServiceFault" use="literal"/
    /wsdl:fault
    /wsdl:operation
    wsdl:operation name="GetPartCostDelta"
    soap:operation soapAction="GetPartCostDelta" style="document"/
    wsdl:input
    soap:body use="literal"/
    /wsdl:input
    wsdl:output
    soap:body use="literal"/
    /wsdl:output
    wsdl:fault name="EWOPartCostDeltaServiceFault"
    soap:fault name="EWOCostDeltaServiceFault" use="literal"/
    /wsdl:fault
    /wsdl:operation
    /wsdl:binding
    wsdl:service name="EWOPartCostDeltaService"
    wsdl:port name="EWOPartCostDeltaPort" binding="tns:EWOPartCostDeltaBinding"
    soap:address location="https://localhost/EWOPartCostDelta"/
    /wsdl:port
    /wsdl:service
    /wsdl:definitions

  • RELEVANCY SCORE 2.55

    DB:2.55:Not Able To Invoke Webservice(Document/Literal ) Using Dii ? z1


    I am able to invoke webservice over http using dynamic invocation interface with *(Call.OPERATION_STYLE_PROPERTY,"rpc"),* but not able to get response using (*Call.OPERATION_STYLE_PROPERTY,"document")* or response using *(Call.OPERATION_STYLE_PROPERTY,"documentwrapped")* and getting below given error -

    Exception in thread "main" javax.xml.rpc.JAXRPCException: failed to invoke operation 'displayName' due to an error in the soap layer (SAAJ); nested exception is: Message[ failed to serialize interface javax.xml.soap.SOAPElementweblogic.xml.schema.binding.SerializationException: mapping lookup failure. class=interface javax.xml.soap.SOAPElement class context=TypedClassContext{schemaType=['http://www.bea.com/examples/Handler']:displayName}]StackTrace[

    javax.xml.soap.SOAPException: failed to serialize interface javax.xml.soap.SOAPElementweblogic.xml.schema.binding.SerializationException: mapping lookup failure. class=interface javax.xml.soap.SOAPElement class context=TypedClassContext{schemaType=['http://www.bea.com/examples/Handler']:displayName}
    at weblogic.webservice.core.DefaultPart.invokeSerializer(DefaultPart.java:339)
    at weblogic.webservice.core.DefaultPart.toXML(DefaultPart.java:304)
    at weblogic.webservice.core.DefaultMessage.toXML(DefaultMessage.java:651)
    at weblogic.webservice.core.ClientDispatcher.send(ClientDispatcher.java:209)
    at weblogic.webservice.core.ClientDispatcher.dispatch(ClientDispatcher.java:146)
    at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:473)
    at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:459)
    at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:569)
    at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:422)
    at client.XTestClient.main(XTestClient.java:42)
    Caused by: weblogic.xml.schema.binding.SerializationException: mapping lookup failure. class=interface javax.xml.soap.SOAPElement class context=TypedClassContext{schemaType=['http://www.bea.com/examples/Handler']:displayName}
    at weblogic.xml.schema.binding.RuntimeUtils.lookup_serializer(RuntimeUtils.java:155)
    at weblogic.xml.schema.binding.RuntimeUtils.invoke_serializer(RuntimeUtils.java:191)
    at weblogic.xml.schema.binding.RuntimeUtils.invoke_serializer(RuntimeUtils.java:178)
    at weblogic.webservice.core.DefaultPart.invokeSerializer(DefaultPart.java:335)
    ---------------------------------------------------------------------------------------------------
    My generated wsdl file is given below
    ?xml version="1.0" encoding="UTF-8" ?
    - definitions xmlns:wsr="http://www.openuri.org/2002/10/soap/reliability/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:soap12enc="http://www.w3.org/2003/05/soap-encoding" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://www.bea.com/examples/Handler" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:conv="http://www.openuri.org/2002/04/wsdl/conversation/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" targetNamespace="http://www.bea.com/examples/Handler"
    - types xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsr="http://www.openuri.org/2002/10/soap/reliability/" xmlns:soap12enc="http://www.w3.org/2003/05/soap-encoding" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:tns="http://www.bea.com/examples/Handler" xmlns:conv="http://www.openuri.org/2002/04/wsdl/conversation/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
    - xsd:schema xmlns:stns="http://www.bea.com/examples/Handler" xmlns:xsd="http://www.w3.org/2001/XMLSchema" attributeFormDefault="unqualified" targetNamespace="http://www.bea.com/examples/Handler" elementFormDefault="qualified"
    - xsd:element name="displayName"
    - xsd:complexType
    - xsd:sequence
    xsd:element name="string" type="xsd:string" /
    /xsd:sequence
    /xsd:complexType
    /xsd:element
    - xsd:element name="displayNameResponse"
    - xsd:complexType
    - xsd:sequence
    xsd:element name="result" type="xsd:string" /
    /xsd:sequence
    /xsd:complexType
    /xsd:element
    /xsd:schema
    /types
    - message name="displayName"
    part xmlns:partns="http://www.bea.com/examples/Handler" element="partns:displayName" name="parameters" /
    /message
    - message name="displayNameResponse"
    part xmlns:partns="http://www.bea.com/examples/Handler" element="partns:displayNameResponse" name="parameters" /
    /message
    - portType name="testservicePort"
    - operation name="displayName"
    input message="tns:displayName" /
    output message="tns:displayNameResponse" /
    /operation
    /portType
    - binding name="testservicePort" type="tns:testservicePort"
    soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" /
    - operation name="displayName"
    soap:operation style="document" soapAction="" /
    - input
    soap:body use="literal" /
    /input
    - output
    soap:body use="literal" /
    /output
    /operation
    /binding
    - service name="testservice"
    - port name="testservicePort" binding="tns:testservicePort"
    soap:address location="http://localhost:7101/webservices/testuri" /
    /port
    /service
    /definitions
    --------------------------------------------------------------------------Dynamic client code is also given below_______________
    package client;

    import java.net.URL;

    import java.util.Iterator;

    import javax.xml.namespace.QName;
    import javax.xml.rpc.Call;
    import javax.xml.rpc.Service;
    import javax.xml.rpc.ServiceFactory;
    import javax.xml.rpc.soap.SOAPFaultException;

    public class XTestClient {

    public static void main(String args[]) throws Exception{

    try{
    System.setProperty("javax.xml.rpc.ServiceFactory","weblogic.webservice.core.rpc.ServiceFactoryImpl");
    String TARGATENAMESPACE = "http://www.bea.com/examples/Handler";
    QName serviceName = new QName(TARGATENAMESPACE,"testservice");
    QName portName = new QName(TARGATENAMESPACE,"testservicePort");
    QName operationName = new QName(TARGATENAMESPACE,"displayName");
    QName QNAME_TYPE_STRING = new QName("http://www.w3.org/2001/XMLSchema", "string");

    URL wsdlLocation = new URL("http://localhost:7101/webservices/testuri?WSDL");

    ServiceFactory factory = ServiceFactory.newInstance();

    Service service = factory.createService(wsdlLocation, serviceName);

    Iterator it = service.getPorts();

    Call call = service.createCall(portName,operationName);

    call.setProperty(Call.OPERATION_STYLE_PROPERTY,"documentwrapped");
    call.setProperty(Call.SOAPACTION_USE_PROPERTY, Boolean.TRUE);
    call.setProperty(Call.SOAPACTION_URI_PROPERTY, "displayName");
    call.setProperty(Call.ENCODINGSTYLE_URI_PROPERTY,"http://schemas.xmlsoap.org/soap/encoding/");

    String result = (String) call.invoke(new Object[] { "abcd" });
    System.out.println("result is -- "+result);

    }catch(SOAPFaultException e){

    System.out.println("*************** Exception occuredc***********");
    e.printStackTrace();

    }
    }
    }
    ------------------------------------
    Thanks in advance and quick reply will be appreciated.......

    DB:2.55:Not Able To Invoke Webservice(Document/Literal ) Using Dii ? z1

    I am able to invoke webservice over http using dynamic invocation interface with *(Call.OPERATION_STYLE_PROPERTY,"rpc"),* but not able to get response using (*Call.OPERATION_STYLE_PROPERTY,"document")* or response using *(Call.OPERATION_STYLE_PROPERTY,"documentwrapped")* and getting below given error -

    Exception in thread "main" javax.xml.rpc.JAXRPCException: failed to invoke operation 'displayName' due to an error in the soap layer (SAAJ); nested exception is: Message[ failed to serialize interface javax.xml.soap.SOAPElementweblogic.xml.schema.binding.SerializationException: mapping lookup failure. class=interface javax.xml.soap.SOAPElement class context=TypedClassContext{schemaType=['http://www.bea.com/examples/Handler']:displayName}]StackTrace[

    javax.xml.soap.SOAPException: failed to serialize interface javax.xml.soap.SOAPElementweblogic.xml.schema.binding.SerializationException: mapping lookup failure. class=interface javax.xml.soap.SOAPElement class context=TypedClassContext{schemaType=['http://www.bea.com/examples/Handler']:displayName}
    at weblogic.webservice.core.DefaultPart.invokeSerializer(DefaultPart.java:339)
    at weblogic.webservice.core.DefaultPart.toXML(DefaultPart.java:304)
    at weblogic.webservice.core.DefaultMessage.toXML(DefaultMessage.java:651)
    at weblogic.webservice.core.ClientDispatcher.send(ClientDispatcher.java:209)
    at weblogic.webservice.core.ClientDispatcher.dispatch(ClientDispatcher.java:146)
    at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:473)
    at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:459)
    at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:569)
    at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:422)
    at client.XTestClient.main(XTestClient.java:42)
    Caused by: weblogic.xml.schema.binding.SerializationException: mapping lookup failure. class=interface javax.xml.soap.SOAPElement class context=TypedClassContext{schemaType=['http://www.bea.com/examples/Handler']:displayName}
    at weblogic.xml.schema.binding.RuntimeUtils.lookup_serializer(RuntimeUtils.java:155)
    at weblogic.xml.schema.binding.RuntimeUtils.invoke_serializer(RuntimeUtils.java:191)
    at weblogic.xml.schema.binding.RuntimeUtils.invoke_serializer(RuntimeUtils.java:178)
    at weblogic.webservice.core.DefaultPart.invokeSerializer(DefaultPart.java:335)
    ---------------------------------------------------------------------------------------------------
    My generated wsdl file is given below
    ?xml version="1.0" encoding="UTF-8" ?
    - definitions xmlns:wsr="http://www.openuri.org/2002/10/soap/reliability/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:soap12enc="http://www.w3.org/2003/05/soap-encoding" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://www.bea.com/examples/Handler" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:conv="http://www.openuri.org/2002/04/wsdl/conversation/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" targetNamespace="http://www.bea.com/examples/Handler"
    - types xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsr="http://www.openuri.org/2002/10/soap/reliability/" xmlns:soap12enc="http://www.w3.org/2003/05/soap-encoding" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:tns="http://www.bea.com/examples/Handler" xmlns:conv="http://www.openuri.org/2002/04/wsdl/conversation/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
    - xsd:schema xmlns:stns="http://www.bea.com/examples/Handler" xmlns:xsd="http://www.w3.org/2001/XMLSchema" attributeFormDefault="unqualified" targetNamespace="http://www.bea.com/examples/Handler" elementFormDefault="qualified"
    - xsd:element name="displayName"
    - xsd:complexType
    - xsd:sequence
    xsd:element name="string" type="xsd:string" /
    /xsd:sequence
    /xsd:complexType
    /xsd:element
    - xsd:element name="displayNameResponse"
    - xsd:complexType
    - xsd:sequence
    xsd:element name="result" type="xsd:string" /
    /xsd:sequence
    /xsd:complexType
    /xsd:element
    /xsd:schema
    /types
    - message name="displayName"
    part xmlns:partns="http://www.bea.com/examples/Handler" element="partns:displayName" name="parameters" /
    /message
    - message name="displayNameResponse"
    part xmlns:partns="http://www.bea.com/examples/Handler" element="partns:displayNameResponse" name="parameters" /
    /message
    - portType name="testservicePort"
    - operation name="displayName"
    input message="tns:displayName" /
    output message="tns:displayNameResponse" /
    /operation
    /portType
    - binding name="testservicePort" type="tns:testservicePort"
    soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" /
    - operation name="displayName"
    soap:operation style="document" soapAction="" /
    - input
    soap:body use="literal" /
    /input
    - output
    soap:body use="literal" /
    /output
    /operation
    /binding
    - service name="testservice"
    - port name="testservicePort" binding="tns:testservicePort"
    soap:address location="http://localhost:7101/webservices/testuri" /
    /port
    /service
    /definitions
    --------------------------------------------------------------------------Dynamic client code is also given below_______________
    package client;

    import java.net.URL;

    import java.util.Iterator;

    import javax.xml.namespace.QName;
    import javax.xml.rpc.Call;
    import javax.xml.rpc.Service;
    import javax.xml.rpc.ServiceFactory;
    import javax.xml.rpc.soap.SOAPFaultException;

    public class XTestClient {

    public static void main(String args[]) throws Exception{

    try{
    System.setProperty("javax.xml.rpc.ServiceFactory","weblogic.webservice.core.rpc.ServiceFactoryImpl");
    String TARGATENAMESPACE = "http://www.bea.com/examples/Handler";
    QName serviceName = new QName(TARGATENAMESPACE,"testservice");
    QName portName = new QName(TARGATENAMESPACE,"testservicePort");
    QName operationName = new QName(TARGATENAMESPACE,"displayName");
    QName QNAME_TYPE_STRING = new QName("http://www.w3.org/2001/XMLSchema", "string");

    URL wsdlLocation = new URL("http://localhost:7101/webservices/testuri?WSDL");

    ServiceFactory factory = ServiceFactory.newInstance();

    Service service = factory.createService(wsdlLocation, serviceName);

    Iterator it = service.getPorts();

    Call call = service.createCall(portName,operationName);

    call.setProperty(Call.OPERATION_STYLE_PROPERTY,"documentwrapped");
    call.setProperty(Call.SOAPACTION_USE_PROPERTY, Boolean.TRUE);
    call.setProperty(Call.SOAPACTION_URI_PROPERTY, "displayName");
    call.setProperty(Call.ENCODINGSTYLE_URI_PROPERTY,"http://schemas.xmlsoap.org/soap/encoding/");

    String result = (String) call.invoke(new Object[] { "abcd" });
    System.out.println("result is -- "+result);

    }catch(SOAPFaultException e){

    System.out.println("*************** Exception occuredc***********");
    e.printStackTrace();

    }
    }
    }
    ------------------------------------
    Thanks in advance and quick reply will be appreciated.......

  • RELEVANCY SCORE 2.54

    DB:2.54:Rpc/Encoded Style On Jboss4.0.4ga ms



    Hi,I tried JBoss4.0.4GA which includes jboss-1.0.0.GA.I have a couple of question...
    1: Creating Web service on JBoss4.0.4GA (jboss-1.0.0.GA Web Service), rpc/encoded style WSDL cannot be used?--if no, any solutions to support rpc/encoded style WSDL?2: Can client send soap-encoded SOAPMessage to Web service on JBoss4.0.4GA (jboss-1.0.0.GA Web service)?--I created AXIS DII and sent soap-encoded style SOAPMessage, but the server throwed exception: "javax.xml.rpc.JAXRPCException: Cannot find child element: **"I created AXIS stub from WSDL(rpc/literal) and called the same Web service. It processed successfully.So I understand Jboss-1.0.0.GA Web service only supports literal style in both side(server and client). Am I correct? Any solutions available for encoded syle ??? Any information will be appreciated! -MIE

    DB:2.54:Rpc/Encoded Style On Jboss4.0.4ga ms


    Thomas,Thank you for your reply.OK, I will change rpc/encoded to rpc/literal...MIE

  • RELEVANCY SCORE 2.54

    DB:2.54:Help: Apache Soap &Amp; Perl kc


    Now I'm developing a J2EE project. In this project, we must call some perl with Apache SOAP.

    I have installed Apache SOAP and Active Perl.
    I have tried to call some java code with Apache SOAP successfully.

    When I try to call perl with Apache SOAP, some error messages are promoted.

    BSF Error: UnsatisfiedLinkError loading library:bsfactivescript engine no bsfactivescriptengine in java.library.path

    How to call perl with Apache SOAP???

    Thanks!

    DB:2.54:Help: Apache Soap &Amp; Perl kc

    Now I'm developing a J2EE project. In this project, we must call some perl with Apache SOAP.

    I have installed Apache SOAP and Active Perl.
    I have tried to call some java code with Apache SOAP successfully.

    When I try to call perl with Apache SOAP, some error messages are promoted.

    BSF Error: UnsatisfiedLinkError loading library:bsfactivescript engine no bsfactivescriptengine in java.library.path

    How to call perl with Apache SOAP???

    Thanks!

  • RELEVANCY SCORE 2.54

    DB:2.54:Facing Issue While Trying To Create Ci In Bmc Footprint Cmdb Through Web-Service Api Call In Java Code. 97



    Hi,

    I am trying to create a CI through web service API call in BMC footpring 11.6 through JAVA client code in the similar way as code given for create issue but it throwing very generic SOAP error,

    Nov 17, 2014 12:19:19 PM com.sun.xml.internal.messaging.saaj.soap.MessageImpl identifyContentType

    SEVERE: SAAJ0537: Invalid Content-Type. Could be an error message instead of a SOAP message

    com.sun.xml.internal.messaging.saaj.SOAPExceptionImpl: com.sun.xml.internal.messaging.saaj.SOAPExceptionImpl:

    My code is herein please help me to identify what is wrong

    import javax.xml.soap.MessageFactory;

    import javax.xml.soap.SOAPBody;

    import javax.xml.soap.SOAPConnection;

    import javax.xml.soap.SOAPConnectionFactory;

    import javax.xml.soap.SOAPElement;

    import javax.xml.soap.SOAPEnvelope;

    import javax.xml.soap.SOAPMessage;

    import javax.xml.soap.Text;

    public class CreateCI {

    public static void main( String[] args ){

    try{

    // Comment this out for NO proxy.

    /* java.util.Properties props = System.getProperties();

    props.put( "http.proxyHost", "localhost" );

    props.put( "http.proxyPort", "8888" );*/

    // Setup SOAP message.

    SOAPConnectionFactory scf = SOAPConnectionFactory.newInstance();

    SOAPConnection connection = scf.createConnection();

    MessageFactory msgFactory = MessageFactory.newInstance();

    SOAPMessage msg = msgFactory.createMessage();

    SOAPEnvelope env = msg.getSOAPPart().getEnvelope();

    env.addNamespaceDeclaration( "xsi", "http://www.w3.org/1999/XMLSchema-instance" );

    env.addNamespaceDeclaration( "xsd", "http://www.w3.org/1999/XMLSchema" );

    env.addNamespaceDeclaration( "namesp2", "http://xml.apache.org/xml-soap" );

    env.addNamespaceDeclaration( "SOAP-ENC", "http://schemas.xmlsoap.org/soap/encoding/" );

    // Compose SOAP body.

    SOAPBody body = env.getBody();

    SOAPElement invoke = body.addChildElement(

    env.createName("MRWebServices__createCI", "namesp1","MRWebServices") );

    SOAPElement arg1 = invoke.addChildElement( env.createName("user") );

    arg1.addAttribute( env.createName("type","xsi",""), "xsd:string" );

    arg1.addTextNode("myuser");

    SOAPElement arg2 = invoke.addChildElement( env.createName("password") );

    arg2.addAttribute( env.createName("type","xsi",""), "xsd:string" );

    arg2.addTextNode("^mypasswordP");

    SOAPElement arg3 = invoke.addChildElement( env.createName("extrainfo") );

    arg3.addAttribute( env.createName("type","xsi",""), "xsd:string" );

    SOAPElement arg4 = invoke.addChildElement( env.createName("args") );

    arg4.addAttribute( env.createName("type","xsi",""), "namesp2:SOAPStruct" );

    SOAPElement arg4_1 = arg4.addChildElement( env.createName("CMDB_ID") );

    arg4_1.addAttribute( env.createName("type","xsi",""), "xsd:int" );

    arg4_1.addTextNode("2");

    SOAPElement arg4_2 = arg4.addChildElement( env.createName("CI_TYPE_ID") );

    arg4_2.addAttribute( env.createName("type","xsi",""), "xsd:int" );

    arg4_2.addTextNode("3");

    SOAPElement arg4_3 = arg4.addChildElement( env.createName("STATUS") );

    arg4_3.addAttribute( env.createName("type","xsi",""), "xsd:string" );

    arg4_3.addTextNode("Building");

    /*SOAPElement arg4_4 = arg4.addChildElement( env.createName("SUBMIT_SYSTIMESTAMP") );

    arg4_4.addAttribute( env.createName("type","xsi",""), "xsd:string" );

    arg4_4.addTextNode("Building, In Service");

    SOAPElement arg4_5 = arg4.addChildElement( env.createName("SUBMIT_USERTIMESTAMP") );

    arg4_5.addAttribute( env.createName("type","xsi",""), "xsd:string" );

    arg4_5.addTextNode("Building, In Service");

    SOAPElement arg4_6 = arg4.addChildElement( env.createName("LASTEDIT_USERTIMESTAMP") );

    arg4_6.addAttribute( env.createName("type","xsi",""), "xsd:string" );

    arg4_6.addTextNode("Building, In Service");*/

    msg.saveChanges();

    //System.out.println("Request Message ----------\n");

    //msg.writeTo( System.out );

    // Make SOAP call

    SOAPMessage reply = connection.call( msg, "https://xyz.com/MRcgi/MRWebServices.pl" );

    connection.close();

    //System.out.println("Reply Message ----------\n");

    //reply.writeTo( System.out );

    // Get result

    SOAPBody replybody = reply.getSOAPPart().getEnvelope().getBody();

    // Check for error

    if( replybody.hasFault() ){

    throw new Exception( replybody.getFault().getFaultString() );

    }

    // Iterate through the result body, extracting information

    java.util.Iterator it = replybody.getChildElements();

    while( it.hasNext() ){

    Object obj = it.next();

    if( obj instanceof SOAPElement ){

    SOAPElement ele = (SOAPElement)obj;

    String s = ele.getElementName().getLocalName();

    if( s.equals("MRWebServices__createCIResponse") ){ //MRWebServices__createIssueResponse

    java.util.Iterator it2 = ele.getChildElements();

    while( it2.hasNext() ){

    Object obj2 = it2.next();

    if( obj2 instanceof SOAPElement ){

    SOAPElement ele2 = (SOAPElement)obj2;

    String s2 = ele2.getElementName().getLocalName();

    if( s2.equals("return") ){

    java.util.Iterator it3 = ele2.getChildElements();

    while( it3.hasNext() ){

    Object obj3 = it3.next();

    if( obj3 instanceof Text ){

    Text txt = (Text)obj3;

    System.out.println( "Issue " + txt.getValue() + " has been created." );

    }

    }

    }

    }

    }

    }

    }

    }

    }

    catch( Exception ex ){

    ex.printStackTrace();

    }

    }

    }

    DB:2.54:Facing Issue While Trying To Create Ci In Bmc Footprint Cmdb Through Web-Service Api Call In Java Code. 97


    It seems that people not using BMC footprint web services API through JAVA or any other language, there is no response from community so far. Good new for all those are facing this issue I able to resolve it by own actuall it is not mentioned in reference guide but attribute field also mandatory for creating CI through API call, when tried with all mandatory fields and attributes(optional as per the fp 11.6 reference guide) it works for me.

    Thanks

  • RELEVANCY SCORE 2.54

    DB:2.54:Simpledeserializer Exception 91



    Trying to get a simple webservice running using JBossWS but getting the following exception on the server side. I was testing out a Complex Type with an array.org.xml.sax.SAXException: SimpleDeserializer encountered a child element, which is NOT expected, in something it was trying to deserialize.Current setup:JBoss 4.0.3RC2 (we are targeting this release)wscompile (wsdp 1.6)I'm using Axis 1.2.1 for DII client.wsdl
    ?xml version="1.0" encoding="UTF-8"?

    definitions name="WsTestService" targetNamespace="http://wstest/"
    xmlns:tns="http://wstest/" xmlns="http://schemas.xmlsoap.org/wsdl/"
    xmlns:ns2="http://wstest/types" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
    types
    schema targetNamespace="http://wstest/types"
    xmlns:tns="http://wstest/types"
    xmlns:soap11-enc="http://schemas.xmlsoap.org/soap/encoding/"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
    xmlns="http://www.w3.org/2001/XMLSchema"
    complexType name="MyMsg"
    sequence
    element name="data" type="string" nillable="true" minOccurs="0"
    maxOccurs="unbounded"/
    element name="item1" type="string" nillable="true"/
    element name="item2" type="string" nillable="true"/
    /sequence
    /complexType
    /schema
    /types
    message name="WsTestEndpoint_pingMsg"
    part name="MyMsg_1" type="ns2:MyMsg"/
    /message
    message name="WsTestEndpoint_pingMsgResponse"
    part name="result" type="ns2:MyMsg"/
    /message
    portType name="WsTestEndpoint"
    operation name="pingMsg" parameterOrder="MyMsg_1"
    input message="tns:WsTestEndpoint_pingMsg"/
    output message="tns:WsTestEndpoint_pingMsgResponse"/
    /operation
    /portType
    binding name="WsTestEndpointBinding" type="tns:WsTestEndpoint"
    soap:binding transport="http://schemas.xmlsoap.org/soap/http"
    style="rpc"/
    operation name="pingMsg"
    soap:operation soapAction=""/
    input
    soap:body use="literal" namespace="http://wstest/"/
    /input
    output
    soap:body use="literal" namespace="http://wstest/"/
    /output
    /operation
    /binding
    service name="WsTestService"
    port name="WsTestEndpointPort" binding="tns:WsTestEndpointBinding"
    soap:address location="REPLACE_WITH_ACTUAL_URL"/
    /port
    /service
    /definitions

    DB:2.54:Simpledeserializer Exception 91


    You probably need to go to Apache and use whatever they offer in terms of support to get this answered.

  • RELEVANCY SCORE 2.54

    DB:2.54:Soap Client Fails To Validate Soap Response zp



    Hi,

    I have developed and deployed a document style web service (with use="literal")
    on Web Logic 7.0 server using servicegen ant task. I am using a non Web Logic
    client to invoke this service.

    The WSDL generated by the service, uses "elementFormDefault="qualified" but in
    the SOAP response, all elements are not qualified by namespace. The client is
    failing to validate this SOAP response against the types defined in WSDL file
    because of this.

    I would like to know how to generate a SOAP response with all elements qualified
    with namaspace.

    Thanks
    Prasgh

    DB:2.54:Soap Client Fails To Validate Soap Response zp

    http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=articlegroup=weblogic.developer.interest.webservicesitem=2831utag=

    prasgh wrote:

    Hi Bruce,

    Thanks for your reply. It works fine with 8.1 but it doesn't with WLS 7.0. What
    we have is 7.0. How can I resolve this on 7.0

    Appreciate your help.

    Thanks
    Prasgh
    Bruce Stephens hbs@nospam.bea.com wrote:
    Hello,

    Are you using the latest WLS 7.0SP2?

    We recently updated the interop instance: http://webservice.bea.com:7001
    with WLS 8.1 so I don't have v7 stack (online) to show you, however I
    did try it locally using the Compound1 test (doc/lit with
    "elementFormDefault="qualified") and it works as shown below.

    HTHs,
    Bruce

    !--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
    ns100:x_Person xmlns:ns100="http://soapinterop.org/xsd"
    Male="true"
    Name="sample string"
    ns101:Age
    xmlns:ns101="http://soapinterop.org/xsd"20.2/ns101:Age
    ns102:ID
    xmlns:ns102="http://soapinterop.org/xsd"10.1/ns102:ID
    /ns100:x_Person
    /env:Body
    /env:Envelope

    Response from the server

    !--RESPONSE.................--
    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
    ns100:result_Person xmlns:ns100="http://soapinterop.org/xsd"
    Name="sample string"
    Male="true"
    ns101:Age
    xmlns:ns101="http://soapinterop.org/xsd"20.2/ns101:Age
    ns102:ID
    xmlns:ns102="http://soapinterop.org/xsd"10.1/ns102:ID
    /ns100:result_Person
    /env:Body
    /env:Envelope

    prasgh@hotmail.com wrote:
    Hi,

    I have developed and deployed a document style web service (with use="literal")
    on Web Logic 7.0 server using servicegen ant task. I am using a nonWeb Logic
    client to invoke this service.

    The WSDL generated by the service, uses "elementFormDefault="qualified"but in
    the SOAP response, all elements are not qualified by namespace. Theclient is
    failing to validate this SOAP response against the types defined inWSDL file
    because of this.

    I would like to know how to generate a SOAP response with all elementsqualified
    with namaspace.

    Thanks
    Prasgh

  • RELEVANCY SCORE 2.53

    DB:2.53:Rpc/Literal Generates Soap Encoded Array cs



    Hi,I have a basic example that is not doing what it is suppose to do. I am running a few tests on multiple WS platforms, and I can?t get this one to work with JBossWS (JBoss 4.0.2 have tried 4.0.3 RC1 as well)I am using org.jboss.axis.wsdl.Java2WSDL with flags turned on for RPC and LITERAL. The only method in my SEI looks like:
    public String[] doIt(Customer i) throws RemoteException;

    DB:2.53:Rpc/Literal Generates Soap Encoded Array cs


    We recommend to use the Sun tool wscompile (like you would use javac) until we have our own tool set ready to be used with jboss.The Axis toolset does not generated J2EE compliant artifacts.

  • RELEVANCY SCORE 2.53

    DB:2.53:Abap: Consuming A Web Service: Cx_St_Group_Missing_Case:Xslt Exception.Element Missing j9



    Hi

    I am trying to consume a WebService. I loaded the WSDL from a file. With "validwsdl.com" I can access the WebService and the answer can be recognized, but with my generated ABAP-Proxy Object I always get the following error:

    CX_ST_GROUP_MISSING_CASE:XSLT exception in offset 231 and XPath SOAP-ENV:Envelope(1)SOAP-ENV:Body(1)ns1:sayHelloResponse(1).Element '{http://www.clxpreview.ch/index/soap}return' missing

    In the response from the WebService the element 'return' is not missing. The Response looks like this:

    ?xml version='1.0' encoding='UTF-8'?

    SOAP-ENV:Envelope xmlns:SOAP-ENV='http://schemas.xmlsoap.org/soap/envelope/' xmlns:ns1='http://www.any_server.com/index/soap'

    SOAP-ENV:Body

    ns1:sayHelloResponse

    return

    Say Hello Test

    /return

    /ns1:sayHelloResponse

    /SOAP-ENV:Body

    /SOAP-ENV:Envelope

    From the WSDL:

    ?xml version="1.0"?

    definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:tns="http://www.clxpreview.ch/index/soap" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap-enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" name="Service_Soap" targetNamespace="http://www.clxpreview.ch/index/soap"

    types

    xsd:schema targetNamespace="http://www.clxpreview.ch/index/soap"

    xsd:complexType name="User"

    xsd:all

    xsd:element name="username" type="xsd:string" nillable="true"/

    xsd:element name="password" type="xsd:string" nillable="true"/

    /xsd:all

    /xsd:complexType

    /xsd:schema

    /types

    message name="sayHelloIn"

    part name="who" type="xsd:string"/

    /message

    message name="sayHelloOut"

    part name="return" type="xsd:string"/

    /message

    portType name="Service_SoapPort"

    operation name="sayHello"

    documentationsayHello/documentation

    input message="tns:sayHelloIn"/

    output message="tns:sayHelloOut"/

    /operation

    /portType

    binding name="Service_SoapBinding" type="tns:Service_SoapPort"

    soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/

    operation name="sayHello"

    soap:operation soapAction="http://www.any_server.com/index/soap#sayHello"/

    input

    soap:body use="literal" namespace="http://clxpreview.ch/index/soap"/

    /input

    output

    soap:body use="literal" namespace="http://clxpreview.ch/index/soap"/

    /output

    /operation

    /binding

    service name="Service_SoapService"

    port name="Service_SoapPort" binding="tns:Service_SoapBinding"

    soap:address location="http://www.any_server.com/index/soap"/

    /port

    /service

    /definitions

    The coding is:

    gs_request-who = 'Test'.CALL METHOD go_clientproxy-say_hello EXPORTING input = gs_request IMPORTING output = gs_response.

    SAP_BASIS is:701

    Can anyone give me a hint how to solve these problems?

    Regards,

    Frowin

    DB:2.53:Abap: Consuming A Web Service: Cx_St_Group_Missing_Case:Xslt Exception.Element Missing j9


    Hi, do you manage to solve this?

    I encountered the same error when trying to consume a webservice from external system.

    Error message:

    SOAP:1,001 CX_ST_GROUP_MISSING_CASE:.Element 'sys_id' missing

  • RELEVANCY SCORE 2.53

    DB:2.53:Why Wsdl.Exe Gives Error When Accessing Soap Rpc/Literal Style Webservice k3


    i need to access a soapwebservice using RPC/literal instead of Document/literal type encoding in .net.
    But .net wsdl.exe only supports document/literal formats for soap webservices, what is the workaround with this, so i can get the procedures described in the soap wsdl in .net.
    thanks
    waqar

    DB:2.53:Why Wsdl.Exe Gives Error When Accessing Soap Rpc/Literal Style Webservice k3

    Why are you using WSDL.EXE? Are you stuck using .NET 2.0?
    Try using Add Service Reference or SVCUTIL.EXE and see if that works. A bug in WSDL.EXE will never be fixed. Bugs in SVCUTIL.EXE are much more likely to be fixed.John Saunders
    WCF is Web Services. They are not two separate things.
    Use WCF for All New Web Service Development, instead of legacy ASMX or obsolete WSE
    Use File-New Project to create Web Service Projects

  • RELEVANCY SCORE 2.52

    DB:2.52:How Do You Embed A Variable In An Xml Literal a1


    Is there a way to add a variable name in the middle on an XML element?

    I am constructing an XML document wrapped in a SOAP envelope. The SOAP envelope has processing instructions, in particular, create, correct, and update contained as part of their namespace. It looks like this:

    SOAPSaveDoc =
    SOAP-ENV:Envelope xmlns:SOAP-ENV=http://schemas.xmlsoap.org/soap/envelope/ xmlns:SOAP-ENC=http://schemas.xmlsoap.org/soap/encoding/ xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance xmlns:xsd=http://www.w3.org/2001/XMLSchema
    xmlns:ns1=http://www.MyPlace.com/DATA
    SOAP-ENV:Body
    m:create xmlns:m=urn:MyPlace.Business.Data.Entry SOAP-ENV:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/
    Body of XML document /
    /m:create
    /SOAP-ENV:Body
    /SOAP-ENV:Envelope

    I have three radio buttons on the form for each type, so based on the RadioButton selection the directive would be either:

    m:create xmlns:m=urn:MyPlace.Business.Data.Entry
    m:correct xmlns:m=urn:MyPlace.Business.Data.Entry
    m:update xmlns:m=urn:MyPlace.Business.Data.Entry

    However, because it is in the middle of an XML literal, I can't figure out how to get the processing instruction to be a variable. I tried %= instruction =% but that only works between element tags, not in the middle of one.

    How can I embed a variable in the middle of an XML literal? If that's not possible, can I create the document with a default value, and then use the xElement.ReplaceNodes method or some other method to alter it after the fact?
    ---Mike

    DB:2.52:How Do You Embed A Variable In An Xml Literal a1

    Well, here's an interesting one. If I don't declare the m namespace using an imports statement, I get the error:
    XML namespace prefix 'm' is not defined.
    If I do declare it using an imports statement, I get the error:
    'm' is an XML prefix and cannot be used as an expression. Use the GetXmlNamespace operator to create a namespace object.
    However, if I combine your suggestion with the error message and change it to:
    %= GetXmlNamespace(m) actionType % xmlns:m=urn:MyPlace.Business.Data.Entry SOAP-ENV:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/
    it works fine.
    I do apologize, I missed that you made a declaration for the XnameSpace at the beginning of your example. I also noted in my previous attempt before even asking this question, that I had a space between the % and the = and that produces as error so my original
    did not work.
    So, yes, your reply worked, I simply did not accuratley replicate your response.
    Thanks,

    ---Mike

    ---Mike

  • RELEVANCY SCORE 2.52

    DB:2.52:Namespace Disappears When Invoke Is Called k7


    I am sending the following SOAP message (I've abbreviated it ...):

    soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:open="http://www.openuri.org/" xmlns:pet="http://gencat.net/scsp/esquemes/peticion"
    soapenv:Header/
    soapenv:Body
    ...
    pet:Documents
    pet:Document
    pet:Hash xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:nil="true"/
    pet:AlgHash xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:nil="true"/
    /pet:Document
    /pet:Documents
    ...

    I send the SOAP message like this:

    public void send (Document xml)
    {
    Node nReq = xml.importNode(req, true);
    xml.getDocumentElement().appendChild(nReq);
    SOAPEnvelope requestEnvelope = new SOAPEnvelope();
    SOAPBodyElement requestBodyElement =
    new SOAPBodyElement(xml.getDocumentElement());

    requestEnvelope.addBodyElement(requestBodyElement);
    Service service = (!signar) ? new Service() : new Service(getWssd());
    Call call = (Call) service.createCall();
    }With Tcpmon I take a look at the actual message that is sent and Axis seems to automagically remove the 'xsi' namespace from both the 'pet:Hash' and 'pet:AlgHash' elements and adds it to the soapenv:Envelope element:

    soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance".

    I don't know why it's doing this (it's also adding the 'xsd' namespace) nor do I understand why the client I am sending it to can't process it, since it seems to be the same info, just sent in a different place. But they say they can't process it.

    So I was wondering if there is a way to tell Axis NOT to change my namespaces around. I've been poking around the api and I don't see anything obvious.

    Little help?

    Thanks,
    Bob

    DB:2.52:Namespace Disappears When Invoke Is Called k7

    I am sending the following SOAP message (I've abbreviated it ...):

    soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:open="http://www.openuri.org/" xmlns:pet="http://gencat.net/scsp/esquemes/peticion"
    soapenv:Header/
    soapenv:Body
    ...
    pet:Documents
    pet:Document
    pet:Hash xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:nil="true"/
    pet:AlgHash xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:nil="true"/
    /pet:Document
    /pet:Documents
    ...

    I send the SOAP message like this:

    public void send (Document xml)
    {
    Node nReq = xml.importNode(req, true);
    xml.getDocumentElement().appendChild(nReq);
    SOAPEnvelope requestEnvelope = new SOAPEnvelope();
    SOAPBodyElement requestBodyElement =
    new SOAPBodyElement(xml.getDocumentElement());

    requestEnvelope.addBodyElement(requestBodyElement);
    Service service = (!signar) ? new Service() : new Service(getWssd());
    Call call = (Call) service.createCall();
    }With Tcpmon I take a look at the actual message that is sent and Axis seems to automagically remove the 'xsi' namespace from both the 'pet:Hash' and 'pet:AlgHash' elements and adds it to the soapenv:Envelope element:

    soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance".

    I don't know why it's doing this (it's also adding the 'xsd' namespace) nor do I understand why the client I am sending it to can't process it, since it seems to be the same info, just sent in a different place. But they say they can't process it.

    So I was wondering if there is a way to tell Axis NOT to change my namespaces around. I've been poking around the api and I don't see anything obvious.

    Little help?

    Thanks,
    Bob

  • RELEVANCY SCORE 2.52

    DB:2.52:Exception While Invoking Web Service kc


    Hi ,

    I m writing a client to invoke a web service

    i m getting following exception -

    org.apache.wsif.WSIFException: duplicated extensibility element java.lang.Class in BindingInput: name=null
    SOAPHeader ({http://schemas.xmlsoap.org/wsdl/soap/}header):
    required=null
    message={http://xmlns.oracle.com/RapidDistributors}WSAReplyToHeader
    part=ReplyTo
    use=literal
    encodingStyles=[]
    soapHeaderFaults=[]
    SOAPHeader ({http://schemas.xmlsoap.org/wsdl/soap/}header):
    required=null
    message={http://xmlns.oracle.com/RapidDistributors}WSAMessageIDHeader
    part=MessageID
    use=literal
    encodingStyles=[]
    soapHeaderFaults=[]
    SOAPBody ({http://schemas.xmlsoap.org/wsdl/soap/}body):
    required=null
    use=literal
    at org.apache.wsif.base.WSIFDefaultPort.getExtElem(Unknown Source)
    at org.apache.wsif.providers.soap.apacheaxis.WSIFPort_ApacheAxis.getExtElem(Unknown Source)
    at org.apache.wsif.providers.soap.apacheaxis.WSIFOperation_ApacheAxis.parseSOAPHeaderElement(Unknown Source)
    at org.apache.wsif.providers.soap.apacheaxis.WSIFOperation_ApacheAxis.parseBindingInput(Unknown Source)
    at org.apache.wsif.providers.soap.apacheaxis.WSIFOperation_ApacheAxis.prepare(Unknown Source)
    at org.apache.wsif.providers.soap.apacheaxis.WSIFOperation_ApacheAxis.invokeRequestResponseOperation(Unknown Source)
    at org.apache.wsif.providers.soap.apacheaxis.WSIFOperation_ApacheAxis.executeRequestResponseOperation(Unknown Source)
    at test.RapidDistributros.main(RapidDistributros.java:146)
    Process exited with exit code 0.

    Any idea why this is happening ????????

    Thanks !

    DB:2.52:Exception While Invoking Web Service kc

    Hi ,

    I m writing a client to invoke a web service

    i m getting following exception -

    org.apache.wsif.WSIFException: duplicated extensibility element java.lang.Class in BindingInput: name=null
    SOAPHeader ({http://schemas.xmlsoap.org/wsdl/soap/}header):
    required=null
    message={http://xmlns.oracle.com/RapidDistributors}WSAReplyToHeader
    part=ReplyTo
    use=literal
    encodingStyles=[]
    soapHeaderFaults=[]
    SOAPHeader ({http://schemas.xmlsoap.org/wsdl/soap/}header):
    required=null
    message={http://xmlns.oracle.com/RapidDistributors}WSAMessageIDHeader
    part=MessageID
    use=literal
    encodingStyles=[]
    soapHeaderFaults=[]
    SOAPBody ({http://schemas.xmlsoap.org/wsdl/soap/}body):
    required=null
    use=literal
    at org.apache.wsif.base.WSIFDefaultPort.getExtElem(Unknown Source)
    at org.apache.wsif.providers.soap.apacheaxis.WSIFPort_ApacheAxis.getExtElem(Unknown Source)
    at org.apache.wsif.providers.soap.apacheaxis.WSIFOperation_ApacheAxis.parseSOAPHeaderElement(Unknown Source)
    at org.apache.wsif.providers.soap.apacheaxis.WSIFOperation_ApacheAxis.parseBindingInput(Unknown Source)
    at org.apache.wsif.providers.soap.apacheaxis.WSIFOperation_ApacheAxis.prepare(Unknown Source)
    at org.apache.wsif.providers.soap.apacheaxis.WSIFOperation_ApacheAxis.invokeRequestResponseOperation(Unknown Source)
    at org.apache.wsif.providers.soap.apacheaxis.WSIFOperation_ApacheAxis.executeRequestResponseOperation(Unknown Source)
    at test.RapidDistributros.main(RapidDistributros.java:146)
    Process exited with exit code 0.

    Any idea why this is happening ????????

    Thanks !

  • RELEVANCY SCORE 2.52

    DB:2.52:Problem With Dii Client For Doc/Literal With Non Built-In Type In Wl8.1 Sp2 m9


    Hello,

    I have been trying to make this DII client for doc/literal using non built-in type to work for 2 days now.

    Any help/input will be greatly appreciated. I have added the code and wsdl below.

    BTW this is using the code first approach.

    Works perfectly fine with the clientgen generated stubs. But not with DII.

    With the stubs, following is the SOAP envelope.

    env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    env:Header/
    env:Body
    n1:getType xmlns:n1="http://www.aeb.com/wlws"
    n2:id xmlns:n2="java:com.aeb.types"XYS/n2:id
    n3:name xmlns:n3="java:com.aeb.types"Name/n3:name
    /n1:getType
    /env:Body
    /env:Envelope

    With DII (using the serializer/deserializer generated by clientgen),

    env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    env:Header/
    env:Body
    n1:TestType xmlns:n1="java:com.aeb.types"
    n1:idABC/n1:id
    n1:nameSome Name/n1:name
    /n1:TestType
    /env:Body/env:Envelope

    Exception
    ---------

    javax.xml.rpc.soap.SOAPFaultException: Unable to find a matching Operation for this remote invocation
    n1:TestType xmlns:n1="java:com.aeb.types"
    n1:idABC/n1:id
    n1:nameSome Name/n1:name
    /n1:TestType.
    Please check your operation name.
    at weblogic.webservice.core.ClientDispatcher.receive(ClientDispatcher.java:313)
    at weblogic.webservice.core.ClientDispatcher.dispatch(ClientDispatcher.java:144)
    at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:457)
    at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:443)
    at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:558)
    at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:411)
    at com.amgen.webservice.clients.DocClient.callService(DocClient.java:83)
    at com.amgen.webservice.clients.DocClient.main(DocClient.java:35)

    Client
    ------
    System.setProperty("javax.xml.rpc.ServiceFactory","weblogic.webservice.core.rpc.ServiceFactoryImpl");
    System.setProperty("weblogic.webservice.verbose", "true");

    String targetNamespace = "http://www.aeb.com/wlws";
    ServiceFactory factory = ServiceFactory.newInstance();
    QName serviceName = new QName(targetNamespace, "DocWebservice");
    QName portName = new QName(targetNamespace, "DocWebservicePort");
    QName operationName = new QName(targetNamespace, "getType");

    Service service = factory.createService(serviceName);
    TypeMappingRegistry registry = service.getTypeMappingRegistry();
    TypeMapping mapping = registry.getTypeMapping(SOAPConstants.URI_NS_SOAP_ENCODING);
    mapping.register(TestType.class, new QName("java:com.aeb.types","TestType"), new TestTypeCodec(), new TestTypeCodec());

    Call call = service.createCall();
    call.setOperationName(operationName);
    call.setPortTypeName(portName);
    call.setProperty(Call.SOAPACTION_USE_PROPERTY, new Boolean(true));
    call.setProperty(Call.SOAPACTION_URI_PROPERTY, "");
    call.setProperty(Call.OPERATION_STYLE_PROPERTY, "document");

    call.addParameter("testType", new QName("java:com.aeb.types","TestType"), TestType.class, ParameterMode.IN);
    call.setReturnType(new QName("java:com.aeb.types", "TestType"),TestType.class);
    call.setTargetEndpointAddress("http://localhost:7001/wlws/DocWebservice");

    TestType type = new TestType();
    type.setId("ABC");
    type.setName("Some Name");
    TestType res = (TestType) call.invoke(new Object[] { type });
    System.out.println(res.getName());

    TestType.java
    -------------
    package com.aeb.types;
    import java.io.Serializable;
    public class TestType implements Serializable {
    private String id;
    private String name;
    public String getId() {
    return id;
    }
    public void setId(String id) {
    this.id = id;
    }
    public String getName() {
    return name;
    }
    public void setName(String name) {
    this.name = name;
    }
    }

    DocWebservice.java
    ------------------

    package com.aeb.webservices;
    import com.aeb.types.TestType;
    public class DocWebservice {
    public TestType getType(TestType type) {
    System.out.println("In Server....");
    System.out.println("Received : " + type.getName());
    return type;
    }
    }

    ServiceGen Ant Task
    -------------------

    servicegen destear="${dist.dir}/wlws.ear" contexturi="wlws"
    service javaClassComponents="com.aeb.webservices.DocWebservice"
    generateTypes="True"
    targetNamespace="http://www.aeb.com/wlws"
    serviceName="DocWebservice"
    serviceURI="/DocWebservice"
    style="document"
    client packageName="com.aeb.ws.doc.client" /
    /service
    /servicegen

    WSDL
    ----

    ?xml version="1.0" encoding="UTF-8"?
    definitions xmlns:tns="http://www.aeb.com/wlws" xmlns:wsr="http://www.openuri.org/2002/10/soap/reliability/"
    xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
    xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
    xmlns:soap12enc="http://www.w3.org/2003/05/soap-encoding" xmlns:conv="http://www.openuri.org/2002/04/wsdl/conversation/"
    xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:s="http://www.w3.org/2001/XMLSchema"
    xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://www.aeb.com/wlws"
    types xmlns:tns="http://www.aeb.com/wlws"
    xmlns:wsr="http://www.openuri.org/2002/10/soap/reliability/"
    xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
    xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
    xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
    xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
    xmlns:soap12enc="http://www.w3.org/2003/05/soap-encoding"
    xmlns:conv="http://www.openuri.org/2002/04/wsdl/conversation/"
    xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
    xmlns:s="http://www.w3.org/2001/XMLSchema"
    xmlns="http://schemas.xmlsoap.org/wsdl/"
    xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:stns="http://www.aeb.com/wlws"
    xmlns:tp="java:com.aeb.types"
    elementFormDefault="qualified"
    attributeFormDefault="qualified"
    targetNamespace="http://www.aeb.com/wlws"
    xsd:import namespace="java:com.aeb.types"
    /xsd:import
    xsd:element xmlns:tp="java:com.aeb.types"
    type="tp:TestType"
    name="getType"
    nillable="true"
    /xsd:element
    xsd:element xmlns:tp="java:com.aeb.types"
    type="tp:TestType"
    name="getTypeResponse"
    nillable="true"
    /xsd:element
    /xsd:schema
    xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:stns="java:com.aeb.types"
    elementFormDefault="qualified"
    attributeFormDefault="qualified"
    targetNamespace="java:com.aeb.types"
    xsd:complexType name="TestType"
    xsd:sequence
    xsd:element type="xsd:string"
    name="id"
    minOccurs="1"
    maxOccurs="1"
    nillable="true"
    /xsd:element
    xsd:element type="xsd:string"
    name="name"
    minOccurs="1"
    maxOccurs="1"
    nillable="true"
    /xsd:element
    /xsd:sequence
    /xsd:complexType
    /xsd:schema
    /types
    message name="getType"
    part xmlns:partns="http://www.aeb.com/wlws"
    name="testType"
    element="partns:getType"
    /part
    /message
    message name="getTypeResponse"
    part xmlns:partns="http://www.aeb.com/wlws"
    name="result"
    element="partns:getTypeResponse"
    /part
    /message
    portType name="DocWebservicePort"
    operation name="getType"
    input message="tns:getType"
    /input
    output message="tns:getTypeResponse"
    /output
    /operation
    /portType
    binding type="tns:DocWebservicePort"
    name="DocWebservicePort"
    soap:binding style="document"
    transport="http://schemas.xmlsoap.org/soap/http"
    /soap:binding
    operation name="getType"
    soap:operation style="document"
    soapAction=""
    /soap:operation
    wsr:reliability persistDuration="60000"
    /wsr:reliability
    input
    soap:body namespace="http://www.aeb.com/wlws"
    use="literal"
    /soap:body
    /input
    output
    soap:body namespace="http://www.aeb.com/wlws"
    use="literal"
    /soap:body
    /output
    /operation
    /binding
    service name="DocWebservice"
    port name="DocWebservicePort"
    binding="tns:DocWebservicePort"
    soap:address location="http://localhost:7001/wlws/DocWebservice"
    /soap:address
    /port
    /service
    /definitions

    Thanks

    Aspert

    DB:2.52:Problem With Dii Client For Doc/Literal With Non Built-In Type In Wl8.1 Sp2 m9

    Hello,

    I have been trying to make this DII client for doc/literal using non built-in type to work for 2 days now.

    Any help/input will be greatly appreciated. I have added the code and wsdl below.

    BTW this is using the code first approach.

    Works perfectly fine with the clientgen generated stubs. But not with DII.

    With the stubs, following is the SOAP envelope.

    env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    env:Header/
    env:Body
    n1:getType xmlns:n1="http://www.aeb.com/wlws"
    n2:id xmlns:n2="java:com.aeb.types"XYS/n2:id
    n3:name xmlns:n3="java:com.aeb.types"Name/n3:name
    /n1:getType
    /env:Body
    /env:Envelope

    With DII (using the serializer/deserializer generated by clientgen),

    env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    env:Header/
    env:Body
    n1:TestType xmlns:n1="java:com.aeb.types"
    n1:idABC/n1:id
    n1:nameSome Name/n1:name
    /n1:TestType
    /env:Body/env:Envelope

    Exception
    ---------

    javax.xml.rpc.soap.SOAPFaultException: Unable to find a matching Operation for this remote invocation
    n1:TestType xmlns:n1="java:com.aeb.types"
    n1:idABC/n1:id
    n1:nameSome Name/n1:name
    /n1:TestType.
    Please check your operation name.
    at weblogic.webservice.core.ClientDispatcher.receive(ClientDispatcher.java:313)
    at weblogic.webservice.core.ClientDispatcher.dispatch(ClientDispatcher.java:144)
    at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:457)
    at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:443)
    at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:558)
    at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:411)
    at com.amgen.webservice.clients.DocClient.callService(DocClient.java:83)
    at com.amgen.webservice.clients.DocClient.main(DocClient.java:35)

    Client
    ------
    System.setProperty("javax.xml.rpc.ServiceFactory","weblogic.webservice.core.rpc.ServiceFactoryImpl");
    System.setProperty("weblogic.webservice.verbose", "true");

    String targetNamespace = "http://www.aeb.com/wlws";
    ServiceFactory factory = ServiceFactory.newInstance();
    QName serviceName = new QName(targetNamespace, "DocWebservice");
    QName portName = new QName(targetNamespace, "DocWebservicePort");
    QName operationName = new QName(targetNamespace, "getType");

    Service service = factory.createService(serviceName);
    TypeMappingRegistry registry = service.getTypeMappingRegistry();
    TypeMapping mapping = registry.getTypeMapping(SOAPConstants.URI_NS_SOAP_ENCODING);
    mapping.register(TestType.class, new QName("java:com.aeb.types","TestType"), new TestTypeCodec(), new TestTypeCodec());

    Call call = service.createCall();
    call.setOperationName(operationName);
    call.setPortTypeName(portName);
    call.setProperty(Call.SOAPACTION_USE_PROPERTY, new Boolean(true));
    call.setProperty(Call.SOAPACTION_URI_PROPERTY, "");
    call.setProperty(Call.OPERATION_STYLE_PROPERTY, "document");

    call.addParameter("testType", new QName("java:com.aeb.types","TestType"), TestType.class, ParameterMode.IN);
    call.setReturnType(new QName("java:com.aeb.types", "TestType"),TestType.class);
    call.setTargetEndpointAddress("http://localhost:7001/wlws/DocWebservice");

    TestType type = new TestType();
    type.setId("ABC");
    type.setName("Some Name");
    TestType res = (TestType) call.invoke(new Object[] { type });
    System.out.println(res.getName());

    TestType.java
    -------------
    package com.aeb.types;
    import java.io.Serializable;
    public class TestType implements Serializable {
    private String id;
    private String name;
    public String getId() {
    return id;
    }
    public void setId(String id) {
    this.id = id;
    }
    public String getName() {
    return name;
    }
    public void setName(String name) {
    this.name = name;
    }
    }

    DocWebservice.java
    ------------------

    package com.aeb.webservices;
    import com.aeb.types.TestType;
    public class DocWebservice {
    public TestType getType(TestType type) {
    System.out.println("In Server....");
    System.out.println("Received : " + type.getName());
    return type;
    }
    }

    ServiceGen Ant Task
    -------------------

    servicegen destear="${dist.dir}/wlws.ear" contexturi="wlws"
    service javaClassComponents="com.aeb.webservices.DocWebservice"
    generateTypes="True"
    targetNamespace="http://www.aeb.com/wlws"
    serviceName="DocWebservice"
    serviceURI="/DocWebservice"
    style="document"
    client packageName="com.aeb.ws.doc.client" /
    /service
    /servicegen

    WSDL
    ----

    ?xml version="1.0" encoding="UTF-8"?
    definitions xmlns:tns="http://www.aeb.com/wlws" xmlns:wsr="http://www.openuri.org/2002/10/soap/reliability/"
    xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
    xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
    xmlns:soap12enc="http://www.w3.org/2003/05/soap-encoding" xmlns:conv="http://www.openuri.org/2002/04/wsdl/conversation/"
    xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:s="http://www.w3.org/2001/XMLSchema"
    xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://www.aeb.com/wlws"
    types xmlns:tns="http://www.aeb.com/wlws"
    xmlns:wsr="http://www.openuri.org/2002/10/soap/reliability/"
    xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
    xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
    xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
    xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
    xmlns:soap12enc="http://www.w3.org/2003/05/soap-encoding"
    xmlns:conv="http://www.openuri.org/2002/04/wsdl/conversation/"
    xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
    xmlns:s="http://www.w3.org/2001/XMLSchema"
    xmlns="http://schemas.xmlsoap.org/wsdl/"
    xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:stns="http://www.aeb.com/wlws"
    xmlns:tp="java:com.aeb.types"
    elementFormDefault="qualified"
    attributeFormDefault="qualified"
    targetNamespace="http://www.aeb.com/wlws"
    xsd:import namespace="java:com.aeb.types"
    /xsd:import
    xsd:element xmlns:tp="java:com.aeb.types"
    type="tp:TestType"
    name="getType"
    nillable="true"
    /xsd:element
    xsd:element xmlns:tp="java:com.aeb.types"
    type="tp:TestType"
    name="getTypeResponse"
    nillable="true"
    /xsd:element
    /xsd:schema
    xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:stns="java:com.aeb.types"
    elementFormDefault="qualified"
    attributeFormDefault="qualified"
    targetNamespace="java:com.aeb.types"
    xsd:complexType name="TestType"
    xsd:sequence
    xsd:element type="xsd:string"
    name="id"
    minOccurs="1"
    maxOccurs="1"
    nillable="true"
    /xsd:element
    xsd:element type="xsd:string"
    name="name"
    minOccurs="1"
    maxOccurs="1"
    nillable="true"
    /xsd:element
    /xsd:sequence
    /xsd:complexType
    /xsd:schema
    /types
    message name="getType"
    part xmlns:partns="http://www.aeb.com/wlws"
    name="testType"
    element="partns:getType"
    /part
    /message
    message name="getTypeResponse"
    part xmlns:partns="http://www.aeb.com/wlws"
    name="result"
    element="partns:getTypeResponse"
    /part
    /message
    portType name="DocWebservicePort"
    operation name="getType"
    input message="tns:getType"
    /input
    output message="tns:getTypeResponse"
    /output
    /operation
    /portType
    binding type="tns:DocWebservicePort"
    name="DocWebservicePort"
    soap:binding style="document"
    transport="http://schemas.xmlsoap.org/soap/http"
    /soap:binding
    operation name="getType"
    soap:operation style="document"
    soapAction=""
    /soap:operation
    wsr:reliability persistDuration="60000"
    /wsr:reliability
    input
    soap:body namespace="http://www.aeb.com/wlws"
    use="literal"
    /soap:body
    /input
    output
    soap:body namespace="http://www.aeb.com/wlws"
    use="literal"
    /soap:body
    /output
    /operation
    /binding
    service name="DocWebservice"
    port name="DocWebservicePort"
    binding="tns:DocWebservicePort"
    soap:address location="http://localhost:7001/wlws/DocWebservice"
    /soap:address
    /port
    /service
    /definitions

    Thanks

    Aspert

  • RELEVANCY SCORE 2.51

    DB:2.51:Document/Literal Dii Client Does Not Work 1p



    Hi,I'm getting an error when running DII client for a document/literal webservice. It can not determine the parameter type. Static client works.Any help would be greatly appreciated.Luan [java] the serializer/deserializer for parameter number: 0,named: "{http://www.w3.org/2001/XMLSchema}string", type: "{http://www.w3.org/2001/XMLSchema}string", is ambiguous because its class could not be determinedThe DII client code is as follows:import java.net.*;import javax.xml.rpc.*;import javax.xml.namespace.*;public class WSDIIClient { private static String qnameService = "MgiParser"; private static String qnamePort = "MgiParserInterfacePort"; private static String endpoint_url = "http://localhost:8080/MgiParserServerJBoss/myParserService"; private static String wsdl_url = "http://localhost:8080/MgiParserServerJBoss/myParserService?wsdl"; private static String target_namespace = "http://com.mgiparser/MgiParser"; private static String NS_XSD = "http://www.w3.org/2001/XMLSchema"; private static String part_name = "parameters"; private static String operation_name = "getParsingResult"; public static void main(String[] args) { try { ServiceFactory factory = ServiceFactory.newInstance(); Service service = factory.createService(new URL(wsdl_url), new QName(target_namespace, qnameService)); QName port = new QName(target_namespace, qnamePort); Call call = service.createCall(port); call.setTargetEndpointAddress(endpoint_url); call.setProperty(Call.SOAPACTION_USE_PROPERTY, new Boolean(true)); call.setProperty(Call.SOAPACTION_URI_PROPERTY, "http://com.mgiparser/MgiParser/getParsingResult"); call.setProperty(Call.ENCODINGSTYLE_URI_PROPERTY, "");call.setProperty(Call.OPERATION_STYLE_PROPERTY, "document"); QName QNAME_TYPE_STRING = new QName(NS_XSD, "string"); call.setReturnType(QNAME_TYPE_STRING); call.setOperationName( new QName(target_namespace, operation_name)); call.addParameter(part_name, QNAME_TYPE_STRING, ParameterMode.IN); Object[] params = new Object[] { "test string1","test string2" }; String result = (String)call.invoke(params); System.out.println(result); } catch (Exception ex) { ex.printStackTrace(); } }}

    DB:2.51:Document/Literal Dii Client Does Not Work 1p


    Hi,I'm getting an error when running DII client for a document/literal webservice. It can not determine the parameter type. Static client works.Any help would be greatly appreciated.Luan [java] the serializer/deserializer for parameter number: 0,named: "{http://www.w3.org/2001/XMLSchema}string", type: "{http://www.w3.org/2001/XMLSchema}string", is ambiguous because its class could not be determinedThe DII client code is as follows:import java.net.*;import javax.xml.rpc.*;import javax.xml.namespace.*;public class WSDIIClient { private static String qnameService = "MgiParser"; private static String qnamePort = "MgiParserInterfacePort"; private static String endpoint_url = "http://localhost:8080/MgiParserServerJBoss/myParserService"; private static String wsdl_url = "http://localhost:8080/MgiParserServerJBoss/myParserService?wsdl"; private static String target_namespace = "http://com.mgiparser/MgiParser"; private static String NS_XSD = "http://www.w3.org/2001/XMLSchema"; private static String part_name = "parameters"; private static String operation_name = "getParsingResult"; public static void main(String[] args) { try { ServiceFactory factory = ServiceFactory.newInstance(); Service service = factory.createService(new URL(wsdl_url), new QName(target_namespace, qnameService)); QName port = new QName(target_namespace, qnamePort); Call call = service.createCall(port); call.setTargetEndpointAddress(endpoint_url); call.setProperty(Call.SOAPACTION_USE_PROPERTY, new Boolean(true)); call.setProperty(Call.SOAPACTION_URI_PROPERTY, "http://com.mgiparser/MgiParser/getParsingResult"); call.setProperty(Call.ENCODINGSTYLE_URI_PROPERTY, "");call.setProperty(Call.OPERATION_STYLE_PROPERTY, "document"); QName QNAME_TYPE_STRING = new QName(NS_XSD, "string"); call.setReturnType(QNAME_TYPE_STRING); call.setOperationName( new QName(target_namespace, operation_name)); call.addParameter(part_name, QNAME_TYPE_STRING, ParameterMode.IN); Object[] params = new Object[] { "test string1","test string2" }; String result = (String)call.invoke(params); System.out.println(result); } catch (Exception ex) { ex.printStackTrace(); } }}

  • RELEVANCY SCORE 2.51

    DB:2.51:Caught Exception While Handling Request: Expected Element Is Missing ka


    Hi,

    very simple case...

    I have a Webservice developed with Jdev 10.1.3.3 (J2EE 1.4 JAX-RPC) using RPC/literal style, deployed on OC4J 10.1.3.3.
    The WS is based on a pl/sql function with 2 inputs parameters, p1 with a default value, p2 withtout and the function is returning a string.

    If i call the WS with all paramaters tags (p1 and p2) in the request, it works fine (CASE 1) but i want to call it with only the required parameters (p2). As p1 has a default value, i make the request without p1 tag and i get the following error: "Caught exception while handling request: expected element is missing: p1"

    More info below

    What's wrong? Is it possible to call the Ws when omitting non-mandatory input parameters?

    Thanks

    ####
    WSDL
    ####
    definitions
    name="MyWebService1"
    targetNamespace="http://tst/MyWebService1.wsdl"
    xmlns="http://schemas.xmlsoap.org/wsdl/"
    xmlns:tns="http://tst/MyWebService1.wsdl"
    xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
    xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"

    types
    /types
    message name="MyWebService1_pviGetInstanceName"
    part name="p1" type="xsd:string"/
    part name="p2" type="xsd:string"/
    /message
    message name="MyWebService1_pviGetInstanceNameResponse"
    part name="result" type="xsd:string"/
    /message
    portType name="MyWebService1"
    operation name="pviGetInstanceName" parameterOrder="p1 p2"
    input message="tns:MyWebService1_pviGetInstanceName"/
    output message="tns:MyWebService1_pviGetInstanceNameResponse"/
    /operation
    /portType
    binding name="MyWebService1SoapHttp" type="tns:MyWebService1"
    soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/
    operation name="pviGetInstanceName"
    soap:operation soapAction="http://tst/MyWebService1.wsdl/pviGetInstanceName"/
    input
    soap:body use="literal" namespace="http://tst/MyWebService1.wsdl" parts="p1 p2"/
    /input
    output
    soap:body use="literal" namespace="http://tst/MyWebService1.wsdl" parts="result"/
    /output
    /operation
    /binding
    service name="MyWebService1"
    port name="MyWebService1SoapHttpPort" binding="tns:MyWebService1SoapHttp"
    soap:address location="http://172.22.35.17:8888/Application13-Project1-context-root/MyWebService1SoapHttpPort"/
    /port
    /service
    /definitions
    ##############
    REQUEST CASE 1 (p1 tag present but empty, p2 filled)
    ##############
    soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="http://tst/MyWebService1.wsdl"
    soap:Body
    ns:pviGetInstanceName
    p1/p1
    p2YY/p2
    /ns:pviGetInstanceName
    /soap:Body
    /soap:Envelope
    ##############
    RESPONSE CASE 1 (ok)
    ##############
    env:Envelope
    xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:ns0="http://tst/MyWebService1.wsdl"
    env:Body
    ns0:pviGetInstanceNameResponse
    result#p1=#p2=YY#/result
    /ns0:pviGetInstanceNameResponse
    /env:Body
    /env:Envelope
    ##############
    REQUEST CASE 2 (p1 tag not passed)
    ##############
    soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="http://tst/MyWebService1.wsdl"
    soap:Body
    ns:pviGetInstanceName
    p2ZZ/p2
    /ns:pviGetInstanceName
    /soap:Body
    /soap:Envelope
    ##############
    RESPONSE CASE 2 (error)
    ##############
    env:Envelope
    xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:ns0="http://tst/MyWebService1.wsdl"
    env:Body
    env:Fault
    faultcodeenv:Client/faultcode
    faultstringCaught exception while handling request: expected element is missing: p1/faultstring
    /env:Fault
    /env:Body
    /env:Envelope
    ##############

    DB:2.51:Caught Exception While Handling Request: Expected Element Is Missing ka

    Hi,

    very simple case...

    I have a Webservice developed with Jdev 10.1.3.3 (J2EE 1.4 JAX-RPC) using RPC/literal style, deployed on OC4J 10.1.3.3.
    The WS is based on a pl/sql function with 2 inputs parameters, p1 with a default value, p2 withtout and the function is returning a string.

    If i call the WS with all paramaters tags (p1 and p2) in the request, it works fine (CASE 1) but i want to call it with only the required parameters (p2). As p1 has a default value, i make the request without p1 tag and i get the following error: "Caught exception while handling request: expected element is missing: p1"

    More info below

    What's wrong? Is it possible to call the Ws when omitting non-mandatory input parameters?

    Thanks

    ####
    WSDL
    ####
    definitions
    name="MyWebService1"
    targetNamespace="http://tst/MyWebService1.wsdl"
    xmlns="http://schemas.xmlsoap.org/wsdl/"
    xmlns:tns="http://tst/MyWebService1.wsdl"
    xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
    xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"

    types
    /types
    message name="MyWebService1_pviGetInstanceName"
    part name="p1" type="xsd:string"/
    part name="p2" type="xsd:string"/
    /message
    message name="MyWebService1_pviGetInstanceNameResponse"
    part name="result" type="xsd:string"/
    /message
    portType name="MyWebService1"
    operation name="pviGetInstanceName" parameterOrder="p1 p2"
    input message="tns:MyWebService1_pviGetInstanceName"/
    output message="tns:MyWebService1_pviGetInstanceNameResponse"/
    /operation
    /portType
    binding name="MyWebService1SoapHttp" type="tns:MyWebService1"
    soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/
    operation name="pviGetInstanceName"
    soap:operation soapAction="http://tst/MyWebService1.wsdl/pviGetInstanceName"/
    input
    soap:body use="literal" namespace="http://tst/MyWebService1.wsdl" parts="p1 p2"/
    /input
    output
    soap:body use="literal" namespace="http://tst/MyWebService1.wsdl" parts="result"/
    /output
    /operation
    /binding
    service name="MyWebService1"
    port name="MyWebService1SoapHttpPort" binding="tns:MyWebService1SoapHttp"
    soap:address location="http://172.22.35.17:8888/Application13-Project1-context-root/MyWebService1SoapHttpPort"/
    /port
    /service
    /definitions
    ##############
    REQUEST CASE 1 (p1 tag present but empty, p2 filled)
    ##############
    soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="http://tst/MyWebService1.wsdl"
    soap:Body
    ns:pviGetInstanceName
    p1/p1
    p2YY/p2
    /ns:pviGetInstanceName
    /soap:Body
    /soap:Envelope
    ##############
    RESPONSE CASE 1 (ok)
    ##############
    env:Envelope
    xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:ns0="http://tst/MyWebService1.wsdl"
    env:Body
    ns0:pviGetInstanceNameResponse
    result#p1=#p2=YY#/result
    /ns0:pviGetInstanceNameResponse
    /env:Body
    /env:Envelope
    ##############
    REQUEST CASE 2 (p1 tag not passed)
    ##############
    soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="http://tst/MyWebService1.wsdl"
    soap:Body
    ns:pviGetInstanceName
    p2ZZ/p2
    /ns:pviGetInstanceName
    /soap:Body
    /soap:Envelope
    ##############
    RESPONSE CASE 2 (error)
    ##############
    env:Envelope
    xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:ns0="http://tst/MyWebService1.wsdl"
    env:Body
    env:Fault
    faultcodeenv:Client/faultcode
    faultstringCaught exception while handling request: expected element is missing: p1/faultstring
    /env:Fault
    /env:Body
    /env:Envelope
    ##############

  • RELEVANCY SCORE 2.50

    DB:2.50:Jxrpc: Reading The Wsdl File zc


    Hi, this is probably a daft quetion so bare with me !

    Ive got a small jaxrpc DII client working which looks like this

    QName serviceName = new QName("http://www.xmethods.net/sd/CurrencyExchangeService.wsdl", "CurrencyExchangePort");
    ServiceFactory factory = ServiceFactory.newInstance();
    Service service = factory.createService(serviceName);

    Call call = service.createCall();
    QName operationName = new QName("urn:xmethods-CurrencyExchange","getRateRequest");
    call.setOperationName(operationName);
    call.addParameter("country1",XMLType.XSD_STRING,String.class,ParameterMode.IN);
    call.addParameter("country2",XMLType.XSD_STRING,String.class,ParameterMode.IN);

    call.setReturnType(XMLType.XSD_FLOAT);

    call.setProperty(Call.OPERATION_STYLE_PROPERTY,"rpc");
    Call.ENCODINGSTYLE_URI_PROPERTY,"http://schemas.xmlsoap.org/soap/encoding/");

    call.setTargetEndpointAddress("http://services.xmethods.net:80/soap");

    Object[] actualArgs ={"Spain","France"};
    Float rate = (Float) call.invoke(actualArgs);
    System.out.println("Rate = '"+rate+"'");

    .... which is fine and working ok.

    However, instead of having the input / output parameters hard coded in the client is it not possible to read the wsdl document and dynamically calculate what input / output parameters are required? and then prompt the user for them? (In the same way that quickTry by binding point works http://www.bindingpoint.com/quicktryv2.aspx )

    Hope someone can point me in the right direction. Many thanks

    DB:2.50:Jxrpc: Reading The Wsdl File zc

    David-
    I suspect that the namespace URI for the service and port are not correct- that is-

    Service service = factory.createService(new URL("http://www.xmethods.net/sd/2001/BNQuoteService.wsdl"), new QName("http://www.xmethods.net/sd/BNQuoteService.wsdl","BNQuoteService"));
    Call[] calls = service.getCalls(new QName("http://www.xmethods.net/sd/BNQuoteService.wsdl","BNQuotePort"));

    I haven't looked at the wsdl, but is the target namespace

    "http://www.xmethods.net/sd/BNQuoteService.wsdl"?

    I will look at the wsdl and get back to you shortly-
    Kathy

  • RELEVANCY SCORE 2.50

    DB:2.50:Dii Call c9



    I am using Call interface to invoke a operation. The operation is implemented in
    document-literal style. The server receives the request correctly and returns
    the response but the client side I receive null. The argment to this operation
    is String and the return vale also is String.

    DB:2.50:Dii Call c9

    I also have same problem . has anyone solution for it?

  • RELEVANCY SCORE 2.50

    DB:2.50:Shape Keys 1a


    Hi,I want to extract some of a model information over it's animation. I know I have to use shape keys for it. For now, I have this :XSI::CGeometryAccessor ga = mesh.GetGeometryAccessor#40; XSI::siConstructionModeModeling, XSI::siCatmullClark, 0 #41;XSI::CRefArray refShapeKeys = ga.GetShapeKeys#40;#41;LONG nShapeKeys = refShapeKeys.GetCount#40;#41;XSI::ShapeKey currentKey = refShapeKeys;XSI::ShapeKey frame0 = currentKey.EvaluateAt#40;0#41;XSI::CClusterPropertyElementArray frameElem = frame0.GetElements#40;#41;LONG frameElemValueSize = frameElem.GetValueSize#40;#41;LONG frameElemCount = frameElem.GetCount#40;#41;So, first of all, the EvaluateAt method... will it return me the something at a particular frame?Second of all, the frameElemValueSize gives me 78 right now and frameElemCount, 21670. How can I know what are the frame elements #40;vertices, polygons...#41; and each of the values for each element #40;UVs, position, color....#41;?? When I call EvaluateAt, information in this array will change too?Any help will be appreciated!Thanks!

    DB:2.50:Shape Keys 1a

    Well, I found my error. I need to call EvaluateAt on the primitive itself then, the GeometryAccessor is updated to the frame I want.

  • RELEVANCY SCORE 2.49

    DB:2.49:Jaxrpc Question x8


    Hi, this is probably a daft quetion so bare with me !

    Ive got a small jaxrpc DII client working which looks like this

    QName serviceName = new QName("http://www.xmethods.net/sd/CurrencyExchangeService.wsdl", "CurrencyExchangePort");
    ServiceFactory factory = ServiceFactory.newInstance();
    Service service = factory.createService(serviceName);

    Call call = service.createCall();
    QName operationName = new QName("urn:xmethods-CurrencyExchange","getRateRequest");
    call.setOperationName(operationName);
    call.addParameter("country1",XMLType.XSD_STRING,String.class,ParameterMode.IN);
    call.addParameter("country2",XMLType.XSD_STRING,String.class,ParameterMode.IN);

    call.setReturnType(XMLType.XSD_FLOAT);

    call.setProperty(Call.OPERATION_STYLE_PROPERTY,"rpc");
    Call.ENCODINGSTYLE_URI_PROPERTY,"http://schemas.xmlsoap.org/soap/encoding/");

    call.setTargetEndpointAddress("http://services.xmethods.net:80/soap");

    Object[] actualArgs ={"Spain","France"};
    Float rate = (Float) call.invoke(actualArgs);
    System.out.println("Rate = '"+rate+"'");

    .... which is fine and working ok.

    However, instead of having the input / output parameters hard coded in the client is it not possible to read the wsdl document and dynamically calculate what input / output parameters are required? and then prompt the user for them? (In the same way that quickTry by binding point works http://www.bindingpoint.com/quicktryv2.aspx )

    Hope someone can point me in the right direction. Many thanks

    DB:2.49:Jaxrpc Question x8

    In addition to Alan's comment, it is worth pointing out that WSI BP 1.0 does not provide support for DII so I would stay away from it. Plus in jaxrpc 2.0, i believe the plan is to give DII a major overhaul

  • RELEVANCY SCORE 2.49

    DB:2.49:Help Required To Call Wfa Rest Api From Bmc Atrium Orchestrator. 7k



    WFA Web services are supported using WSDL SOAP bindings with old version of WFA metioned in the TR 4254

    In the TR, the URL to calll SOAP API is mentioned as -

    Document/literal encoding, which is used most often by Java® applicationshttp://WFA_IP address/wfa-ws/WorkflowService_doc?wsdl RPC encoding, which is used most often by .Net, Visual C#, and Windows PowerShell™http://WFA_IP address/wfa-ws/WorkflowService_rpc?wsdl

    In my case I'm trying to call REST APIs from BMC Atrium Orchestrator from wfa 3.0

    I'd like to know how can I call REST APIs from BMC AO for WFA 3.0

    We are getting an error when I put the below URL in BMC AO Studio Manager

    http://WFA_IP address/rest/workflows

    RegardsPatil

  • RELEVANCY SCORE 2.49

    DB:2.49:Dii With Document Literal To .Net Returns Classcastexception: Xmlelement 9f


    I'm calling a void method in .Net land, using Dynamic Interface Invocation with WS-Security
    turned on. We can see the .Net side complete and send a response, however I get a error on
    the Java side;

    deserialization error: java.lang.ClassCastException: oracle.xml.parser.v2.XMLElement
    at oracle.j2ee.ws.common.encoding.literal.LiteralObjectSerializerBase.deserialize(LiteralObjectSerializerBase.java:165)
    at oracle.j2ee.ws.client.dii.CallInvokerImpl._readFirstBodyElement(CallInvokerImpl.java:533)
    at oracle.j2ee.ws.client.StreamingSender._sendImpl(StreamingSender.java:333)
    at oracle.j2ee.ws.client.StreamingSender._send(StreamingSender.java:112)
    at oracle.j2ee.ws.client.dii.CallInvokerImpl.directInvoke(CallInvokerImpl.java:711)
    at oracle.j2ee.ws.client.dii.BasicCall.directInvoke(BasicCall.java:739)
    at oracle.j2ee.ws.client.dii.BasicCall.invoke(BasicCall.java:645)

    The WSDL looks like;

    s:element name="Method1"
    s:complexType
    s:sequence
    s:element minOccurs="0" maxOccurs="1" name="p1" type="s:string"/
    s:element minOccurs="0" maxOccurs="1" name="p2" type="s:string"/
    s:element minOccurs="0" maxOccurs="1" name="p3" type="s:string"/
    s:element minOccurs="0" maxOccurs="1" name="p4" type="s:string"/
    s:element minOccurs="0" maxOccurs="1" name="p5" type="s:string"/
    /s:sequence
    /s:complexType
    /s:element
    s:element name="Method1Response"
    s:complexType/
    /s:element

    wsdl:operation name="Method1"
    soap:operation soapAction="http://a.b.c.d/adws/adsi/IADsUser/Method1" style="document"/
    wsdl:input
    soap:body use="literal"/
    /wsdl:input
    wsdl:output
    soap:body use="literal"/
    /wsdl:output
    /wsdl:operation

    In my code I set up the Call object and set a return type

    ServiceFactory factory = ServiceFactory.newInstance();
    Service service = factory.createService(wsdl, new QName(BODY_NAMESPACE_VALUE, qnameService));

    QName port = new QName(BODY_NAMESPACE_VALUE, qnamePort);

    QName opQ = new QName(BODY_NAMESPACE_VALUE, opName, "ns0");
    Call call = service.createCall(port);
    call.setTargetEndpointAddress(endpoint);

    call.setProperty(Call.SOAPACTION_USE_PROPERTY, Boolean.valueOf(true));
    call.setProperty(Call.SOAPACTION_URI_PROPERTY, BODY_NAMESPACE_VALUE + "/" + opName);

    QName responseType = new QName(BODY_NAMESPACE_VALUE, "Method1Response", "ns0");
    call.setReturnType(responseType);

    And set up the input parameters through the SOAPElement class

    SOAPFactory soapfactory = SOAPFactory.newInstance();
    SOAPElement m1 = soapfactory.createElement(opName, "ns0", BODY_NAMESPACE_VALUE);
    SOAPElement m2 = soapfactory.createElement(param, "ns0", BODY_NAMESPACE_VALUE);
    m2.addTextNode("param-value);
    m1.addChildElement(m2);

    and finally invoke the method

    OracleCall oCall = (OracleCall)call;
    oCall.invoke((Element)m1);

    It waits for the response and then the deserialisation error: comes, no matter what I try
    I always get this ClassCastException....

    Has anyone succeeded in using DII in this manner?

    Many thanks for any hints
    Scott.

    DB:2.49:Dii With Document Literal To .Net Returns Classcastexception: Xmlelement 9f

    Hi All,

    This Deserialization error is a bug filed on Component SECURITY Comp Ver: 10.1.3.2 due to bug 5968831. For Secured environment the SOAPMessage has XMLElement instead of SOAPElement. The ClassCastException is raised due to this.

    Regards,
    Lester.

  • RELEVANCY SCORE 2.48

    DB:2.48:Webservice Returns Correct Value But Flex Sees It As Null px



    Nice, I just realized that my original post only had the WSDL. Sorry about that. The underlying issue I am having is, the Flex Builder 3 Manage Web Services wizard consumes the wsdl just fine, creates all necessary classes and from there I can instantiate and call the webservice. Using Service Capture I see the SOAP response come back, I can debug in Flex Builder and step through the code and see the response was returned but it gets lost within the SOAPDecoder.as in the decodeBody() method.

    Unfortunately, I can not open up a port to allow anyone to try it out. The best I can do is post the SOAP request body and the SOAP response body along with the wsdl.

    SOAP Request Body:

    SOAP-ENV:Envelope xmlns="http://www.w3.org/2001/XMLSchema" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

    SOAP-ENV:Body

    intf:startSession xmlns:intf="http://company.com/HeliumWS"

    intf:usernameDEV/intf:username

    /intf:startSession

    /SOAP-ENV:Body

    /SOAP-ENV:Envelope

    SOAP Reponse Body:

    env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

    env:Body

    n1:startSessionResponse env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:n1="http://company.com/HeliumWS"

    return xmlns:n2="http://www.ruby-lang.org/xmlns/ruby/type/custom" xsi:type="n2:HeliumWS..StartSessionReturn"

    sessionID xsi:type="xsd:string"session7a86c52d/sessionID

    /return

    /n1:startSessionResponse

    /env:Body

    /env:Envelope

    WSDL:

    ?xml version="1.0" encoding="UTF-8"? wsdl:definitions targetNamespace="http://company.com/HeliumWS" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://company.com/HeliumWS" xmlns:intf="http://company.com/HeliumWS" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" wsdl:types schema elementFormDefault="qualified" targetNamespace="http://company.com/HeliumWS" xmlns="http://www.w3.org/2001/XMLSchema" element name="startSession" complexType sequence element name="username" nillable="true" type="xsd:string"/ /sequence /complexType /element element name="startSessionResponse" complexType sequence element name="returnValue" type="intf:startSessionReturn"/ /sequence /complexType /element complexType name="startSessionReturn" sequence element name="sessionID" type="xsd:string"/ /sequence /complexType /schema /wsdl:types wsdl:message name="startSessionRequest" wsdl:part element="impl:startSession" name="parameters"/ /wsdl:message wsdl:message name="startSessionResponse" wsdl:part element="impl:startSessionResponse" name="parameters"/ /wsdl:message wsdl:portType name="MCUBindingImpl" wsdl:operation name="startSession" wsdl:input message="impl:startSessionRequest" name="startSessionRequest"/ wsdl:output message="impl:startSessionResponse" name="startSessionResponse"/ /wsdl:operation /wsdl:portType wsdl:binding name="MCUBindingImplSoapBinding" type="impl:MCUBindingImpl" wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/ wsdl:operation name="startSession" wsdlsoap:operation soapAction=""/ wsdl:input name="startSessionRequest" wsdlsoap:body use="literal"/ /wsdl:input wsdl:output name="startSessionResponse" wsdlsoap:body use="literal"/ /wsdl:output /wsdl:operation /wsdl:binding wsdl:service name="MCUBindingImplService" wsdl:port binding="impl:MCUBindingImplSoapBinding" name="MCUBindingImpl" wsdlsoap:address location="http://10.10.20.82/soap"/ /wsdl:port /wsdl:service /wsdl:definitions

    DB:2.48:Webservice Returns Correct Value But Flex Sees It As Null px


    Nice, I just realized that my original post only had the WSDL. Sorry about that. The underlying issue I am having is, the Flex Builder 3 Manage Web Services wizard consumes the wsdl just fine, creates all necessary classes and from there I can instantiate and call the webservice. Using Service Capture I see the SOAP response come back, I can debug in Flex Builder and step through the code and see the response was returned but it gets lost within the SOAPDecoder.as in the decodeBody() method.

    Unfortunately, I can not open up a port to allow anyone to try it out. The best I can do is post the SOAP request body and the SOAP response body along with the wsdl.

    SOAP Request Body:

    SOAP-ENV:Envelope xmlns="http://www.w3.org/2001/XMLSchema" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

    SOAP-ENV:Body

    intf:startSession xmlns:intf="http://company.com/HeliumWS"

    intf:usernameDEV/intf:username

    /intf:startSession

    /SOAP-ENV:Body

    /SOAP-ENV:Envelope

    SOAP Reponse Body:

    env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

    env:Body

    n1:startSessionResponse env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:n1="http://company.com/HeliumWS"

    return xmlns:n2="http://www.ruby-lang.org/xmlns/ruby/type/custom" xsi:type="n2:HeliumWS..StartSessionReturn"

    sessionID xsi:type="xsd:string"session7a86c52d/sessionID

    /return

    /n1:startSessionResponse

    /env:Body

    /env:Envelope

    WSDL:

    ?xml version="1.0" encoding="UTF-8"? wsdl:definitions targetNamespace="http://company.com/HeliumWS" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://company.com/HeliumWS" xmlns:intf="http://company.com/HeliumWS" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" wsdl:types schema elementFormDefault="qualified" targetNamespace="http://company.com/HeliumWS" xmlns="http://www.w3.org/2001/XMLSchema" element name="startSession" complexType sequence element name="username" nillable="true" type="xsd:string"/ /sequence /complexType /element element name="startSessionResponse" complexType sequence element name="returnValue" type="intf:startSessionReturn"/ /sequence /complexType /element complexType name="startSessionReturn" sequence element name="sessionID" type="xsd:string"/ /sequence /complexType /schema /wsdl:types wsdl:message name="startSessionRequest" wsdl:part element="impl:startSession" name="parameters"/ /wsdl:message wsdl:message name="startSessionResponse" wsdl:part element="impl:startSessionResponse" name="parameters"/ /wsdl:message wsdl:portType name="MCUBindingImpl" wsdl:operation name="startSession" wsdl:input message="impl:startSessionRequest" name="startSessionRequest"/ wsdl:output message="impl:startSessionResponse" name="startSessionResponse"/ /wsdl:operation /wsdl:portType wsdl:binding name="MCUBindingImplSoapBinding" type="impl:MCUBindingImpl" wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/ wsdl:operation name="startSession" wsdlsoap:operation soapAction=""/ wsdl:input name="startSessionRequest" wsdlsoap:body use="literal"/ /wsdl:input wsdl:output name="startSessionResponse" wsdlsoap:body use="literal"/ /wsdl:output /wsdl:operation /wsdl:binding wsdl:service name="MCUBindingImplService" wsdl:port binding="impl:MCUBindingImplSoapBinding" name="MCUBindingImpl" wsdlsoap:address location="http://10.10.20.82/soap"/ /wsdl:port /wsdl:service /wsdl:definitions

  • RELEVANCY SCORE 2.48

    DB:2.48:Xsi On Japanese Os 9p


    Hi everybody!I've a big problem with XSI and Japanese windows-XPprefessional-32bitThe error is that the User directory is not wrote in ASCII font.I tried to change every single thing (if it was possible) in Alphabet but everytime the same error... and XSI don't work.

    DB:2.48:Xsi On Japanese Os 9p

    ehi "StephenBlair" Workin' perfect, now I can show XSI to my Boss and meabe He will buy that for me TNX!

  • RELEVANCY SCORE 2.48

    DB:2.48:Jax-Prc : How To Get The Address Of The Requesting Client c3


    I used JAX-RPC to write a webserice that collects data(strings) from client. The client is written in a dynamic interface invocation (DII) fashion.

    However, I would like to know if there is any way I can retrieve the client url and print it out on the web service server side. Is there anything to deal with xml soap namesapce ?

    Please advise. thanks!

    DB:2.48:Jax-Prc : How To Get The Address Of The Requesting Client c3

    I used JAX-RPC to write a webserice that collects data(strings) from client. The client is written in a dynamic interface invocation (DII) fashion.

    However, I would like to know if there is any way I can retrieve the client url and print it out on the web service server side. Is there anything to deal with xml soap namesapce ?

    Please advise. thanks!

  • RELEVANCY SCORE 2.48

    DB:2.48:Client Found Response Content Type Of Text/Plain, But Expected Text/Xml. pm


    Hi friendsam call a 3rd party web service and when i call one of their methods i get above errorany ideas how to resolve this please ?Thanks for ur helpfull error textClient found response content type of 'text/plain', but expected 'text/xml'.The request failed with the error message:--?xml version=1.0 encoding=UTF-8?wsdl:definitions xmlns=http://schemas.xmlsoap.org/wsdl/ xmlns:apachesoap=http://xml.apache.org/xml-soap xmlns:impl=urn:submissionGateway/wsdl xmlns:intf=urn:submissionGateway/wsdl xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/ xmlns:sg=urn:submissionGateway xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/ xmlns:wsdlsoap=http://schemas.xmlsoap.org/wsdl/soap/ xmlns:xsd=http://www.w3.org/2001/XMLSchema targetNamespace=urn:submissionGateway/wsdl    wsdl:types        schema targetNamespace=urn:submissionGateway/wsdl xmlns=http://www.w3.org/2001/XMLSchema            import namespace=urn:submissionGateway schemaLocation=submissionGateway.xsd/        /schema    /wsdl:types    wsdl:message name=soapIn        wsdl:part name=send element=sg:send/    /wsdl:message    wsdl:message name=soapOut        wsdl:part name=sendResponse element=sg:sendResponse/    /wsdl:message    wsdl:message name=getVersionRequest   /wsdl:message    wsdl:message name=getVersionResponse        wsdl:part name=getVersionResponse element=sg:getVersionResponse/    /wsdl:message    wsdl:message name=validateAccountRequest        wsdl:part name=validateAccount element=sg:validateAccount/    /wsdl:message    wsdl:message name=validateAccountResponse        wsdl:part name=validateAccountResponse element=sg:validateAccountResponse/    /wsdl:message    wsdl:portType name=SubmissionGateway        wsdl:operation name=send            wsdl:input message=impl:soapIn/            wsdl:output message=impl:soapOut/        /wsdl:operation        wsdl:operation name=getVersion            wsdl:input message=impl:getVersionRequest/            wsdl:output message=impl:getVersionResponse/        /wsdl:operation        wsdl:operation name=validateAccount            wsdl:input message=impl:validateAccountRequest/            wsdl:output message=impl:validateAccountResponse/        /wsdl:operation    /wsdl:portType    wsdl:binding name=SubmissionGatewaySoapBinding type=impl:SubmissionGateway        wsdlsoap:binding style=document transport=http://schemas.xmlsoap.org/soap/http/        wsdl:operation name=send            wsdlsoap:operation soapAction=urn:#send/            wsdl:input                wsdlsoap:body use=literal namespace=urn:submissionGateway/wsdl/            /wsdl:input            wsdl:output                wsdlsoap:body use=literal namespace=urn:submissionGateway/wsdl/            /wsdl:output        /wsdl:operation        wsdl:operation name=getVersion            wsdlsoap:operation soapAction=urn:#getVersion/            wsdl:input                wsdlsoap:body use=literal namespace=urn:submissionGateway/wsdl/            /wsdl:input            wsdl:output                wsdlsoap:body use=literal namespace=urn:submissionGateway/wsdl/            /wsdl:output        /wsdl:operation        wsdl:operation name=validateAccount            wsdlsoap:operation soapAction=urn:#validateAccount/            wsdl:input                wsdlsoap:body use=literal namespace=urn:submissionGateway/wsdl/            /wsdl:input            wsdl:output                wsdlsoap:body use=literal namespace=urn:submissionGateway/wsdl/            /wsdl:output        /wsdl:operation    /wsdl:binding    wsdl:service name=SubmissionGatewayService        wsdl:port name=SubmissionGateway binding=impl:SubmissionGatewaySoapBinding            wsdlsoap:address location=http://hlk-dbtest:5099/SubmissionGateway/        /wsdl:port    /wsdl:service/wsdl:definitions--.

    DB:2.48:Client Found Response Content Type Of Text/Plain, But Expected Text/Xml. pm

    Had the same problem. Made contact with an Axis webservice but kept on receiving the message. A last I added the line System.Net.ServicePointManager.Expect100Continue = false; before the ws call. This solved my problem.
     

  • RELEVANCY SCORE 2.48

    DB:2.48:Unsupported Content-Type: Application/Soap+Xml c9


    I've created a simple composite application with a bpel jbi module using glassfishesbv21.
    The bpel process starts when I invoke a webservice (soap-binding).
    When I run a test case for the ca everything works fine.
    When I call the webservice from an external web application, the client (created with netbeans wizard bundled in glassfishesbv21) obtains the response as expected and doesn't report any exception while the server rises a com.sun.xml.ws.server.UnsupportedMediaException.
    Googoling I found that this maybe caused by the use of soap1.1 and soap1.2 but is also true that JAX-WS runtime should look into the WSDL to determine the binding being used and configures itself accordingly.

    the stacktrace is:
    ....
    Finished processing outbound messages.
    Request doesnt have a Content-Type
    com.sun.xml.ws.server.UnsupportedMediaException: Request doesnt have a Content-Type
    at com.sun.xml.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:267)
    at com.sun.xml.ws.transport.http.HttpAdapter.decodePacket(HttpAdapter.java:276)
    at com.sun.xml.ws.transport.http.HttpAdapter.invokeAsync(HttpAdapter.java:341)
    at com.sun.jbi.httpsoapbc.embedded.JAXWSGrizzlyRequestProcessor.processAsynchRequest(JAXWSGrizzlyRequestProcessor.java:386)
    at com.sun.jbi.httpsoapbc.embedded.JAXWSGrizzlyRequestProcessor.service(JAXWSGrizzlyRequestProcessor.java:220)
    at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:647)
    at com.sun.jbi.httpsoapbc.embedded.JBIGrizzlyAsyncFilter.doFilter(JBIGrizzlyAsyncFilter.java:95)
    at com.sun.enterprise.web.connector.grizzly.async.DefaultAsyncExecutor.invokeFilters(DefaultAsyncExecutor.java:175)
    at com.sun.enterprise.web.connector.grizzly.async.DefaultAsyncExecutor.interrupt(DefaultAsyncExecutor.java:153)
    at com.sun.enterprise.web.connector.grizzly.async.AsyncProcessorTask.doTask(AsyncProcessorTask.java:92)
    at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:265)
    at com.sun.enterprise.web.connector.grizzly.WorkerThreadImpl.run(WorkerThreadImpl.java:116)
    Unsupported Content-Type: application/soap+xml Supported ones are: [text/xml]
    com.sun.xml.ws.server.UnsupportedMediaException: Unsupported Content-Type: application/soap+xml Supported ones are: [text/xml]
    at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:291)
    at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:128)
    ...
    ====[com.sun.xml.ws.assembler.server:request]====
    ?xml version="1.0" ?
    soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsa="http://www.w3.org/2005/08/addressing"
    soap-env:Header
    wsa:Actionhttp://schemas.xmlsoap.org/ws/2004/09/transfer/Get/wsa:Action
    wsa:Tohttp://localhost:19081/coreAnagrafeUpdateService/coreAnagrafeUpdatePort/wsa:To
    wsa:ReplyTo
    wsa:Addresshttp://www.w3.org/2005/08/addressing/anonymous/wsa:Address
    /wsa:ReplyTo
    wsa:MessageIDuuid:778b135f-3fdf-44b2-b53e-ebaab7441e40/wsa:MessageID
    /soap-env:Header
    soap-env:Body/soap-env:Body
    /soap-env:Envelope
    ============
    ...
    ====[com.sun.xml.ws.assembler.server:response]====
    ?xml version="1.0" ?
    S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"
    S:Body
    S:Fault xmlns:ns3="http://www.w3.org/2003/05/soap-envelope" xmlns=""
    faultcodeS:Server/faultcode
    faultstringjavax.jbi.messaging.MessagingException: HTTPBC-E00798: Message normalization failed/faultstring
    /S:Fault
    /S:Body
    /S:Envelope
    ============
    Unsupported Content-Type: application/soap+xml Supported ones are: [text/xml]
    com.sun.xml.ws.server.UnsupportedMediaException: Unsupported Content-Type: application/soap+xml Supported ones are: [text/xml]
    at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:291)
    at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:128)
    at com.sun.xml.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:287)
    ...
    ====[com.sun.xml.ws.assembler.server:request]====
    ?xml version="1.0" ?
    soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsa="http://www.w3.org/2005/08/addressing"
    soap-env:Header
    wsa:Actionhttp://schemas.xmlsoap.org/ws/2004/09/transfer/Get/wsa:Action
    wsa:Tohttp://localhost:19081/coreAnagrafeUpdateService/coreAnagrafeUpdatePort/mex/wsa:To
    wsa:ReplyTo
    wsa:Addresshttp://www.w3.org/2005/08/addressing/anonymous/wsa:Address
    /wsa:ReplyTo
    wsa:MessageIDuuid:778b135f-3fdf-44b2-b53e-ebaab7441e40/wsa:MessageID
    /soap-env:Header
    soap-env:Body/soap-env:Body
    /soap-env:Envelope
    ============

    the wsdl is:
    ?xml version="1.0" encoding="UTF-8" standalone="yes"?
    definitions name="coreAnagrafeUpdateService"
    targetNamespace="http://service.box.nexus.com/"
    xmlns="http://schemas.xmlsoap.org/wsdl/"
    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:tns="http://service.box.nexus.com/"
    xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
    xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" types
    xsd:schema
    xsd:import namespace="http://service.box.nexus.com/" schemaLocation="core_anagrafe.xsd"/
    /xsd:schema
    /types
    message name="coreAnagrafeUpdateOperationRequest"
    part name="parameters" element="tns:requestParameter"/
    /message
    message name="coreAnagrafeUpdateOperationResponse"
    part name="parameters" element="tns:coreAnagrafeResponse"/
    /message
    message name="coreAnagrafeUpdateOperationFault"
    part name="part1" element="tns:faultMessage"/
    /message
    portType name="coreAnagrafeUpdatePortType"
    operation name="coreAnagrafeUpdateOperation"
    input message="tns:coreAnagrafeUpdateOperationRequest"/
    output message="tns:coreAnagrafeUpdateOperationResponse"/
    wsdl:fault name="fault1" message="tns:coreAnagrafeUpdateOperationFault"/
    /operation
    /portType
    binding name="coreAnagrafeUpdateBinding" type="tns:coreAnagrafeUpdatePortType"
    soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/
    operation name="coreAnagrafeUpdateOperation"
    soap:operation soapAction=""/
    input
    soap:body use="literal" /
    /input
    output
    soap:body use="literal" /
    /output
    wsdl:fault name="fault1"
    soap:fault use="literal" name="fault1"/
    /wsdl:fault
    /operation
    /binding
    service name="coreAnagrafeUpdateService"
    port name="coreAnagrafeUpdatePort" binding="tns:coreAnagrafeUpdateBinding"
    soap:address location="http://localhost:19081/coreAnagrafeUpdateService/coreAnagrafeUpdatePort"/
    /port
    /service
    /definitions

    Can anyone help me to understand the problem and solve it?

    Thanks in advance.

    DB:2.48:Unsupported Content-Type: Application/Soap+Xml c9

    I've created a simple composite application with a bpel jbi module using glassfishesbv21.
    The bpel process starts when I invoke a webservice (soap-binding).
    When I run a test case for the ca everything works fine.
    When I call the webservice from an external web application, the client (created with netbeans wizard bundled in glassfishesbv21) obtains the response as expected and doesn't report any exception while the server rises a com.sun.xml.ws.server.UnsupportedMediaException.
    Googoling I found that this maybe caused by the use of soap1.1 and soap1.2 but is also true that JAX-WS runtime should look into the WSDL to determine the binding being used and configures itself accordingly.

    the stacktrace is:
    ....
    Finished processing outbound messages.
    Request doesnt have a Content-Type
    com.sun.xml.ws.server.UnsupportedMediaException: Request doesnt have a Content-Type
    at com.sun.xml.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:267)
    at com.sun.xml.ws.transport.http.HttpAdapter.decodePacket(HttpAdapter.java:276)
    at com.sun.xml.ws.transport.http.HttpAdapter.invokeAsync(HttpAdapter.java:341)
    at com.sun.jbi.httpsoapbc.embedded.JAXWSGrizzlyRequestProcessor.processAsynchRequest(JAXWSGrizzlyRequestProcessor.java:386)
    at com.sun.jbi.httpsoapbc.embedded.JAXWSGrizzlyRequestProcessor.service(JAXWSGrizzlyRequestProcessor.java:220)
    at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:647)
    at com.sun.jbi.httpsoapbc.embedded.JBIGrizzlyAsyncFilter.doFilter(JBIGrizzlyAsyncFilter.java:95)
    at com.sun.enterprise.web.connector.grizzly.async.DefaultAsyncExecutor.invokeFilters(DefaultAsyncExecutor.java:175)
    at com.sun.enterprise.web.connector.grizzly.async.DefaultAsyncExecutor.interrupt(DefaultAsyncExecutor.java:153)
    at com.sun.enterprise.web.connector.grizzly.async.AsyncProcessorTask.doTask(AsyncProcessorTask.java:92)
    at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:265)
    at com.sun.enterprise.web.connector.grizzly.WorkerThreadImpl.run(WorkerThreadImpl.java:116)
    Unsupported Content-Type: application/soap+xml Supported ones are: [text/xml]
    com.sun.xml.ws.server.UnsupportedMediaException: Unsupported Content-Type: application/soap+xml Supported ones are: [text/xml]
    at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:291)
    at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:128)
    ...
    ====[com.sun.xml.ws.assembler.server:request]====
    ?xml version="1.0" ?
    soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsa="http://www.w3.org/2005/08/addressing"
    soap-env:Header
    wsa:Actionhttp://schemas.xmlsoap.org/ws/2004/09/transfer/Get/wsa:Action
    wsa:Tohttp://localhost:19081/coreAnagrafeUpdateService/coreAnagrafeUpdatePort/wsa:To
    wsa:ReplyTo
    wsa:Addresshttp://www.w3.org/2005/08/addressing/anonymous/wsa:Address
    /wsa:ReplyTo
    wsa:MessageIDuuid:778b135f-3fdf-44b2-b53e-ebaab7441e40/wsa:MessageID
    /soap-env:Header
    soap-env:Body/soap-env:Body
    /soap-env:Envelope
    ============
    ...
    ====[com.sun.xml.ws.assembler.server:response]====
    ?xml version="1.0" ?
    S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"
    S:Body
    S:Fault xmlns:ns3="http://www.w3.org/2003/05/soap-envelope" xmlns=""
    faultcodeS:Server/faultcode
    faultstringjavax.jbi.messaging.MessagingException: HTTPBC-E00798: Message normalization failed/faultstring
    /S:Fault
    /S:Body
    /S:Envelope
    ============
    Unsupported Content-Type: application/soap+xml Supported ones are: [text/xml]
    com.sun.xml.ws.server.UnsupportedMediaException: Unsupported Content-Type: application/soap+xml Supported ones are: [text/xml]
    at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:291)
    at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:128)
    at com.sun.xml.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:287)
    ...
    ====[com.sun.xml.ws.assembler.server:request]====
    ?xml version="1.0" ?
    soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsa="http://www.w3.org/2005/08/addressing"
    soap-env:Header
    wsa:Actionhttp://schemas.xmlsoap.org/ws/2004/09/transfer/Get/wsa:Action
    wsa:Tohttp://localhost:19081/coreAnagrafeUpdateService/coreAnagrafeUpdatePort/mex/wsa:To
    wsa:ReplyTo
    wsa:Addresshttp://www.w3.org/2005/08/addressing/anonymous/wsa:Address
    /wsa:ReplyTo
    wsa:MessageIDuuid:778b135f-3fdf-44b2-b53e-ebaab7441e40/wsa:MessageID
    /soap-env:Header
    soap-env:Body/soap-env:Body
    /soap-env:Envelope
    ============

    the wsdl is:
    ?xml version="1.0" encoding="UTF-8" standalone="yes"?
    definitions name="coreAnagrafeUpdateService"
    targetNamespace="http://service.box.nexus.com/"
    xmlns="http://schemas.xmlsoap.org/wsdl/"
    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:tns="http://service.box.nexus.com/"
    xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
    xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" types
    xsd:schema
    xsd:import namespace="http://service.box.nexus.com/" schemaLocation="core_anagrafe.xsd"/
    /xsd:schema
    /types
    message name="coreAnagrafeUpdateOperationRequest"
    part name="parameters" element="tns:requestParameter"/
    /message
    message name="coreAnagrafeUpdateOperationResponse"
    part name="parameters" element="tns:coreAnagrafeResponse"/
    /message
    message name="coreAnagrafeUpdateOperationFault"
    part name="part1" element="tns:faultMessage"/
    /message
    portType name="coreAnagrafeUpdatePortType"
    operation name="coreAnagrafeUpdateOperation"
    input message="tns:coreAnagrafeUpdateOperationRequest"/
    output message="tns:coreAnagrafeUpdateOperationResponse"/
    wsdl:fault name="fault1" message="tns:coreAnagrafeUpdateOperationFault"/
    /operation
    /portType
    binding name="coreAnagrafeUpdateBinding" type="tns:coreAnagrafeUpdatePortType"
    soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/
    operation name="coreAnagrafeUpdateOperation"
    soap:operation soapAction=""/
    input
    soap:body use="literal" /
    /input
    output
    soap:body use="literal" /
    /output
    wsdl:fault name="fault1"
    soap:fault use="literal" name="fault1"/
    /wsdl:fault
    /operation
    /binding
    service name="coreAnagrafeUpdateService"
    port name="coreAnagrafeUpdatePort" binding="tns:coreAnagrafeUpdateBinding"
    soap:address location="http://localhost:19081/coreAnagrafeUpdateService/coreAnagrafeUpdatePort"/
    /port
    /service
    /definitions

    Can anyone help me to understand the problem and solve it?

    Thanks in advance.

  • RELEVANCY SCORE 2.48

    DB:2.48:Add A Security Header To Soap Message Using Mssoap30 mk


    Hi I'm really stuck on getting my SOAP messages to work. I've tried many approaches but they all have the same problem in common: they don't have a security header. The security header needs to contain a username and password. In VB.Net this is done by:
    userNameAssertion.UsernameTokenProvider = new
    UsernameTokenProvider(username, password);

    Policy policy = new Policy();
    policy.Assertions.Add(userNameAssertion);
    proxy.SetPolicy(policy);
    Two routines which I am developing which don't work are at the end of this message. There is a third which uses the MS SOAP Toolkit 3, but this gives so many errors it doesn't seem worth using if it's not necessary. If it is, then the errors alternate on first run are class not registered but subsequently no such interface supported. That error occurs on the line:
    Set sc_partservice = New SoapClient30
    Any help to get this working will be greatly appreciated! Thanks David
    Dim ENC As String
    Dim XSI As String
    Dim XSD As String

    Sub SOAPsuds()

    'Define Envelope Constants
    ENC = http://schemas.xmlsoap.org/soap/encoding/ 'Encoding
    XSI = http://www.w3.org/1999/XMLSchema-instance 'Schema Instance
    XSD = http://www.w3.org/1999/XMLSchema 'Schema

    'Define Envelope Variables
    URL = omitted 'Web Service
    Uri = omitted
    Method = omitted 'Web Method

    'Instantiate things
    Dim Connector As SoapConnector30
    Dim Serializer As SoapSerializer30
    Dim Reader As SoapReader30
    Set Connector = New HttpConnector30
    Set Serializer = New SoapSerializer30
    Set Reader = New SoapReader30

    'Prepare the Connector to talk to the SOAP Server
    Connector.Property(EndPointURL) = URL
    Call Connector.Connect
    Connector.Property(SoapAction) = Uri # Method
    Call Connector.BeginMessage

    'Associate Serializer with Connector
    Serializer.Init Connector.InputStream

    'Start the SOAP Envelope and specify the Encoding and XML-Schema
    Serializer.StartEnvelope , ENC
    Serializer.SoapNamespace xsi, XSI
    Serializer.SoapNamespace SOAP-ENC, ENC
    Serializer.SoapNamespace xsd, XSD

    'Start the body of the message
    Serializer.StartBody
    Serializer.StartElement Method, Uri, , method

    'Write each method parameter out as a child to the root element
    Serializer.StartElement Author
    Serializer.SoapAttribute type, , xsd:string, xsi
    Serializer.WriteString Wilde, Oscar
    Serializer.EndElement

    'End the root element, the body and the envelope
    Serializer.EndElement
    Serializer.EndBody
    Serializer.EndEnvelope

    'Ending the message causes it to be sent
    Connector.EndMessage

    'Load the result into the Reader
    Reader.Load Connector.OutputStream

    'If ok then pull result out of DOM
    If Not Reader.Fault Is Nothing Then
    MsgBox Reader.FaultString.text, vbExclamation
    Else
    Set Result = Reader.Dom
    '//parse the DOM to extract the result set
    End If

    End Sub

    Dim oDoc As MSXML2.DOMDocument

    Private Sub WSTest1()
    On Error GoTo ErrorHandler

    'Define Services
    Dim PartService
    Set PartService = CreateObject(MSSOAP.SoapClient30)
    PartService.MSSoapInit URL 'string substituted

    xmlSchema C:\Documents and Settings\User\Desktop\SOAP XML VB\Schemas\Request\GetByIDRequest.xsd

    'Query Services
    test = (PartService.GetByID(oDoc.documentElement))

    Exit Sub

    'Handle WSDL Errors
    ErrorHandler:
    If Err.Number = -2147024809 Then
    MsgBox run-time error: ' Err.Number ': Chr(13) Chr(13) Err.Description Chr(13) This is a WSDL Error
    End If

    End Sub

    Function xmlSchema(StrXML)

    Dim fSuccess As Boolean

    Set oDoc = New MSXML2.DOMDocument
    oDoc.async = False
    oDoc.validateOnParse = False
    fSuccess = oDoc.Load(StrXML)
    If Not fSuccess Then
    MsgBox oDoc.parseError.reason
    End If

    End Function

    DB:2.48:Add A Security Header To Soap Message Using Mssoap30 mk

    Hi Steve That's some excellent info. Thanks. Perhaps my best bet would be to write a dll in c# and utilise that somehow from VB. I can write the dll easily enough, but I don't know if I'll encounter difficulties in utilising it from VB. Any thoughts? Thanks David

  • RELEVANCY SCORE 2.48

    DB:2.48:Document/Literal Plsql Web Service. js


    Hi,

    I'm trying to develop a web service to expose some plsql package functions as a web service to be called from BPEL using:-

    OAS 10.1.2.0.2
    JDeveloper 10.1.2.2.0
    BPEL 10.1.2.0.2

    I initially used Objects as the parameters for the functions as this allows JDeveloper to generate an rpc/encoded web service that works quite well, however some of the input and output data is quite complex so the generated web service uses SOAP Arrays to represent it. Unfortunately it seems that BPEL does not support SOAP Arrays so my customer is unable to call the web service and use BPEL functionality to manipulate the data returned.

    In an attempt to get around this I have changed the parameters of the plsql functions to xmltype and transform/build the xml within the plsql code, JDeveloper generates an rpc/literal web service to deal with this however again this is not supported very well by BPEL (the customer has to use embedded java in the bpel process to manually build the soap message and call the web service operation as a partner link seems to insist on using the encoding style rather than literal).

    I would like to try to make life easier for my customer by producing a document/literal web service as this seems to be better supported by BPEL, with this in mind I found the following entries in the OTN forums:-

    Document/Literal SOAP format generation using jdeveloper 10.1.2.0.0
    web services jdbc

    I have followed the instructions given i.e. changed the servlet class to oracle.j2ee.ws.StatelessJavaDocWebService in web.xml and generated a document/literal wsdl file, however when I deploy and invoke the resultant web service I get the following fault soap fault back:-

    ?xml version='1.0' encoding='UTF-8'?
    SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    SOAP-ENV:Body
    SOAP-ENV:Fault
    faultcodeSOAP-ENV:Server.Exception:/faultcode
    faultstringjava.sql.SQLException: found null connection context/faultstring
    faultactor/get_users_doc/Get_users_doc/faultactor
    /SOAP-ENV:Fault
    /SOAP-ENV:Body
    /SOAP-ENV:Envelope

    I can only assume that the way the sqlj classes, generated by the plsql web service wizard in JDeveloper, connect to the database is not supported by the oracle.j2ee.ws.StatelessJavaDocWebService servlet but I don't know how to get around this.

    Any suggestions on how I can fix the connection issue or a better way to build a document/litteral web service that will call my plsql would be very much appreciated.

    DB:2.48:Document/Literal Plsql Web Service. js

    Hi,

    I'm trying to develop a web service to expose some plsql package functions as a web service to be called from BPEL using:-

    OAS 10.1.2.0.2
    JDeveloper 10.1.2.2.0
    BPEL 10.1.2.0.2

    I initially used Objects as the parameters for the functions as this allows JDeveloper to generate an rpc/encoded web service that works quite well, however some of the input and output data is quite complex so the generated web service uses SOAP Arrays to represent it. Unfortunately it seems that BPEL does not support SOAP Arrays so my customer is unable to call the web service and use BPEL functionality to manipulate the data returned.

    In an attempt to get around this I have changed the parameters of the plsql functions to xmltype and transform/build the xml within the plsql code, JDeveloper generates an rpc/literal web service to deal with this however again this is not supported very well by BPEL (the customer has to use embedded java in the bpel process to manually build the soap message and call the web service operation as a partner link seems to insist on using the encoding style rather than literal).

    I would like to try to make life easier for my customer by producing a document/literal web service as this seems to be better supported by BPEL, with this in mind I found the following entries in the OTN forums:-

    Document/Literal SOAP format generation using jdeveloper 10.1.2.0.0
    web services jdbc

    I have followed the instructions given i.e. changed the servlet class to oracle.j2ee.ws.StatelessJavaDocWebService in web.xml and generated a document/literal wsdl file, however when I deploy and invoke the resultant web service I get the following fault soap fault back:-

    ?xml version='1.0' encoding='UTF-8'?
    SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    SOAP-ENV:Body
    SOAP-ENV:Fault
    faultcodeSOAP-ENV:Server.Exception:/faultcode
    faultstringjava.sql.SQLException: found null connection context/faultstring
    faultactor/get_users_doc/Get_users_doc/faultactor
    /SOAP-ENV:Fault
    /SOAP-ENV:Body
    /SOAP-ENV:Envelope

    I can only assume that the way the sqlj classes, generated by the plsql web service wizard in JDeveloper, connect to the database is not supported by the oracle.j2ee.ws.StatelessJavaDocWebService servlet but I don't know how to get around this.

    Any suggestions on how I can fix the connection issue or a better way to build a document/litteral web service that will call my plsql would be very much appreciated.

  • RELEVANCY SCORE 2.48

    DB:2.48:Possible Namespace Bug In C Xml Parser d1


    I'm using the C XML Parser v 2.0.7 on Solaris 2.6, and I am encountering this problem.

    My application is attempting to parse a SOAP envelope, with the "xsi" namepsace prefix declared inside the root tag. If the "xsi" prefix is declared first inside that tag, it works. If it is declared second or third, as is the case with the input the soapclient.com generic soap client provides, the parser dies with the error "namespace prefix xsi not declared". It also works if I declare the namespace inside the tag where it actually gets used.

    Any help with this matter would be sincerely appreciated

    See example below.

    ?xml version="1.0"?
    SOAP-ENV:Envelope
    xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
    xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
    SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" SOAP-ENV:Body
    mns:EchoInput
    xmlns:mns="http://www.urbanite.com/xml/schema/urbmethods.xsd"
    what xsi:type="xsd:string"Echo/what
    /mns:EchoInput
    /SOAP-ENV:Body
    /SOAP-ENV:Envelope
    null

  • RELEVANCY SCORE 2.48

    DB:2.48:Problem With Client Code. fx


    Hi,
    I am trying to us SAAJ to use a simple HelloWorld service.

    I have written a published a HelloWorld wev service.
    Here is the wsdl.

    definitions targetNamespace="http://hellowebservice/" name="HelloWSService"
    types/
    minus;
    message name="sayHello"
    part name="arg0" type="xsd:string"/
    /message
    minus;
    message name="sayHelloResponse"
    part name="return" type="xsd:string"/
    /message
    minus;
    portType name="Hello"
    minus;
    operation name="sayHello"
    input message="tns:sayHello"/
    output message="tns:sayHelloResponse"/
    /operation
    /portType
    minus;
    binding name="HelloWSPortBinding" type="tns:Hello"
    soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="rpc"/
    minus;
    operation name="sayHello"
    soap:operation soapAction=""/
    minus;
    input
    soap:body use="literal" namespace="http://hellowebservice/"/
    /input
    minus;
    output
    soap:body use="literal" namespace="http://hellowebservice/"/
    /output
    /operation
    /binding
    minus;
    service name="HelloWSService"
    minus;
    port name="HelloWSPort" binding="tns:HelloWSPortBinding"
    soap:address location="http://localhost:9999/hello"/
    /port
    /service
    /definitionsHere is the client code:

    URL wsdl = new URL("http://localhost:9999/hello?wsdl");
    String ns = "http://hellowebservice/";

    String svcName = "HelloWSService";
    QName svcQName = new QName(ns, svcName);

    // Get a delegate wrapper
    Service service = Service.create(wsdl, svcQName);

    // Create the Port name
    String portName = "HelloWSPort";
    QName portQName = new QName(ns, portName);

    DispatchSOAPMessage dispatch =
    service.createDispatch(portQName,
    SOAPMessage.class,
    Service.Mode.MESSAGE);

    // Create the message
    SOAPMessage soapMsg =
    MessageFactory.newInstance().createMessage();

    // Get the body from the envelope
    SOAPPart soapPart =soapMsg.getSOAPPart();
    SOAPEnvelope env = soapPart.getEnvelope();
    SOAPBody body = env.getBody();

    // debug print what we're sending
    soapMsg.writeTo(System.out);
    System.out.println("\nInvoking...");

    //send the message as request to service and get response
    SOAPMessage response = dispatch.invoke(soapMsg);

    // just show in the console for now
    response.writeTo(System.out);The soap message out putted to console is
    SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"SOAP-ENV:Header/SOAP-ENV:Body//SOAP-ENV:EnvelopeThe error I am getting is:

    Exception in thread "main" javax.xml.ws.soap.SOAPFaultException: Cannot find dispatch method for {}
    at com.sun.xml.internal.ws.fault.SOAP11Fault.getProtocolException(Unknown Source)Which makes sense. What API's do I need to call on the SOAP BODY so that I can invoke the HelloWorld service?

    Any ideas?

    Edited by: beginner2 on May 15, 2010 6:12 AM

    DB:2.48:Problem With Client Code. fx

    Thanks so much.

    Here is the answer to for this specific code..

    SOAPElement operation = body.addChildElement("sayHello", "ns1",
    "http://hellowebservice/");
    SOAPElement value = operation.addChildElement("arg0");
    value.addTextNode("ping");

  • RELEVANCY SCORE 2.48

    DB:2.48:Does Dii Support Document Based Web Service? pd


    Hi,

    I am writing a web service cleint DII, the web service is document based. I followed the sample in
    https://bpcatalog.dev.java.net/nonav/soa/standalone-client/

    Everything seems correct. When I call call.invoke, I got an exception saying "operation style: \"document\" not supported".
    Here is the code fragment, can anyone tell me what's wrong or does DII support document based service?

    Thanks a lot!
    Y. Zhao

    try {
    ServiceFactory factory = ServiceFactory.newInstance();
    service = factory.createService(new QName(EXTRACTURLSERVICE));
    port = new QName(EXTRACTURLPORT);
    } catch (Exception se) {
    // throw new Exception("Can not create stock service: " + se.getMessage());
    }

    _endPointAddr = "http://www.atomic-x.com/xmlservices/HyperlinkExtractor.asmx";
    _qnameNamespaceURI = new QName("ExtractUrl");
    requestQname = new QName(NAMESPACE_URI, "ExtractUrl");
    responseQname = new QName(NAMESPACE_URI, "ExtractUrlResponse");

    Call call = null;

    try {
    call = service.createCall(port);
    call.setTargetEndpointAddress(_endPointAddr);
    call.setProperty(Call.SOAPACTION_USE_PROPERTY,
    Boolean.TRUE);
    call.setProperty(Call.SOAPACTION_URI_PROPERTY, "http://www.atomic-x.com/xmlservices/HyperlinkExtractor/ExtractUrl");
    call.setProperty("javax.xml.rpc.encodingstyle.namespace.uri", "");
    call.setProperty(Call.OPERATION_STYLE_PROPERTY, "document");

    call.setProperty(Call.ENCODINGSTYLE_URI_PROPERTY, "literal");

    call.addParameter("parameters", requestQname, ExtractUrl.class, ParameterMode.IN);
    call.setReturnType(responseQname, ExtractUrlResponse.class);
    result = (ExtractUrlResponse)call.invoke((Object[])params);
    } catch (Exception ex) {
    //throw new ServiceException("Can not get service: " + ex.getMessage());
    String msg = ex.getMessage();
    ex.printStackTrace();
    }

    DB:2.48:Does Dii Support Document Based Web Service? pd

    Thanks for your response!

    The WSDL specified it's document, not rpc.

    The web service is written in .net. I saw some posts it has some issues to work with Java clients, but didn't saw any solution or response for that.

    Thanks!

  • RELEVANCY SCORE 2.48

    DB:2.48:Possible To Use A Jsr 109 Client With A Custom Soap Address zx



    Is it possible to use a JSR 109 client with a locally packaged wsdl file (i.e., META-INF/Service.wsdl), yet override the soap:address that the ServiceFactory uses?I basically want to call a web-service at a URL that I specify at runtime.In the JbossWS user guide, it appears that I can do this using an unconfigured DII client (http://labs.jboss.com/portal/jbossws/user-guide/en/html_single/index.html#dii-clients) . But I'd like to do this with a JSR 109 client.It appears that I can change the published wsdl location using a JSR109 client, per the following code:

    ServiceFactoryImpl factory = (ServiceFactoryImpl) ServiceFactory.newInstance();
    ClassLoader cl = Thread.currentThread().getContextClassLoader();
    URL wsdlLocation = cl.getResource("Service.wsdl");
    URL mappingLocation = cl.getResource("jaxrpc-mapping-client.xml");
    QName serviceName = new QName(SERVICE_NAMESPACE, ENDPOINT_SERVICE_NAME);
    ServiceImpl service = (ServiceImpl) factory.createService(wsdlLocation, serviceName, mappingLocation);

    ServiceMetaData data = service.getServiceMetaData();
    data.setWsdlPublishLocation()

    DB:2.48:Possible To Use A Jsr 109 Client With A Custom Soap Address zx


    Yes, that is possible. Look at javax.xml.rpc.Stub.ENDPOINT_ADDRESS_PROPERTY

  • RELEVANCY SCORE 2.47

    DB:2.47:Namespace_Err Using Saaj 99


    Hi

    We use JWSDP 1.5 and Java 1.4.2.06 within a generic mechanism that generates out SOAP for calling external webservices. Since upgrading from JWSDP 1.1. we are unable to generate SOAP messages like the following
    code
    SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="sx3_app.ServicerequestWS" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsd="http://www.w3.org/2001/XMLSchema" xsi="http://www.w3.org/2001/XMLSchema-instance"SOAP-ENV:Header/SOAP-ENV:Body SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"ns1:update_srsrNumber xsd="http://www.w3.org/2001/XMLSchema" xsi="http://www.w3.org/2001/XMLSchema-instance"542/srNumberstatus xsd="http://www.w3.org/2001/XMLSchema" xsi="http://www.w3.org/2001/XMLSchema-instance"Opn/statusnoteText xsd="http://www.w3.org/2001/XMLSchema" xsi="http://www.w3.org/2001/XMLSchema-instance"Service Request Number(628) Status Date(2005/03/08 10:19:55) Status(RAI)/noteText/ns1:update_sr/SOAP-ENV:Body/SOAP-ENV:Envelope
    /code

    We receive an error of the form

    org.w3c.dom.DOMException: NAMESPACE_ERR: An attempt is made to create or change an object in a way which is incorrect with regard to namespaces.
    at org.apache.xerces.dom.CoreDocumentImpl.checkDOMNSErr(CoreDocumentImpl.java:2128)
    at org.apache.xerces.dom.AttrNSImpl.setName(AttrNSImpl.java:149)
    at org.apache.xerces.dom.AttrNSImpl.init(AttrNSImpl.java:110)
    at org.apache.xerces.dom.CoreDocumentImpl.createAttributeNS(CoreDocumentImpl.java:1786)
    at com.sun.xml.messaging.saaj.soap.SOAPDocumentImpl.createAttributeNS(SOAPDocumentImpl.java:142)
    at org.apache.xerces.dom.ElementImpl.setAttributeNS(ElementImpl.java:660)
    at com.sun.xml.messaging.saaj.soap.impl.ElementImpl.addAttributeBare(ElementImpl.java:282)
    at com.sun.xml.messaging.saaj.soap.impl.ElementImpl.addAttribute(ElementImpl.java:266)

    I have added the appropriate namespace declaration and yet the error continues. I have also attempted to swap the version of xalan/xerces used for the latest one from Apache however you then get problems with the classloader because SAAJ has a hard coded path in looking for com/sun/org/apache/xerces/internal/dom/DocumentImpl

    Does anyone have any ideas - currently I am left with going back to JWSDP 1.1 which is not great or changing to use something else like Axis?

    All comments and suggestions are gratefully appreciated

    Cheers

    Chris

    DB:2.47:Namespace_Err Using Saaj 99

    Hi

    We use JWSDP 1.5 and Java 1.4.2.06 within a generic mechanism that generates out SOAP for calling external webservices. Since upgrading from JWSDP 1.1. we are unable to generate SOAP messages like the following
    code
    SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="sx3_app.ServicerequestWS" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsd="http://www.w3.org/2001/XMLSchema" xsi="http://www.w3.org/2001/XMLSchema-instance"SOAP-ENV:Header/SOAP-ENV:Body SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"ns1:update_srsrNumber xsd="http://www.w3.org/2001/XMLSchema" xsi="http://www.w3.org/2001/XMLSchema-instance"542/srNumberstatus xsd="http://www.w3.org/2001/XMLSchema" xsi="http://www.w3.org/2001/XMLSchema-instance"Opn/statusnoteText xsd="http://www.w3.org/2001/XMLSchema" xsi="http://www.w3.org/2001/XMLSchema-instance"Service Request Number(628) Status Date(2005/03/08 10:19:55) Status(RAI)/noteText/ns1:update_sr/SOAP-ENV:Body/SOAP-ENV:Envelope
    /code

    We receive an error of the form

    org.w3c.dom.DOMException: NAMESPACE_ERR: An attempt is made to create or change an object in a way which is incorrect with regard to namespaces.
    at org.apache.xerces.dom.CoreDocumentImpl.checkDOMNSErr(CoreDocumentImpl.java:2128)
    at org.apache.xerces.dom.AttrNSImpl.setName(AttrNSImpl.java:149)
    at org.apache.xerces.dom.AttrNSImpl.init(AttrNSImpl.java:110)
    at org.apache.xerces.dom.CoreDocumentImpl.createAttributeNS(CoreDocumentImpl.java:1786)
    at com.sun.xml.messaging.saaj.soap.SOAPDocumentImpl.createAttributeNS(SOAPDocumentImpl.java:142)
    at org.apache.xerces.dom.ElementImpl.setAttributeNS(ElementImpl.java:660)
    at com.sun.xml.messaging.saaj.soap.impl.ElementImpl.addAttributeBare(ElementImpl.java:282)
    at com.sun.xml.messaging.saaj.soap.impl.ElementImpl.addAttribute(ElementImpl.java:266)

    I have added the appropriate namespace declaration and yet the error continues. I have also attempted to swap the version of xalan/xerces used for the latest one from Apache however you then get problems with the classloader because SAAJ has a hard coded path in looking for com/sun/org/apache/xerces/internal/dom/DocumentImpl

    Does anyone have any ideas - currently I am left with going back to JWSDP 1.1 which is not great or changing to use something else like Axis?

    All comments and suggestions are gratefully appreciated

    Cheers

    Chris

  • RELEVANCY SCORE 2.47

    DB:2.47:Dynamic Proxy With Custom Types cm


    Am trying to use dynamic proxy that looks up the WSDL document to get information on the service.

    This appears to work OK when the request/return types have built-in/primitive serializers/deserializers. However, when trying to use custom objects, the server throws this exception -

    [ERROR] server - -unexpected element type:
    expected={http://www.w3.org/2001/XMLSchema}int,
    actual={http://schemas.xmlsoap.org/soap/encoding/}int unexpected element
    type: expected={http://www.w3.org/2001/XMLSchema}int,
    actual={http://schemas.xmlsoap.org/soap/encoding/}int

    It appears that there is an encoding type mismatch between the client/server serializers/deserializers. From the exception it does not appear that I need to register a serializer for my custom object which contains the "int" primitive type.

    Not certain if using DII would help our aim of a WSDL lookup. Also, are there any WSDL API implementations available to call on and set the appropriate encoding that the server expects ?

    Sincerely appreciate any inputs on this.

    Thanks in advance,
    Sharmin.

    DB:2.47:Dynamic Proxy With Custom Types cm

    this has been answered to you through an e-mailCould you please post the solution in the forum?

  • RELEVANCY SCORE 2.47

    DB:2.47:Getting The Value Of An Operand In Constructor ac


     
    In VisitMethodCall, When I try to get the operands and try to cast operand[0] into literal, I always end up with null, Could you please help me with that
     
    Literal literal = call.Operands[0] as Literal; // literal is always null
     
    I want to get the value of the string passed to the Regex constructor.
     
     
    Value of call.Operand[0] being:
     
    Microsoft.FxCop.Sdk.ClassNodeystem.String pattern}
        [Microsoft.FxCop.Sdk.Parameter]: {Microsoft.FxCop.Sdk.ClassNodeystem.String pattern}
        base {Microsoft.FxCop.Sdk.Node}: {Microsoft.FxCop.Sdk.ClassNodeystem.String pattern}
        ILOffset: 1
        Type: {Microsoft.FxCop.Sdk.ClassNodeystem.String}
        type: {Microsoft.FxCop.Sdk.ClassNodeystem.String}
     
    Thanks,
    Ajay
     
    Here is the rule code:
     
    public override void VisitMethodCall(MethodCall call)
    {
    MemberBinding mb = call.Callee as MemberBinding;
    if (mb == null)
    return;
    Method methd = mb.BoundMember as Method;
    if (methd == null)
    return;
    string[] fullName = methd.FullName.Split(new char[] { '(' });
    if (fullName[0] == System.Text.RegularExpressions.Regex.#ctor)
    {
    Expression expression = call.Operands[0] as Expression;
    Literal literal = expression as Literal;
    if (literal != null)
    {
    string pattern = literal.Value as string;
    }
    }
    }

    DB:2.47:Getting The Value Of An Operand In Constructor ac

    Hi Ajay,
     
    I don't think the VisitMethodCall method gets you the Regex constructor statement. So instead of using VisitMethodCall, you should use VisitConstruct and the code should be similar to the above to get you the Operands.
     
    Thanks,
    James 

  • RELEVANCY SCORE 2.47

    DB:2.47:Gzip And Soap1.1 z3


    Hi
    I have downloaded samples with WCF from this site:
    http://www.microsoft.com/en-us/download/details.aspx?id=21459
    There is very good example of GZIP implementation (\WCF\Extensibility\MessageEncoder\Compression).
    My problem is that it uses SOAP 1.2 and my requirement is to use SOAP 1.1.
    I have changed a little the code when inner
    TextMessageEncodingBindingElement
    is created
    and in the constructor of this class a pass
    MessageVersion.Soap11, System.Text.Encoding.UTF8.

    Unfortunately it did not help and when I get wsdl I still see SOAP1.2, here is part of the wsdl:

    wsdl:bindingname=BufferedHttpSampleServer_ISampleServertype=tns:ISampleServer
    wsp:PolicyReferenceURI=#BufferedHttpSampleServer_ISampleServer_policy/
    soap12:bindingtransport=http://schemas.xmlsoap.org/soap/http/
    wsdl:operationname=Echo
    soap12:operationsoapAction=http://tempuri.org/ISampleServer/Echostyle=document/
    wsdl:input
    soap12:bodyuse=literal/
    /wsdl:input
    wsdl:output
    soap12:bodyuse=literal/
    /wsdl:output
    /wsdl:operation
    wsdl:operationname=BigEcho
    soap12:operationsoapAction=http://tempuri.org/ISampleServer/BigEchostyle=document/
    wsdl:input
    soap12:bodyuse=literal/
    /wsdl:input
    wsdl:output
    soap12:bodyuse=literal/
    /wsdl:output
    /wsdl:operation
    /wsdl:binding

    I have founded out that when I use custom binding with default message encoding then SOAP 1.1 is used. When I use
    gzipMessageEncoding SOAP 1.2 is used even though I pass to the constructor:
    new TextMessageEncodingBindingElement(MessageVersion.Soap11, System.Text.Encoding.UTF8).

    customBinding

    binding
    name=myBasicHttpBinding

    textMessageEncoding
    messageVersion=Soap11
    /

    !--gzipMessageEncoding innerMessageEncoding=textMessageEncoding/--

    httpTransport /

    /binding

    /customBinding

    Any ideas how to achieve GZIP and SOAP 1.1?
    Regards

    kicaj

    DB:2.47:Gzip And Soap1.1 z3

    I have resolved this by using IWsdlExportExtension.kicaj

  • RELEVANCY SCORE 2.47

    DB:2.47:Usage Of Xsi:Nil With Literal Style fp



    Noel wroteDoes a null value in a complex type for doc/literal should have"xsi:nil='1'/" ?I thought xsi should be used only for encoded.

    DB:2.47:Usage Of Xsi:Nil With Literal Style fp


    from Jason
    The xsi prefix typically refers to schema-instance, which is literalvalid. What you are thinking of is xsi:null (as opposed to xsi:nil)which is a schema 1999 attribute. SOAP Encoding states that use ofxsi:null for null values is allowed, but it was never a requirement. Italso says custom attributes, and omitting the tag altogether is alsoallowed.So, to clarify, anything that is sent using the literal style must beschema 2001 valid, and thus must use xsi:nil to represent a null value.This, however, is only allowed if the schema has nillable=true on thecorresponding type.-Jasonand I left one thing out. An element can only be omitted if minOccurs=0, allnillable=true does is allow xsi:nil to be used.

  • RELEVANCY SCORE 2.47

    DB:2.47:Bad Wsdl Interpretation In Abap Proxy m7



    Hello,

    I have a problem with generated ABAP proxy. Generating from wsdl definition itself from given URL works fine, but when I call a method on this proxy class, the call results into bad SOAP request and consequent error.

    WSDL definition:

    ?xml version="1.0" encoding="UTF-8"?

    wsdl:definitions name="sapBridge"

    targetNamespace="http://www.your-company.com/sapBridge.wsdl"

    xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"

    xmlns:tns="http://www.your-company.com/sapBridge.wsdl"

    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"

    xmlns:xsd="http://www.w3.org/2001/XMLSchema"

    xmlns:xsd1="http://www.your-company.com/sapBridge.xsd1"

    wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"Created using Cape Clear Studio SOA Editor - http://www.capeclear.com/wsdl:documentation

    wsdl:types

    xsd:schema

    targetNamespace="http://www.your-company.com/sapBridge.xsd1"

    xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"

    xmlns:xsd="http://www.w3.org/2001/XMLSchema"

    xmlns:xsd1="http://www.your-company.com/sapBridge.xsd1"

    xsd:complexType name="echoRequestType"

    xsd:sequence

    xsd:element maxOccurs="1" minOccurs="1" name="arg1" type="xsd:string"/

    /xsd:sequence

    /xsd:complexType

    xsd:element name="echoRequest" type="xsd1:echoRequestType"/

    /xsd:schema

    /wsdl:types

    wsdl:message name="echoStringResponse"

    wsdl:part element="xsd1:echoRequest" name="echoStringOut"/

    /wsdl:message

    wsdl:message name="echoStringRequest"

    wsdl:part element="xsd1:echoRequest" name="echoStringIn"/

    /wsdl:message

    wsdl:portType name="sapBridgePortType"

    wsdl:operation name="echoString"

    wsdl:input message="tns:echoStringRequest"/

    wsdl:output message="tns:echoStringResponse"/

    /wsdl:operation

    /wsdl:portType

    wsdl:binding name="sapBridgeBinding" type="tns:sapBridgePortType"

    soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/

    wsdl:operation name="echoString"

    soap:operation soapAction="capeconnect:sapBridge:sapBridgePortType#echoString"/

    wsdl:input

    soap:body use="literal"/

    /wsdl:input

    wsdl:output

    soap:body use="literal"/

    /wsdl:output

    /wsdl:operation

    /wsdl:binding

    wsdl:service name="sapBridge"

    wsdl:port binding="tns:sapBridgeBinding" name="sapBridgePort"

    soap:address location="http://ws.myserver.com/soap/sapBridge"/

    /wsdl:port

    /wsdl:service

    /wsdl:definitions

    Resulting (bad) SOAP request which is sent to service is here:

    soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/"

    soap-env:Header

    n0:Trace xmlns:n0="http://www.sap.com/webas/630/soap/features/runtime/tracing/"

    TraceLevel xmlns="http://www.sap.com/webas/630/soap/features/runtime/tracing/"Full/TraceLevel

    /n0:Trace

    /soap-env:Header

    soap-env:Body

    nr1:echoRequest xmlns:nr1="http://www.your-company.com/sapBridge.xsd1"

    arg1/arg1

    /nr1:echoRequest

    /soap-env:Body

    /soap-env:Envelope

    Unfortunately I have not any idea, what could be the problem.

    Many thanks for any ideas.

    Milan

    DB:2.47:Bad Wsdl Interpretation In Abap Proxy m7


    Hello,

    I have a problem with generated ABAP proxy. Generating from wsdl definition itself from given URL works fine, but when I call a method on this proxy class, the call results into bad SOAP request and consequent error.

    WSDL definition:

    ?xml version="1.0" encoding="UTF-8"?

    wsdl:definitions name="sapBridge"

    targetNamespace="http://www.your-company.com/sapBridge.wsdl"

    xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"

    xmlns:tns="http://www.your-company.com/sapBridge.wsdl"

    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"

    xmlns:xsd="http://www.w3.org/2001/XMLSchema"

    xmlns:xsd1="http://www.your-company.com/sapBridge.xsd1"

    wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"Created using Cape Clear Studio SOA Editor - http://www.capeclear.com/wsdl:documentation

    wsdl:types

    xsd:schema

    targetNamespace="http://www.your-company.com/sapBridge.xsd1"

    xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"

    xmlns:xsd="http://www.w3.org/2001/XMLSchema"

    xmlns:xsd1="http://www.your-company.com/sapBridge.xsd1"

    xsd:complexType name="echoRequestType"

    xsd:sequence

    xsd:element maxOccurs="1" minOccurs="1" name="arg1" type="xsd:string"/

    /xsd:sequence

    /xsd:complexType

    xsd:element name="echoRequest" type="xsd1:echoRequestType"/

    /xsd:schema

    /wsdl:types

    wsdl:message name="echoStringResponse"

    wsdl:part element="xsd1:echoRequest" name="echoStringOut"/

    /wsdl:message

    wsdl:message name="echoStringRequest"

    wsdl:part element="xsd1:echoRequest" name="echoStringIn"/

    /wsdl:message

    wsdl:portType name="sapBridgePortType"

    wsdl:operation name="echoString"

    wsdl:input message="tns:echoStringRequest"/

    wsdl:output message="tns:echoStringResponse"/

    /wsdl:operation

    /wsdl:portType

    wsdl:binding name="sapBridgeBinding" type="tns:sapBridgePortType"

    soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/

    wsdl:operation name="echoString"

    soap:operation soapAction="capeconnect:sapBridge:sapBridgePortType#echoString"/

    wsdl:input

    soap:body use="literal"/

    /wsdl:input

    wsdl:output

    soap:body use="literal"/

    /wsdl:output

    /wsdl:operation

    /wsdl:binding

    wsdl:service name="sapBridge"

    wsdl:port binding="tns:sapBridgeBinding" name="sapBridgePort"

    soap:address location="http://ws.myserver.com/soap/sapBridge"/

    /wsdl:port

    /wsdl:service

    /wsdl:definitions

    Resulting (bad) SOAP request which is sent to service is here:

    soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/"

    soap-env:Header

    n0:Trace xmlns:n0="http://www.sap.com/webas/630/soap/features/runtime/tracing/"

    TraceLevel xmlns="http://www.sap.com/webas/630/soap/features/runtime/tracing/"Full/TraceLevel

    /n0:Trace

    /soap-env:Header

    soap-env:Body

    nr1:echoRequest xmlns:nr1="http://www.your-company.com/sapBridge.xsd1"

    arg1/arg1

    /nr1:echoRequest

    /soap-env:Body

    /soap-env:Envelope

    Unfortunately I have not any idea, what could be the problem.

    Many thanks for any ideas.

    Milan

  • RELEVANCY SCORE 2.46

    DB:2.46:Invoking Routing Service From Axis Dii Client pa


    Hi,

    Iam trying to invoke a routing service from an axis-1.4 dii client. I checked "Can be invoked from external service" for this routing service. The invocation returns with a fault -

    INFO: Mapping Exception to AxisFault
    AxisFault
    faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server
    faultString: java.lang.NullPointerException
    faultActor:
    faultDetail:
    stackTrace: AxisFault
    faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server
    faultString: java.lang.NullPointerException
    faultActor:
    faultDetail:

    java.lang.NullPointerException
    at org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:135)
    at org.apache.axis.encoding.DeserializationContextImpl.endElement(DeserializationContextImpl.java:942)
    at org.apache.xerces.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:569)

    Iam not able to identify the reason behind this.

    Please help.

    DB:2.46:Invoking Routing Service From Axis Dii Client pa

    Does it require WSIF to invoke a routing service ?

  • RELEVANCY SCORE 2.46

    DB:2.46:How To Send String Parameter To .Net Web Service Using Jax-Rpc Dii 8m


    This is my code below:------

    package dii;

    import javax.xml.rpc.Call;
    import javax.xml.rpc.Service;
    import javax.xml.rpc.JAXRPCException;
    import javax.xml.namespace.QName;
    import javax.xml.rpc.ServiceFactory;
    import javax.xml.rpc.ParameterMode;
    import javax.xml.soap.SOAPConstants;

    import java.net.URL;

    public class HelloClient {

    private static String qnameService = "Service1";
    private static String qnamePort = "Service1Soap";
    private static String qnameoperationName = "ViewQuestListByCategory";

    private static String BODY_NAMESPACE_VALUE =
    "http://gnr.patni.com/webservices/";
    private static String NS_XSD =
    "http://www.w3.org/2001/XMLSchema";
    private static String URI_ENCODING =
    "http://schemas.xmlsoap.org/soap/encoding/";

    private static final String wsdlURL ="http://pc-p4-281/UserVQlist/Service1.asmx?WSDL";

    public static void main(String[] args) {

    try {

    ServiceFactory factory = ServiceFactory.newInstance();

    Service service = factory.createService(new QName(qnameService));

    QName port = new QName(qnamePort);
    //call.setPortTypeName(new QName(qnamePort));

    //call.setOperationName(new QName(BODY_NAMESPACE_VALUE,qnameoperationName));

    QName operation = new QName(BODY_NAMESPACE_VALUE,qnameoperationName);

    Call call = service.createCall(port, operation);

    call.setTargetEndpointAddress("http://pc-p4-281/UserVQlist/Service1.asmx");

    call.setProperty(Call.SOAPACTION_USE_PROPERTY, new Boolean(true));
    call.setProperty(Call.SOAPACTION_URI_PROPERTY, BODY_NAMESPACE_VALUE + qnameoperationName);

    // use="literal" in WSDL
    call.setProperty(Call.ENCODINGSTYLE_URI_PROPERTY, "");
    // style="document" in WSDL
    call.setProperty(Call.OPERATION_STYLE_PROPERTY, "document");

    QName REQUEST_QNAME = new QName(NS_XSD, "ViewQuestListByCategorySoapIn");

    Class cls = Class.forName("java.lang.String");

    call.addParameter("category_id", REQUEST_QNAME, cls, ParameterMode.IN);

    QName RESPONSE_QNAME = new QName(NS_XSD, "ViewQuestListByCategorySoapOut");
    call.setReturnType(RESPONSE_QNAME, cls);

    String[] params = new String[]{"6C4139BA-EDA3-4FAD-9887-7882772907D3"};

    System.out.println("9");

    String result = (String)call.invoke(params);
    System.out.println("10");
    System.out.println(result);

    } catch (Exception ex) {
    ex.printStackTrace();
    }
    }
    }

    When I am passing a String parameter to .Net Web service which is also taking String parameter in its method error is generated "Argument is null" What I guess is that it is not taking my datatype.So how to pass String parameter.????

    Plz help its urgent! Thanx in advance.

  • RELEVANCY SCORE 2.46

    DB:2.46:Xsi And V Ray? 9s


    Is there any plans for Softimage to cover Vray XSI integration this year at thesiggraph 08? Perhaps as a collaborated thing with chaos group and maybe presentV ray used in XSI production and cover little bit of demo on that as well?

    DB:2.46:Xsi And V Ray? 9s

    its still being tested and developed... if you want to see it ask the chaosgroup guys at their booth. it might be still early to be using it in a production...

  • RELEVANCY SCORE 2.46

    DB:2.46:Document/Literal Messaging With Oas 9.0.4 xd


    please let me know if i have this right...

    my understanding is that if i want to do document/literal soap messaging to a wrapped pl/sql function with OAS 9.0.4 then i have to go rpc/endcoded and use a string for my xml document payload?

    any input would be most appreciated.

    thanks in advance.

    Message was edited by:
    user521233

    DB:2.46:Document/Literal Messaging With Oas 9.0.4 xd

    If you are new to Web Services, you should really consider using the latest version of the OAS stack. With 9.0.4, you should only work with RPC/Encoded and the basic data type supported out of the box.
    Using 10.1.3.2 (or any 10.1.3) is really where you want to start.

    This is just my personnal opinion, and I do understand that it's not always possible to move to the latest release. However, pushing back may be your best option.

    Best,
    -Eric

  • RELEVANCY SCORE 2.46

    DB:2.46:Dii Asynchronous Calls zm



    JAXRPC 1.1 states that the DII client model should support one-way invocations. According to the spec, a client thread shouldn't block waiting for the completion of the remote invocation. In the SOAP/HTTP case, the client should block until a HTTP response code has been received. After using async calls (CallImpl.invokeOneWay) for a while in JBossWS, I realised that the client thread is blocked until the remote invocation completes on the server side. Is this behaviour JAXRPC compliant?

    DB:2.46:Dii Asynchronous Calls zm


    I meant HTTP parsing, not XML parsing.-Jason

  • RELEVANCY SCORE 2.46

    DB:2.46:Dyn. Invocation Interface - Not As Dynamic As It Should Be? 9d


    Hello,

    In the JWSDP in chapter "Java API for XML-based RPC", section "A Dynamic Invocation Interface (DII) Client Example" I read the following: "With the dynamic invocation interface (DII), a client can call a remote procedure even if the signature of the remote procedure or the name of the service are unknown until runtime." Also "... a DII client can be used in a service broker that dynamically discovers services, configures the remote calls, and executes the calls."

    But when I study the example, I see the following:

    call.setOperationName(new QName(BODY_NAMESPACE_VALUE, "sayHello"));

    That means as a programmer I have to know the name of the remote procedures, in this case "sayHello". I thought it should be possible in this "dynamic" example to get a list of all available remote procedures the web service offers, so that the client is able to configure itself to invoke the remote procedures.

    My questions:
    1. Is this possible with DII?
    2. if not, is it possible in any other way?

    thanks for help,
    Matthias

    DB:2.46:Dyn. Invocation Interface - Not As Dynamic As It Should Be? 9d

    Dear Sir,

    regarding this msg. Have you already foudn the right way to develop a truely dynamic client? =)

    Thanks.

    Your reply and any forms of help will be appreciated. =)

  • RELEVANCY SCORE 2.46

    DB:2.46:Error Calling Com+ Webservice zf


    Hey guys,

    I am having problems to call COM+ webservices using Mediator.
    My composite needs to call some legacy Delphi DLL that are published in a Windows 2003 COM+ SOAP services.
    When I try to call the services using the HTTP Analyser tool, everything works fine. However, when I try to call it in my composite application using a Mediator component, I got the following exception:

    javax.xml.ws.soap.SOAPFaultException: **** System.Runtime.Serialization.SerializationException - Parse Error, no assembly associated with Xml key wsa Action.

    Have anybody faced problems like this to call COM+ SOAP services?

    Here is my COM+ SOAP WSDL:

    ?xml version="1.0" encoding="UTF-8" ?
    wsdl:definitions
    name="StringCon"
    targetNamespace="http://oracle.com/sca/soapservice/InternaliazacaoApp/StringCon/StringCon"
    xmlns:tns="http://oracle.com/sca/soapservice/InternaliazacaoApp/StringCon/StringCon"
    xmlns:inp1="http://xmlns.oracle.com/singleString"
    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
    xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
    wsdl:documentation
    abstractWSDLhttp://anvisa-soa-dev:8001/soa-infra/services/default/StringCon!1.0/StringCon.wsdl/abstractWSDL
    /wsdl:documentation
    wsdl:types
    xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xsd:import namespace="http://xmlns.oracle.com/singleString" schemaLocation="http://anvisa-soa-dev:8001/soa-infra/services/default/StringCon/StringCon?XSD=xsd/singleString.xsd"/
    /xsd:schema
    /wsdl:types
    wsdl:message name="requestMessage"
    wsdl:part name="input" element="inp1:singleString"/
    /wsdl:message
    wsdl:message name="replyMessage"
    wsdl:part name="output" element="inp1:singleString"/
    /wsdl:message
    wsdl:portType name="execute_ptt"
    wsdl:operation name="execute"
    wsdl:input message="tns:requestMessage"/
    wsdl:output message="tns:replyMessage"/
    /wsdl:operation
    /wsdl:portType
    wsdl:binding name="execute_pttBinding" type="tns:execute_ptt"
    soap:binding transport="http://schemas.xmlsoap.org/soap/http"/
    wsdl:operation name="execute"
    soap:operation style="document" soapAction="execute"/
    wsdl:input
    soap:body use="literal" namespace="http://oracle.com/sca/soapservice/InternaliazacaoApp/StringCon/StringCon"/
    /wsdl:input
    wsdl:output
    soap:body use="literal" namespace="http://oracle.com/sca/soapservice/InternaliazacaoApp/StringCon/StringCon"/
    /wsdl:output
    /wsdl:operation
    /wsdl:binding
    wsdl:service name="StringCon"
    wsdl:port name="execute_pt" binding="tns:execute_pttBinding"
    soap:address location="http://anvisa-soa-dev:8001/soa-infra/services/default/StringCon/StringCon"/
    /wsdl:port
    /wsdl:service
    /wsdl:definitions

    Edited by: 904488 on Dec 26, 2011 5:56 AM

    DB:2.46:Error Calling Com+ Webservice zf

    soa suite ws binding sends out wsa headers - that is what fails to be parsed on the .NET side ("Parse Error, no assembly associated with Xml key wsa Action.")

    there is a flag on the outbound ws binding properties (omit.wsa.headers) that let's you turn this off.

  • RELEVANCY SCORE 2.46

    DB:2.46:Error In Using The Rpc Wsdl Based Business Service az


    Hi,

    I am using OSB 11g. I have created a business service with one of the WSDL which supports rpc/literal style. I am trying to call this business service using the service callout.

    For the service callout if i use Configure SOAP Body option, i am getting the following error and unable to deploy to the server.
    *'The Configuration does not correspond to a SOAP RPC WSDL.The WSDL of the target service may have changed.'*

    But i am able to use the same option in sbconsole with out any problem. Is it an real issue with Eclipse IDE or a bug in the IDE? Please let me know if any insights into this issue.

    Thanks
    Siva

    DB:2.46:Error In Using The Rpc Wsdl Based Business Service az

    Hi Manoj,

    the error message is shown in the IDE at the design time itself and unable to deploy from IDE because of this error.
    I will checkout again on this as i am unable to reproduce this issue in IDE always.

    Thanks
    Siva

  • RELEVANCY SCORE 2.45

    DB:2.45:Is This Possible With Jboss Web Services? dp



    Hi I am busy with a systems integration project.I have he following problem. Calling a SOAP web service running in jboss returns a raw roap response from the web service that contain"soapenv" xml tags and xml attributes as well as xmlns and xsi attributes. This is a proper SOAP response.My problem is this. The 3rd party software (which i can't change) has the facility to call soap calls and make the XML available to that 3rd party application. However that application can't understand the returned SOAP tags and xml descriptive attributes received with the XML data after calling a SOAP web service running in JBoss I described above.Is there a way to exclude the soap headers and/or those extra descriptive tags in a JBoss SOAP web service response in a config file or somewhere else?What I basically want is the plain xml returned like this:Code:

    Response
    Field11/Field1
    Field22/Field2
    Field3abc/Field3
    /Response

    DB:2.45:Is This Possible With Jboss Web Services? dp


    Maybe you can apply a xslt to the soap message to turn it into what you need, using Apache Xalan.

  • RELEVANCY SCORE 2.45

    DB:2.45:Web Service Permission Denied ka



    Hallo,

    I am trying to write a webinterface for the Webservice of Virtualcenter, but i can't connect.

    The service runs correctly. i also can log me in with this login.html but if i try from another computer i just geht an permission denied.

    my code looks like this:

    ?php

    include('SOAP/Client.php');

    $soapclient = new SOAP_client('http://nbbntst8:8083'); //the adress..port 8083 is my non-SSL port

    $options = array('style' = 'document',

    'use' = 'literal');

    $auth = array('userName' = 'COMPANY\User',

    'password' = 'Userpassword'); //the User is admin

    $login = $soapclient-call('Login',$auth,$options); /should execute a login

    print_r($login);

    ?

    DB:2.45:Web Service Permission Denied ka


    Hallo,

    I am trying to write a webinterface for the Webservice of Virtualcenter, but i can't connect.

    The service runs correctly. i also can log me in with this login.html but if i try from another computer i just geht an permission denied.

    my code looks like this:

    ?php

    include('SOAP/Client.php');

    $soapclient = new SOAP_client('http://nbbntst8:8083'); //the adress..port 8083 is my non-SSL port

    $options = array('style' = 'document',

    'use' = 'literal');

    $auth = array('userName' = 'COMPANY\User',

    'password' = 'Userpassword'); //the User is admin

    $login = $soapclient-call('Login',$auth,$options); /should execute a login

    print_r($login);

    ?

  • RELEVANCY SCORE 2.45

    DB:2.45:Not Able To Invoke Document Style Service From Dii Client 3p


    I am not able to invoke document/literal service from DII client. It works fine for rpc/encoded service.

    Here is the code:
    System.setProperty("javax.xml.rpc.ServiceFactory",
    "weblogic.webservice.core.rpc.ServiceFactoryImpl");
    ServiceFactory sf = ServiceFactory.newInstance();
    QName serviceQname = new QName("http://batchrecord.webservices.sums.cfm.com", "CFMBatchRecordService");
    Service service = sf.createService( serviceQname);
    QName portQname = new QName("http://batchrecord.webservices.sums.cfm.com", "CFMBatchRecordServicePort");
    QName QNAME_TYPE_STRING = new QName(NS_XSD, "string");

    Call call = service.createCall(portQname);
    // call.setProperty("javax.xml.rpc.encodingstyle.namespace.uri", "");
    call.setProperty(Call.OPERATION_STYLE_PROPERTY, "document");
    call.setTargetEndpointAddress(endpoint);
    call.setProperty(Call.SOAPACTION_USE_PROPERTY, new Boolean(true));
    call.setProperty(Call.SOAPACTION_URI_PROPERTY, "");

    call.setReturnType(QNAME_TYPE_STRING);
    call.setOperationName(new QName("http://batchrecord.webservices.sums.cfm.com", "processBREditForAlerts"));
    call.addParameter("string", QNAME_TYPE_STRING, ParameterMode.IN);
    // call.addParameter("parameters", requestQname, String.class, ParameterMode.IN);

    String params[] = {
    "testtest"};
    String result = (String) call.invoke(new QName("http://batchrecord.webservices.sums.cfm.com"), params);
    System.out.println(result);

    DB:2.45:Not Able To Invoke Document Style Service From Dii Client 3p

    DII does work with basic doc/lit invocations, but once you start dealing with more complex structures, problems may occur.

  • RELEVANCY SCORE 2.45

    DB:2.45:Combining One-Way And Normal Operation-Members In A Service Using Pollingduplexbinding k7


    Hi all,
    I am trying to put together a simple chat-application using silverlight talking to a wcf service configured with PollingDuplexBinding. At this point, communicating with the service using polling-duplex methodology outlined in msdn is working fine. However,
    there are some methods which are straightforward and don't require two-way communication. But my attempts at calling these normal (not one-way) methods on the service-class from the silverlight application always end up throwing this exception:
    The remote server returned an error: NotFound
    The error occurs in the service-reference's reference.cs file, here:

    public System.Collections.ObjectModel.ObservableCollection EndGetRooms(System.IAsyncResult result) { object[] _args = new object[0]; System.Collections.ObjectModel.ObservableCollection _result = ((System.Collections.ObjectModel.ObservableCollection)(base.EndInvoke(GetRooms, _args, result))); return _result; }

    Now, I'm guessing that running the wcf service using the PollingDuplexServiceHostFactorysomehow changes the paths to the methods? Can anyone tell me if and how I can call normal methodsin this situation?
    The setup is almost one to one to what is outlined here: http://msdn.microsoft.com/en-us/library/cc645027%28VS.95%29.aspxand here: http://msdn.microsoft.com/en-us/library/dd470097%28VS.95%29.aspx

    I'll also throw in the wsdl if that helps anyone:
    wsdl:definitions name=ChatServicetargetNamespace=http://tempuri.org/xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/xmlns:wsu=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsdxmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/xmlns:wsam=http://www.w3.org/2007/05/addressing/metadataxmlns:tns=http://tempuri.org/xmlns:wsa=http://schemas.xmlsoap.org/ws/2004/08/addressingxmlns:wsp=http://schemas.xmlsoap.org/ws/2004/09/policyxmlns:i0=ChatServerxmlns:wsap=http://schemas.xmlsoap.org/ws/2004/08/addressing/policyxmlns:xsd=http://www.w3.org/2001/XMLSchemaxmlns:msc=http://schemas.microsoft.com/ws/2005/12/wsdl/contractxmlns:wsaw=http://www.w3.org/2006/05/addressing/wsdlxmlns:soap12=http://schemas.xmlsoap.org/wsdl/soap12/xmlns:wsa10=http://www.w3.org/2005/08/addressingxmlns:wsx=http://schemas.xmlsoap.org/ws/2004/09/mex wsdl:import namespace=ChatServer location=http://yoni-home/Chat.Server/ChatService.svc?wsdl=wsdl0 / wsdl:types / wsdl:binding name=CustomBinding_IChatServerService type=i0:IChatServerService soap:binding transport=http://schemas.xmlsoap.org/soap/http / wsdl:operation name=JoinRoom soap:operation soapAction=ChatServer/IChatServerService/JoinRoom style=document / wsdl:input soap:body use=literal / /wsdl:input wsdl:output soap:body use=literal / /wsdl:output /wsdl:operation wsdl:operation name=GetRooms soap:operation soapAction=ChatServer/IChatServerService/GetRooms style=document / wsdl:input soap:body use=literal / /wsdl:input wsdl:output soap:body use=literal / /wsdl:output /wsdl:operation wsdl:operation name=ReceiveClientsUpdate soap:operation soapAction=ChatServer/IChatServerService/ReceiveClientsUpdate style=document / wsdl:output soap:body use=literal / /wsdl:output /wsdl:operation wsdl:operation name=ReceiveMessageAdded soap:operation soapAction=ChatServer/IChatServerService/ReceiveMessageAdded style=document / wsdl:output soap:body use=literal / /wsdl:output /wsdl:operation /wsdl:binding wsdl:service name=ChatService wsdl:port name=CustomBinding_IChatServerService binding=tns:CustomBinding_IChatServerService soap:address location=http://yoni-home/Chat.Server/ChatService.svc / /wsdl:port /wsdl:service/wsdl:definitions

    DB:2.45:Combining One-Way And Normal Operation-Members In A Service Using Pollingduplexbinding k7

    Hi all,
    I am trying to put together a simple chat-application using silverlight talking to a wcf service configured with PollingDuplexBinding. At this point, communicating with the service using polling-duplex methodology outlined in msdn is working fine. However,
    there are some methods which are straightforward and don't require two-way communication. But my attempts at calling these normal (not one-way) methods on the service-class from the silverlight application always end up throwing this exception:
    The remote server returned an error: NotFound
    The error occurs in the service-reference's reference.cs file, here:

    public System.Collections.ObjectModel.ObservableCollection EndGetRooms(System.IAsyncResult result) { object[] _args = new object[0]; System.Collections.ObjectModel.ObservableCollection _result = ((System.Collections.ObjectModel.ObservableCollection)(base.EndInvoke(GetRooms, _args, result))); return _result; }

    Now, I'm guessing that running the wcf service using the PollingDuplexServiceHostFactorysomehow changes the paths to the methods? Can anyone tell me if and how I can call normal methodsin this situation?
    The setup is almost one to one to what is outlined here: http://msdn.microsoft.com/en-us/library/cc645027%28VS.95%29.aspxand here: http://msdn.microsoft.com/en-us/library/dd470097%28VS.95%29.aspx

    I'll also throw in the wsdl if that helps anyone:
    wsdl:definitions name=ChatServicetargetNamespace=http://tempuri.org/xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/xmlns:wsu=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsdxmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/xmlns:wsam=http://www.w3.org/2007/05/addressing/metadataxmlns:tns=http://tempuri.org/xmlns:wsa=http://schemas.xmlsoap.org/ws/2004/08/addressingxmlns:wsp=http://schemas.xmlsoap.org/ws/2004/09/policyxmlns:i0=ChatServerxmlns:wsap=http://schemas.xmlsoap.org/ws/2004/08/addressing/policyxmlns:xsd=http://www.w3.org/2001/XMLSchemaxmlns:msc=http://schemas.microsoft.com/ws/2005/12/wsdl/contractxmlns:wsaw=http://www.w3.org/2006/05/addressing/wsdlxmlns:soap12=http://schemas.xmlsoap.org/wsdl/soap12/xmlns:wsa10=http://www.w3.org/2005/08/addressingxmlns:wsx=http://schemas.xmlsoap.org/ws/2004/09/mex wsdl:import namespace=ChatServer location=http://yoni-home/Chat.Server/ChatService.svc?wsdl=wsdl0 / wsdl:types / wsdl:binding name=CustomBinding_IChatServerService type=i0:IChatServerService soap:binding transport=http://schemas.xmlsoap.org/soap/http / wsdl:operation name=JoinRoom soap:operation soapAction=ChatServer/IChatServerService/JoinRoom style=document / wsdl:input soap:body use=literal / /wsdl:input wsdl:output soap:body use=literal / /wsdl:output /wsdl:operation wsdl:operation name=GetRooms soap:operation soapAction=ChatServer/IChatServerService/GetRooms style=document / wsdl:input soap:body use=literal / /wsdl:input wsdl:output soap:body use=literal / /wsdl:output /wsdl:operation wsdl:operation name=ReceiveClientsUpdate soap:operation soapAction=ChatServer/IChatServerService/ReceiveClientsUpdate style=document / wsdl:output soap:body use=literal / /wsdl:output /wsdl:operation wsdl:operation name=ReceiveMessageAdded soap:operation soapAction=ChatServer/IChatServerService/ReceiveMessageAdded style=document / wsdl:output soap:body use=literal / /wsdl:output /wsdl:operation /wsdl:binding wsdl:service name=ChatService wsdl:port name=CustomBinding_IChatServerService binding=tns:CustomBinding_IChatServerService soap:address location=http://yoni-home/Chat.Server/ChatService.svc / /wsdl:port /wsdl:service/wsdl:definitions

  • RELEVANCY SCORE 2.44

    DB:2.44:Using Wsif To Call A Db Adapter ck


    Hi,

    environment: OESB, Win XP, JDev 10.1.3.4, 10gAS 10.1.3.4, Enterprise 10gR2 DB

    I've created a DB adapter for a PLSQL procedure that gets a single value from a single DB table. There are no IN parameters and it returns a single VARCHAR. I've successfully tested this adapter from the ESB console SOAP test client.

    I now want to call this DB adapter using WSIF from a local Java class in the same project. I've followed the instructions in Ch 9 (Using WSIF) of the 10gAS Advanced Web Services Developer Guide using the DII approach (i.e. not using the dynamic proxy) but I'm having trouble getting this working.

    My questions are:

    1. Is what I'm trying to do a valid approach? Should I be trying to access it via a Routing Service?

    2. What values should I be using to set up the WSIF service in the WSIFServiceFactory.getService() call?
    - currently I'm using the following:
    WSDL location = concrete WSDL URL (from the ESB Console - definition)
    Service Namespace and Name = Service from the concrete WSDL
    PortType Namespace and Name = null
    WSIF Port = soap port from the concrete WSDL

    With the above settings, I get:
    IllegalArgumentException: getSerializer requires a Java type or/and an XML type

    I've tried using the DB Adapter WSDL values but get
    WSIFException: No provider exists for the binding http://xmlns.oracle.com/pcbpel/wsdl/jca/

    Thanks
    DTY

    DB:2.44:Using Wsif To Call A Db Adapter ck

    Hi,

    environment: OESB, Win XP, JDev 10.1.3.4, 10gAS 10.1.3.4, Enterprise 10gR2 DB

    I've created a DB adapter for a PLSQL procedure that gets a single value from a single DB table. There are no IN parameters and it returns a single VARCHAR. I've successfully tested this adapter from the ESB console SOAP test client.

    I now want to call this DB adapter using WSIF from a local Java class in the same project. I've followed the instructions in Ch 9 (Using WSIF) of the 10gAS Advanced Web Services Developer Guide using the DII approach (i.e. not using the dynamic proxy) but I'm having trouble getting this working.

    My questions are:

    1. Is what I'm trying to do a valid approach? Should I be trying to access it via a Routing Service?

    2. What values should I be using to set up the WSIF service in the WSIFServiceFactory.getService() call?
    - currently I'm using the following:
    WSDL location = concrete WSDL URL (from the ESB Console - definition)
    Service Namespace and Name = Service from the concrete WSDL
    PortType Namespace and Name = null
    WSIF Port = soap port from the concrete WSDL

    With the above settings, I get:
    IllegalArgumentException: getSerializer requires a Java type or/and an XML type

    I've tried using the DB Adapter WSDL values but get
    WSIFException: No provider exists for the binding http://xmlns.oracle.com/pcbpel/wsdl/jca/

    Thanks
    DTY

  • RELEVANCY SCORE 2.44

    DB:2.44:Deserialization Error For Type Of String[] In Complextype zx


    I got following error while sending soap message to service using DII with or without asking WSDL file at runtime:
    [junit] java.rmi.RemoteException: JAXRPC.TIE.01: caught exception while hand
    ling request: deserialization error: unexpected element type: expected={Director
    y}ArrayOfstring, actual={http://schemas.xmlsoap.org/soap/encoding/}NMTOKENS

    Here is the soap messag part:

    ?xml version="1.0" encoding="UTF-8"?
    env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/" env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"env:Bodyans1:createGroup xmlns:ans1="Directory"BasicGroup_1 href="#ID1"//ans1:createGroupans1:BasicGroup xmlns:ans1="Directory" id="ID1"URN xsi:type="xsd:string"urn:group:directoryGroup1089142082746/URNgroupOwnerURNs xsi:type="enc:NMTOKENS"/groupOwnerURNspersonOwnerURNs xsi:type="enc:NMTOKENS"urn:person:Olga M Babkova/personOwnerURNs/ans1:BasicGroup/env:Body/env:Envelope

    Here is the related WSDL part:

    types
    schema xmlns="http://www.w3.org/2001/XMLSchema" xmlns:soap11-enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" targetNamespace="Directory"
    import namespace="http://schemas.xmlsoap.org/soap/encoding/"/
    complexType name="BasicGroup"
    sequence
    element name="URN" type="string"/
    element name="groupOwnerURNs" type="tns:ArrayOfstring"/
    element name="personOwnerURNs" type="tns:ArrayOfstring"//sequence/complexType
    complexType name="ArrayOfstring"
    complexContent
    restriction base="soap11-enc:Array"
    attribute ref="soap11-enc:arrayType" wsdl:arrayType="string[]"//restriction/complexContent/complexType

    Clearly based on WSDL, it's a type of ArrayOfstring, but soap message built by JWSDP on the client site using DII created a type of xsi:type="enc:NMTOKENS".

    Any idea why it's happening? I saw a similar post here with topic "using array in custom object", seems a common problem with array in JWSDP.

    So the only option left is to use static stub approach.

    Any workaround?

    DB:2.44:Deserialization Error For Type Of String[] In Complextype zx

    Hello-
    Please send me the wsdl file that you are using or
    a simplified wsdl file. Having the client program would help as well-
    Regards,
    Kathy

  • RELEVANCY SCORE 2.44

    DB:2.44:Wrong Soap Message j1


    Hi all,

    I am having problems when invoking a .NET web service using a DII client. My code is generating the following SOAP message:

    ?xml version="1.0" encoding="UTF-8"?
    env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/"
    env:Body
    ans1:ResolveIP xmlns:ans1="http://ws.cdyne.com/"
    IPaddressX.X.X.X/IPaddress
    licenseKey0/licenseKey
    /ans1:ResolveIP
    /env:Body
    /env:Envelopebut, it should generate the following:
    ?xml version="1.0" encoding="utf-8" standalone="yes"?
    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
    n1:ResolveIP xmlns:n1="http://ws.cdyne.com/"
    n1:IPaddress xmlns:n1="http://ws.cdyne.com/"X.X.X.X/n1:IPaddress
    n1:LicenseKey xmlns:n1="http://ws.cdyne.com/"0/n1:LicenseKey
    /n1:ResolveIP
    /env:Body
    /env:EnvelopeI am using JWSDP-1.6 1.6, JDK 1.5.0_03 and Ant 1.6.5 here you can find the client code and the build.xml files.

    project name="ejemplo6" default="build"
    !-- common properties --
    property file="../ejemplos.properties"/
    !-- propiedades concretas del proyecto --
    property name="nombre.ejemplo" value="ejemplo6" /
    property name="src.dir" value="${ejemplos.home.dir}/${nombre.ejemplo}/src" /
    property name="output.dir" value="${ejemplos.home.dir}/${nombre.ejemplo}/output" /
    property name="build.dir" value="${ejemplos.home.dir}/${nombre.ejemplo}/build" /
    property name="service.name" value="HelloWorldService" /
    property name="service.url" value="/${service.name}" /
    property name="client.package" value="tme.tds.ws.ej06" /
    property name="client.path" value="${src.dir}/tme/tds/ws/ej06" /
    property name="client.classes.dir" value="${output.dir}/client" /

    path id="project.class.path"
    fileset dir="/home/joseluis/jwsdp-1.6/jaxrpc/lib"
    include name="*.jar"/
    /fileset
    fileset dir="/home/joseluis/jwsdp-1.6/saaj/lib"
    include name="*.jar"/
    /fileset
    fileset dir="/home/joseluis/jwsdp-1.6/jwsdp-shared/lib"
    include name="*.jar"/
    /fileset
    pathelement path="${client.classes.dir}"/
    pathelement location="${java.home}/../lib/tools.jar"/
    /path

    target name="init"
    taskdef name="wscompile"
    classname="com.sun.xml.rpc.tools.ant.Wscompile"
    classpathref="project.class.path"/
    /target

    target name="build" depends="clean,setup,gen.types,compile.client" /

    target name="clean"
    delete dir="${output.dir}" /
    /target

    target name="setup"
    mkdir dir="${client.classes.dir}" /
    /target

    target name="gen.types" depends="init"
    wscompile gen="true"
    base="${client.classes.dir}"
    features="documentliteral,wsi,explicitcontext"
    verbose="true"
    keep="true"
    debug="true"
    config="${src.dir}/client-config.xml"
    classpath refid="project.class.path" /
    /wscompile
    /target

    target name="compile.client"
    javac
    destdir="${client.classes.dir}"
    source="1.4"
    target="1.4"
    debug="true"
    src path="${src.dir}" /
    include name="**/*.java"/
    classpath refid="project.class.path"/
    /javac
    /target

    target name="run"
    java classname="${client.package}.Main" fork="true"
    classpath refid="project.class.path" /
    arg line="http://ws.cdyne.com/ip2geo/ip2geo.asmx?wsdl" /
    /java
    /target

    /projectMain.java[/b]

    package tme.tds.ws.ej06;

    import java.net.Authenticator;
    import java.net.URL;
    import javax.xml.namespace.QName;
    import javax.xml.rpc.Call;
    import javax.xml.rpc.ParameterMode;
    import javax.xml.rpc.Service;
    import javax.xml.rpc.ServiceFactory;
    import javax.xml.rpc.encoding.DeserializerFactory;
    import javax.xml.rpc.encoding.SerializerFactory;
    import javax.xml.rpc.encoding.TypeMapping;
    import javax.xml.rpc.encoding.TypeMappingRegistry;
    import javax.xml.soap.SOAPConstants;
    import com.sun.xml.rpc.encoding.SingletonDeserializerFactory;
    import com.sun.xml.rpc.encoding.SingletonSerializerFactory;
    import tme.tds.security.SimpleAuthenticator;

    public class Main
    {
    public static void main(String[] args)
    {
    Authenticator.setDefault(new SimpleAuthenticator());
    try
    {
    new Main().invoke(args[0]);
    }
    catch (Exception e)
    {
    e.printStackTrace();
    }
    }

    private void invoke(String wsdlURL)
    throws Exception
    {
    //create service factory
    ServiceFactory factory = ServiceFactory.newInstance();

    //define qnames
    String targetNameSpace = "http://ws.cdyne.com/";
    QName serviceName = new QName(targetNameSpace, "IP2Geo");
    QName portName = new QName(targetNameSpace, "IP2GeoSoap");
    QName operationName = new QName(targetNameSpace, "ResolveIP");

    //create service
    Service service = factory.createService(new URL(wsdlURL), serviceName);

    TypeMappingRegistry registry = service.getTypeMappingRegistry();
    TypeMapping mapping = registry.createTypeMapping();

    ResolveIP_LiteralSerializer resolveIPSerializer =
    new ResolveIP_LiteralSerializer(
    new QName(targetNameSpace, "ResolveIP"),
    "literal"
    );
    mapping.register(
    tme.tds.ws.ej06.ResolveIP.class,
    new QName(targetNameSpace, "ResolveIP"),
    new SingletonSerializerFactory(resolveIPSerializer),
    new SingletonDeserializerFactory(resolveIPSerializer)
    );

    IPInformation_LiteralSerializer ipInfoSerializer =
    new IPInformation_LiteralSerializer(
    new QName(targetNameSpace, "IPInformation"),
    "literal"
    );
    mapping.register(tme.tds.ws.ej06.IPInformation.class,
    new QName(targetNameSpace, "IPInformation"),
    new SingletonSerializerFactory(ipInfoSerializer),
    new SingletonDeserializerFactory(ipInfoSerializer)
    );

    ResolveIPResponse_LiteralSerializer resolveIPResponseSerializer =
    new ResolveIPResponse_LiteralSerializer(
    new QName(targetNameSpace, "ResolveIPResponse"),
    "literal"
    );
    mapping.register(
    tme.tds.ws.ej06.ResolveIPResponse.class,
    new QName(targetNameSpace, "ResolveIPResponse"),
    new SingletonSerializerFactory(resolveIPResponseSerializer),
    new SingletonDeserializerFactory(resolveIPResponseSerializer)
    );

    //create call
    Call call = service.createCall(portName, operationName);
    call.setTargetEndpointAddress("http://ws.cdyne.com/ip2geo/ip2geo.asmx");
    call.setProperty(Call.SOAPACTION_USE_PROPERTY,
    new Boolean(true));
    String soapAction = targetNameSpace + "ResolveIP";
    call.setProperty(Call.SOAPACTION_URI_PROPERTY, soapAction);

    ResolveIP resolveIP = new ResolveIP("X.X.X.X", "0");
    System.out.println(resolveIP.toString());
    ResolveIPResponse resolveIPResponse =
    (ResolveIPResponse) call.invoke(new Object[]{resolveIP});
    IPInformation ipInfo = resolveIPResponse.getResolveIPResult();
    System.out.println(ipInfo.toString());
    }
    }I am using wscompile for generating the complex types, serializers, deserializers, etc with the options you can see in the script above.

    As you can see the only difference is that the code is not generating the correct namespace for the parameters. I do not know what I am doing wrong or missing.

    Just for your info: I have create a successful client using BEA WebLogic SOAP runtime and the autotype tool (something similar to wscompile), but when trying to do the equivalent with the JWSDP-1.6 does not work.

    Could someone help me with this? Thanks in advance.

    DB:2.44:Wrong Soap Message j1

    Sorry, I forgot to post the error message I get running the client I previously posted:

    tme.tds.ws.ej06.ResolveIP@14db0e3
    java.rmi.RemoteException: Server was unable to process request. -- Object reference not set to an instance of an object.
    at com.sun.xml.rpc.client.dii.BasicCall.invoke(BasicCall.java:507)
    at tme.tds.ws.ej06.Main.invoke(Main.java:112)
    at tme.tds.ws.ej06.Main.main(Main.java:39)

  • RELEVANCY SCORE 2.44

    DB:2.44:Invoking A Web Service With Multi Document Wsdl sx


    Hi,

    I'm trying to call a web service from BPEL using the partner link button. The WSDL I have is in two parts, the first document includes the endpoint and a wsdl:import statement which points to the second document containing types and definitions. I can create a client to the service using JDeveloper but BPEL doesn't seem to register the WSDL as valid.

    I have included the wsdls below for information. I would appreciate any help or suggestions.

    Thanks in advance

    John

    Document One:

    ?xml version="1.0" encoding="utf-8"?

    !-- Generated by WSDLDefinitionsParser --wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" name="RADCalcWSWsd" targetNamespace="urn:RADCalcWSWsd" xmlns:bns0="urn:RADCalcWSWsd/Config1/rpc" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
    wsdl:documentationRAD Calculator Service description./wsdl:documentation
    wsdl:import location="./bindings/Config1_rpc.wsdl" namespace="urn:RADCalcWSWsd/Config1/rpc"/
    wsdl:service name="RADCalcWS"
    wsdl:port name="Config1Port_Rpc" binding="bns0:Config1Binding"
    soap:address location="http://ermprot1:50000/RADCalcWS/Config1?style=rpc"/
    /wsdl:port
    /wsdl:service
    /wsdl:definitions

    Document Two

    ?xml version="1.0" encoding="utf-8"?

    !-- Generated by WSDLDefinitionsParser --wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" targetNamespace="urn:RADCalcWSWsd/Config1/rpc" xmlns:prt0="urn:RADCalcWSWsd/RADCalcWSVi/rpc" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
    wsdl:import location="../porttypes/Config1_RADCalcWSVi_rpc.wsdl" namespace="urn:RADCalcWSWsd/RADCalcWSVi/rpc"/
    wsdl:binding name="Config1Binding" type="prt0:RADCalcWSVi_Rpc"
    soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="rpc"/
    wsdl:operation name="add"
    soap:operation soapAction=""/
    wsdl:input
    soap:body use="literal" namespace="urn:RADCalcWSVi" parts="f1 f2 "/
    /wsdl:input
    wsdl:output
    soap:body use="literal" namespace="urn:RADCalcWSVi"/
    /wsdl:output
    /wsdl:operation
    wsdl:operation name="divide"
    soap:operation soapAction=""/
    wsdl:input
    soap:body use="literal" namespace="urn:RADCalcWSVi" parts="f1 f2 "/
    /wsdl:input
    wsdl:output
    soap:body use="literal" namespace="urn:RADCalcWSVi"/
    /wsdl:output
    /wsdl:operation
    wsdl:operation name="getDateTime"
    soap:operation soapAction=""/
    wsdl:input
    soap:body use="literal" namespace="urn:RADCalcWSVi"/
    /wsdl:input
    wsdl:output
    soap:body use="literal" namespace="urn:RADCalcWSVi"/
    /wsdl:output
    /wsdl:operation
    wsdl:operation name="multiply"
    soap:operation soapAction=""/
    wsdl:input
    soap:body use="literal" namespace="urn:RADCalcWSVi" parts="f1 f2 "/
    /wsdl:input
    wsdl:output
    soap:body use="literal" namespace="urn:RADCalcWSVi"/
    /wsdl:output
    /wsdl:operation
    wsdl:operation name="subtract"
    soap:operation soapAction=""/
    wsdl:input
    soap:body use="literal" namespace="urn:RADCalcWSVi" parts="f1 f2 "/
    /wsdl:input
    wsdl:output
    soap:body use="literal" namespace="urn:RADCalcWSVi"/
    /wsdl:output
    /wsdl:operation
    wsdl:operation name="test"
    soap:operation soapAction=""/
    wsdl:input
    soap:body use="literal" namespace="urn:RADCalcWSVi"/
    /wsdl:input
    wsdl:output
    soap:body use="literal" namespace="urn:RADCalcWSVi"/
    /wsdl:output
    /wsdl:operation
    /wsdl:binding
    /wsdl:definitions

    DB:2.44:Invoking A Web Service With Multi Document Wsdl sx

    As I see it you can't merge the wsdls since they are all in different namespaces. However I supppose if you did merge them, and fixed the namespaces, it would prove it's a recursion problem - you just wouldn't be able to call it - since the namespaces are incorrect. :-( Chicken and the Egg.

  • RELEVANCY SCORE 2.43

    DB:2.43:Jsr 181-Document Style-Dii Not Working p3



    Hello,i have deployed a web service to a JBOSS 4.0.4 GA server. The web service is really simple. It provides a method that returns a string. Now I try to call this web service with the dynamic invocation interface. But this does not work. The client comes up with the problem : javax.xml.rpc.JAXRPCException: Cannot find child element: result. I checked the SOAP message and saw that the result element contains a prefix of a namespace. Maybe this is the problem. But I can not find any method in the Call interface to set a namespace for a result.What is going wrong?Thanks in advance.Best regardsAndreas

    DB:2.43:Jsr 181-Document Style-Dii Not Working p3


    HiI had exactly same problem, although with Jboss-4.0.5 GA version. It seems Jboss -Jars issue. I simply pointed the client JARs to Jboss-4.0.2 and everything works fine.Hope this helps.Ram Pathak

  • RELEVANCY SCORE 2.43

    DB:2.43:External Soap Web Service Api Call Without Wsdl From Vco Workflow jk



    Hi All,

    is it possible to call SOAP web services without using WSDL and vCO SOAP plug-in ??

    I want to consume third party SOAP webservices without using SOAP plug-in, any one know how to do this, please share with me.

    Thanks in advance.

    DB:2.43:External Soap Web Service Api Call Without Wsdl From Vco Workflow jk


    There are a few other ways to "work around" using the SOAP plug-in:
    Local "command" - The "command" object could be used to execute curl locally to make the necessary SOAP calls. This article (How to run a Perl Script from a vCenter Orchestrator Workflow ) walks you through the steps necessary to execute a local command on a vCO ApplianceUse the Guest Operations workflows to have another system call curl, or whatever other command line utility, to make the necessary SOAP calls (Use this package as a starting point if you decide to go this route: Guest script manager package)Use the PowerShell plug-in to have PowerShell execute the SOAP calls
    In any case, you will have some parsing to deal with. Good luck!

  • RELEVANCY SCORE 2.43

    DB:2.43:Sap Xsi With Ups Carrier c7



    Hi,

    We have a meeting with UPS technical team and they would like a list of clients where SAP XSI with UPS is working or in process of implementation so their technical team can internally contact with UPS to understand what needs to be done from XSI implementation point. Let me know If you just want to send an email directly to me.

    Also, I have another question open on SAP XSI where I would like to understand in detail how XSI can be implemented in detail and what is the relevance of UPS worldship if we implement SAP XSI.

    Thanks.

    Naren Ginagam

    DB:2.43:Sap Xsi With Ups Carrier c7


    Thanks for the link. It a good presentation but in this cases it uses a new 3rd party tool called CONNECTSHIP and there are more customization done for CONNECTSHIP rather than using SAP XSI completely. I think what is done is CONNECTSHIP is implemented and it uses SAP XSI. There are new transactions created in SAP instance to process the labels. I have seen similar 3rd party solution called ECS provided by PROCESSWEAVER. Again 3rd party tool but time frame for implemenation is shorter.

    Infact we had considered CONNECTSHIP option before but considering timeframe of implementation and cost we moved to other options. I don't thing currently SAP XSI is used by itself at any client without any 3rd party tool.

  • RELEVANCY SCORE 2.43

    DB:2.43:Mudbox Xsi zz


    is anyone familiar with a good mudbox xsi workflow?i'd love to know some suggestions or screenshots of a good mudbox export settings xsi rendertree setup if possible.thanks in advance

    DB:2.43:Mudbox Xsi zz

    here are some tips from baroody...www.mudbox3d.com/forums/showthread.php?t=2408



    ----------------------------------------------------------------------http://www.linkedin.com/pub/christoph-schaedl/6/558/73b

  • RELEVANCY SCORE 2.43

    DB:2.43:Need Dii Invocation With Complex Type Sample 37


    Hi there,

    Could anyone provide me a CLIENT sample with DII invocation with complex type. Or you could point me to a sample out in the WEB.

    Thanks!!
    Garrick

    DB:2.43:Need Dii Invocation With Complex Type Sample 37

    Hi Samratbarve,

    Here is a sample code to invoke a xmethod web service with simple type:

    import javax.xml.namespace.QName;
    import javax.xml.rpc.Call;
    import javax.xml.rpc.Service;

    public class TemperatureService
    {
    public static void main(String[] args)
    {
    try
    {
    String endpoint = "http://services.xmethods.net:80/soap/servlet/rpcrouter";
    String namespaceURI = "urn:xmethods-Temperature";
    Service service = (Service) Class.forName("org.apache.axis.client.Service").newInstance();

    Call call = (Call) service.createCall();
    call.setTargetEndpointAddress(endpoint);
    call.setOperationName(new QName(namespaceURI, "getTemp"));

    Object [] arguments = new Object[1];
    arguments[0] = "90026";

    Float degree = (Float) call.invoke(arguments);
    System.out.println(degree);
    }catch(Exception ex)
    {
    ex.printStackTrace();
    }
    }
    }

  • RELEVANCY SCORE 2.43

    DB:2.43:Wsdeploy Ingores "Literal" Setting In Wsdl c9


    Can anyone tell me why the wsdeploy tool ingores the "literal" setting in the wsdl file, and replace it with "encoded" in the cooked war? I want the wsdl to be WS-I conformed.

    Thanks.

    original wsdl file,

    binding name="ProviderServiceBinding" type="tns:ProviderService"
    soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="rpc"/
    operation name="getProviderById"
    soap:operation soapAction=""/
    input
    soap:body use="literal" namespace="http://www.xxx.com/wsdl"//input
    output
    soap:body use="literal" namespace="http://www.xxx.com/wsdl"/
    /output
    /operation
    /binding

    cooked wsdl,

    binding name="ProviderServiceBinding" type="tns:ProviderService"
    soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="rpc"/
    operation name="getProviderById"
    soap:operation soapAction=""/
    input
    soap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" namespace="http://www.xxx.com/wsdl/ProviderWebServices"//input
    output
    soap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" namespace="http://www.xxx.com/wsdl/ProviderWebServices"//output/operation/binding

    DB:2.43:Wsdeploy Ingores "Literal" Setting In Wsdl c9

    Can anyone tell me why the wsdeploy tool ingores the "literal" setting in the wsdl file, and replace it with "encoded" in the cooked war? I want the wsdl to be WS-I conformed.

    Thanks.

    original wsdl file,

    binding name="ProviderServiceBinding" type="tns:ProviderService"
    soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="rpc"/
    operation name="getProviderById"
    soap:operation soapAction=""/
    input
    soap:body use="literal" namespace="http://www.xxx.com/wsdl"//input
    output
    soap:body use="literal" namespace="http://www.xxx.com/wsdl"/
    /output
    /operation
    /binding

    cooked wsdl,

    binding name="ProviderServiceBinding" type="tns:ProviderService"
    soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="rpc"/
    operation name="getProviderById"
    soap:operation soapAction=""/
    input
    soap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" namespace="http://www.xxx.com/wsdl/ProviderWebServices"//input
    output
    soap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" namespace="http://www.xxx.com/wsdl/ProviderWebServices"//output/operation/binding

  • RELEVANCY SCORE 2.43

    DB:2.43:Xsi - Parcel Tracking m7



    Hi All

    We are trying to implement SAP's XSI - functionality for tracking the inbound shipments.

    Is SAP still suporting XSI (Express delivery Company)..We are in ECC 6.0.

    which carriers support SAP's XSI functionality..can we integrate that with DHL, fedex, UPS or any other carriers.

    Can I get any technical documentation from these carriers?

    Please provide any information you know regarding XSI

    Appreciate your help

    thanks

    Vijay

    DB:2.43:Xsi - Parcel Tracking m7


    Hi All

    We are trying to implement SAP's XSI - functionality for tracking the inbound shipments.

    Is SAP still suporting XSI (Express delivery Company)..We are in ECC 6.0.

    which carriers support SAP's XSI functionality..can we integrate that with DHL, fedex, UPS or any other carriers.

    Can I get any technical documentation from these carriers?

    Please provide any information you know regarding XSI

    Appreciate your help

    thanks

    Vijay

  • RELEVANCY SCORE 2.43

    DB:2.43:Using Dii In Jax-Rpc 1p


    I've been trying to connect (unsuccessfully so far) to a webservice using DII in JAX-RPC. Was able to connect to the said webservice successfully using static stubs. But our requirement is for dynamic invocation. Sorry if a topic like this has been posted already. I did search the forums but couldn't find the answer to my problem.

    The WSDL for the web service is as follows:

    ?xml version="1.0" encoding="utf-8"?
    definitions 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://secure.yehey.com/2003/01/PayPlus" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" targetNamespace="http://secure.yehey.com/2003/01/PayPlus" xmlns="http://schemas.xmlsoap.org/wsdl/"
    types
    s:schema elementFormDefault="qualified" targetNamespace="http://secure.yehey.com/2003/01/PayPlus"
    s:element name="Process"
    s:complexType
    s:sequence
    s:element minOccurs="0" maxOccurs="1" name="inpData" type="s:string" /
    /s:sequence
    /s:complexType
    /s:element
    s:element name="ProcessResponse"
    s:complexType
    s:sequence
    s:element minOccurs="0" maxOccurs="1" name="ProcessResult" type="s:string" /
    /s:sequence
    /s:complexType
    /s:element
    s:element name="GetStatus"
    s:complexType
    s:sequence
    s:element minOccurs="0" maxOccurs="1" name="inxml" type="s:string" /
    /s:sequence
    /s:complexType
    /s:element
    s:element name="GetStatusResponse"
    s:complexType
    s:sequence
    s:element minOccurs="0" maxOccurs="1" name="GetStatusResult" type="s:string" /
    /s:sequence
    /s:complexType
    /s:element
    s:element name="GetRedirectURL"
    s:complexType
    s:sequence
    s:element minOccurs="0" maxOccurs="1" name="inpURL" type="s:string" /
    /s:sequence
    /s:complexType
    /s:element
    s:element name="GetRedirectURLResponse"
    s:complexType
    s:sequence
    s:element minOccurs="0" maxOccurs="1" name="GetRedirectURLResult" type="s:string" /
    /s:sequence
    /s:complexType
    /s:element
    s:element name="string" nillable="true" type="s:string" /
    /s:schema
    /types
    message name="ProcessSoapIn"
    part name="parameters" element="s0:Process" /
    /message
    message name="ProcessSoapOut"
    part name="parameters" element="s0:ProcessResponse" /
    /message
    message name="GetStatusSoapIn"
    part name="parameters" element="s0:GetStatus" /
    /message
    message name="GetStatusSoapOut"
    part name="parameters" element="s0:GetStatusResponse" /
    /message
    message name="GetRedirectURLSoapIn"
    part name="parameters" element="s0:GetRedirectURL" /
    /message
    message name="GetRedirectURLSoapOut"
    part name="parameters" element="s0:GetRedirectURLResponse" /
    /message
    message name="ProcessHttpGetIn"
    part name="inpData" type="s:string" /
    /message
    message name="ProcessHttpGetOut"
    part name="Body" element="s0:string" /
    /message
    message name="GetStatusHttpGetIn"
    part name="inxml" type="s:string" /
    /message
    message name="GetStatusHttpGetOut"
    part name="Body" element="s0:string" /
    /message
    message name="GetRedirectURLHttpGetIn"
    part name="inpURL" type="s:string" /
    /message
    message name="GetRedirectURLHttpGetOut"
    part name="Body" element="s0:string" /
    /message
    message name="ProcessHttpPostIn"
    part name="inpData" type="s:string" /
    /message
    message name="ProcessHttpPostOut"
    part name="Body" element="s0:string" /
    /message
    message name="GetStatusHttpPostIn"
    part name="inxml" type="s:string" /
    /message
    message name="GetStatusHttpPostOut"
    part name="Body" element="s0:string" /
    /message
    message name="GetRedirectURLHttpPostIn"
    part name="inpURL" type="s:string" /
    /message
    message name="GetRedirectURLHttpPostOut"
    part name="Body" element="s0:string" /
    /message
    portType name="PayplusSoap"
    operation name="Process"
    input message="s0:ProcessSoapIn" /
    output message="s0:ProcessSoapOut" /
    /operation
    operation name="GetStatus"
    input message="s0:GetStatusSoapIn" /
    output message="s0:GetStatusSoapOut" /
    /operation
    operation name="GetRedirectURL"
    input message="s0:GetRedirectURLSoapIn" /
    output message="s0:GetRedirectURLSoapOut" /
    /operation
    /portType
    portType name="PayplusHttpGet"
    operation name="Process"
    input message="s0:ProcessHttpGetIn" /
    output message="s0:ProcessHttpGetOut" /
    /operation
    operation name="GetStatus"
    input message="s0:GetStatusHttpGetIn" /
    output message="s0:GetStatusHttpGetOut" /
    /operation
    operation name="GetRedirectURL"
    input message="s0:GetRedirectURLHttpGetIn" /
    output message="s0:GetRedirectURLHttpGetOut" /
    /operation
    /portType
    portType name="PayplusHttpPost"
    operation name="Process"
    input message="s0:ProcessHttpPostIn" /
    output message="s0:ProcessHttpPostOut" /
    /operation
    operation name="GetStatus"
    input message="s0:GetStatusHttpPostIn" /
    output message="s0:GetStatusHttpPostOut" /
    /operation
    operation name="GetRedirectURL"
    input message="s0:GetRedirectURLHttpPostIn" /
    output message="s0:GetRedirectURLHttpPostOut" /
    /operation
    /portType
    binding name="PayplusSoap" type="s0:PayplusSoap"
    soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" /
    operation name="Process"
    soap:operation soapAction="http://secure.yehey.com/2003/01/PayPlus/Process" style="document" /
    input
    soap:body use="literal" /
    /input
    output
    soap:body use="literal" /
    /output
    /operation
    operation name="GetStatus"
    soap:operation soapAction="http://secure.yehey.com/2003/01/PayPlus/GetStatus" style="document" /
    input
    soap:body use="literal" /
    /input
    output
    soap:body use="literal" /
    /output
    /operation
    operation name="GetRedirectURL"
    soap:operation soapAction="http://secure.yehey.com/2003/01/PayPlus/GetRedirectURL" style="document" /
    input
    soap:body use="literal" /
    /input
    output
    soap:body use="literal" /
    /output
    /operation
    /binding
    binding name="PayplusHttpGet" type="s0:PayplusHttpGet"
    http:binding verb="GET" /
    operation name="Process"
    http:operation location="/Process" /
    input
    http:urlEncoded /
    /input
    output
    mime:mimeXml part="Body" /
    /output
    /operation
    operation name="GetStatus"
    http:operation location="/GetStatus" /
    input
    http:urlEncoded /
    /input
    output
    mime:mimeXml part="Body" /
    /output
    /operation
    operation name="GetRedirectURL"
    http:operation location="/GetRedirectURL" /
    input
    http:urlEncoded /
    /input
    output
    mime:mimeXml part="Body" /
    /output
    /operation
    /binding
    binding name="PayplusHttpPost" type="s0:PayplusHttpPost"
    http:binding verb="POST" /
    operation name="Process"
    http:operation location="/Process" /
    input
    mime:content type="application/x-www-form-urlencoded" /
    /input
    output
    mime:mimeXml part="Body" /
    /output
    /operation
    operation name="GetStatus"
    http:operation location="/GetStatus" /
    input
    mime:content type="application/x-www-form-urlencoded" /
    /input
    output
    mime:mimeXml part="Body" /
    /output
    /operation
    operation name="GetRedirectURL"
    http:operation location="/GetRedirectURL" /
    input
    mime:content type="application/x-www-form-urlencoded" /
    /input
    output
    mime:mimeXml part="Body" /
    /output
    /operation
    /binding
    service name="Payplus"
    port name="PayplusSoap" binding="s0:PayplusSoap"
    soap:address location="https://secured.teamyehey.com/payplus/services/payplus.asmx" /
    /port
    port name="PayplusHttpGet" binding="s0:PayplusHttpGet"
    http:address location="https://secured.teamyehey.com/payplus/services/payplus.asmx" /
    /port
    port name="PayplusHttpPost" binding="s0:PayplusHttpPost"
    http:address location="https://secured.teamyehey.com/payplus/services/payplus.asmx" /
    /port
    /service
    /definitions

    My code to access the above webservice (for Process method) is as follows (which is almost an exact copy from the sample code in JWSDP tutorial) :

    String qnameService = "Payplus";
    String qnamePort = "PayplusSoap";
    String BODY_NAMESPACE_VALUE = "http://secure.yehey.com/2003/01/PayPlus";
    String ENCODING_STYLE_PROPERTY = "javax.xml.rpc.encodingstyle.namespace.uri";
    String NS_XSD = "http://www.w3.org/2001/XMLSchema";
    String URI_ENCODING = "http://schemas.xmlsoap.org/soap/encoding/";

    ServiceFactory factory = ServiceFactory.newInstance();
    Service service = factory.createService(new QName(qnameService));

    QName port = new QName(qnamePort);

    Call call = service.createCall(port);
    call.setTargetEndpointAddress(urlstring);

    call.setProperty(Call.SOAPACTION_USE_PROPERTY, new Boolean(true));
    call.setProperty(Call.SOAPACTION_URI_PROPERTY, "http://secure.yehey.com/2003/01/PayPlus/Process");
    call.setProperty(ENCODING_STYLE_PROPERTY, URI_ENCODING);
    QName QNAME_TYPE_STRING = new QName(NS_XSD, "string");
    call.setReturnType(QNAME_TYPE_STRING);

    call.setOperationName(new QName(BODY_NAMESPACE_VALUE, "Process"));
    call.addParameter("inpData", QNAME_TYPE_STRING, ParameterMode.IN);
    String[] params = { getProcessString() }; // getProcessString here returns the parameter required

    String result = (String)call.invoke(params);
    System.out.println(result);

    The error that I keep on getting is this:

    java.rmi.RemoteException: System.Web.Services.Protocols.SoapException: Server was unable to process request. --- System.ArgumentNullException: Value cannot be null.
    Parameter name: s
    at System.IO.StringReader..ctor(String s)
    at Payplus.Payplus.Process(String inpData)

    Any help would be greatly appreciated. Thanks!

    DB:2.43:Using Dii In Jax-Rpc 1p

    Are you using the JAXRPC implementation from java.sun.com
    for your client invocations? IThis may be an implementation problem
    and if you are not using the sun implementation, then I can not explain
    the exception-

    kathy

  • RELEVANCY SCORE 2.43

    DB:2.43:Bug: Detailfragmentdeserializeer Does Not Deserialize Null Elements. c3


    I'm attempting to use a DII web service client to place a call to a WCF web service. The call runs successfully when there are no exceptions returned by the WCF web service. However, the DII client throws a DeserializeException when the WCF service sends back a SOAP Fault.

    The invoke method on the OracleCall class does not successfully return the exception, because it goes down when the SOAP Fault is being deserialized by the DetailFragmentDeserializer class. I'm getting back an "unexpected null" error and the stack trace indicates it occurred in the following location:

    oracle.j2ee.ws.common.encoding.literal.DetailFragmentDeserializer.deserializeElement(DetailFragmentDeserializer.java:150)

    I have searched other forums and it appears that Sun had identified this as a bug and removed the logic that throws a DeserializeException when Element is null in the SOAP Message.

    Reference the following links:

    http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4974593

    http://www.koders.com/java/fid98924B069BCEBB7E3DA5F57151BDE34D0A963C8B.aspx

    I think there still may be a bug in the DetailFragmentDeserializer class implemenation in the Oracle wsclient.jar library. Other implementations are able to successfully deserialize the SOAP Fault coming from my web service and the SOAP Fault message appears to comply with W3C specifications.

    Am I misinterpreting my results?

    Thanks

    DB:2.43:Bug: Detailfragmentdeserializeer Does Not Deserialize Null Elements. c3

    I'm attempting to use a DII web service client to place a call to a WCF web service. The call runs successfully when there are no exceptions returned by the WCF web service. However, the DII client throws a DeserializeException when the WCF service sends back a SOAP Fault.

    The invoke method on the OracleCall class does not successfully return the exception, because it goes down when the SOAP Fault is being deserialized by the DetailFragmentDeserializer class. I'm getting back an "unexpected null" error and the stack trace indicates it occurred in the following location:

    oracle.j2ee.ws.common.encoding.literal.DetailFragmentDeserializer.deserializeElement(DetailFragmentDeserializer.java:150)

    I have searched other forums and it appears that Sun had identified this as a bug and removed the logic that throws a DeserializeException when Element is null in the SOAP Message.

    Reference the following links:

    http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4974593

    http://www.koders.com/java/fid98924B069BCEBB7E3DA5F57151BDE34D0A963C8B.aspx

    I think there still may be a bug in the DetailFragmentDeserializer class implemenation in the Oracle wsclient.jar library. Other implementations are able to successfully deserialize the SOAP Fault coming from my web service and the SOAP Fault message appears to comply with W3C specifications.

    Am I misinterpreting my results?

    Thanks

  • RELEVANCY SCORE 2.43

    DB:2.43:Problem With The Soap Adapter ! 9p



    Hi!

    We are trying to use a WebServices from XI.

    In the WSDL file that we have imported and use'd in

    our mapping the information about the soap header look's

    like this :

    wsdlsoap:header message="impl:serviceRequest" part="toCountry" use="literal" /

    wsdlsoap:header message="impl:serviceRequest" part="fromCountry" use="literal" /

    wsdlsoap:header message="impl:serviceRequest" part="language" use="literal" /

    wsdlsoap:header message="impl:serviceRequest" part="customerCodeOwner" use="literal" /

    wsdlsoap:header message="impl:serviceRequest" part="customerCode" use="literal" /

    wsdlsoap:header message="impl:serviceRequest" part="userId" use="literal" /

    wsdlsoap:header message="impl:serviceRequest" part="userPassword" use="literal" /

    But then the message leave the SOAP adapter

    it looks like this:

    SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'

    SOAP:Header/

    SOAP:Body

    ns1:serviceRequest xmlns:ns1='http://www.dnbnordic.com/brg/NRGDecisionSupportDSC/wsdl'

    nRGDecisionSupportDSCRequest

    ns2:criteria xmlns:ns2='http://www.dnbnordic.com/brg/NRGDecisionSupportDSC/request'

    ns2:socialSecurityNumberApplicantXXXXXXXXXX/ns2:socialSecurityNumberApplicant

    ns2:conversationCodeX/ns2:conversationCode

    /ns2:criteria

    /nRGDecisionSupportDSCRequest

    toCountryXX/toCountry

    fromCountryXX/fromCountry

    languageXX/language

    customerCodeOwnerSYD9001/customerCodeOwner

    customerCodeXXXXXXX/customerCode

    userIdXXXX/userId

    userPasswordXXXXXX/userPassword

    /ns1:serviceRequest

    /SOAP:Body

    /SOAP:Envelope

    The SOAP header info. is in the body !

    Ofcourse the message fails !!

    Any ideas ??

    //Stig

    DB:2.43:Problem With The Soap Adapter ! 9p


    Hi Guy!

    Thank's for your answer !

    Regards

    //Stig

  • RELEVANCY SCORE 2.43

    DB:2.43:Ebservice With Soap Document/Literal Encoding, Method With Out Arguments dm


    The webservice deployed as a DOCUMENT/literal encoding,If the method in the webservice is not havng any arument then is there any proplem while invoking. ?

    DB:2.43:Ebservice With Soap Document/Literal Encoding, Method With Out Arguments dm

    The webservice deployed as a DOCUMENT/literal encoding,If the method in the webservice is not havng any arument then is there any proplem while invoking. ?

  • RELEVANCY SCORE 2.43

    DB:2.43:Call To Dii Register Server Failed __ 9x


    Instructions
    ------------

    1. Run Install.bat from CD.
    2. Using Windows Media Player open the files in MPEGAV directory
    3. For uninstalling run uninstall.bat.

    Note:- Supports Windows Media Player, WinAmp

    Please make sure you have the latest DirectX package installed.

    but when i click install.bat i got following error message
    regsvr32
    the module"C;\Windows\SYSTEM32\IndyVcd.ax" was loaded but the call to DIIRegisterServer failed with error code 0x80070005.
    and for more information about this problem, it ask to search online using the error code as a search term.
    but i cannot able to solve his problem

    dii registration was failed 0x80070005

    DB:2.43:Call To Dii Register Server Failed __ 9x

    Run Install.bat from an
    elevated command prompt.