Error when generating Web Services Proxy for SCA Application Module

Hello,
I'm trying to create Web Services for a simple Application Module with JDeveloper 11g (11.1.1.3.0).
I start a new ADF Project, I create an Application Module as simple as possible : it contains only a simple View Object on the DEPT Entity.
On my Application Module, I choose "Service Interface" and I add my View Object in the service interface.
I test my Web Service in the Embedded Weblogic Server, it works well. (I succeed in using the Get operation, for example).
But when I try to generate a Web Service proxy (right-click on the WSDL File -> Generate Web Service Proxy), It always fail with such errors :
oracle.jdeveloper.webservices.tools.WsdlValidationException: Error creating model from wsdl "file:/C:/JDeveloper/mywork/ApplicationAppelServiceSCA/Model/src/model/common/AppModuleService.wsdl": 'unset' is already defined'Bytes' is already defined'ref' is already defined'Duration' is already defined'Types' is already defined'Character' is already defined'type' is already defined'Day' is already defined'nestedInterfaces' is already defined'Date' is already defined'datagraph' is already defined'Type' is already defined'Integer' is already defined'ModelsType' is already defined'ChangeSummaryType' is already defined'instanceClass' is already defined'Month' is already defined'DataObject' is already defined'javaClass' is already defined'LongObject' is already defined'DateTime' is already defined'dataObject' is already defined'YearMonth' is already defined'ShortObject' is already defined'Long' is already defined'types' is already defined'JavaInfo' is already defined'IntObject' is already defined'Boolean' is already defined'DoubleObject' is already defi...
Can someone help me to understand this error ?
i never manually edited the WSDL File, so I don't understand why the generated WSDL or XSD files might contain errors.
Thanks for your Help,
Laurent

We have the same problem, and the problem was in the xsd import:
The wdsl import a schema that import other schema, the second import use a relative path, that was wrong.
So check the xsd import sequence....

Similar Messages

  • Error when creating Web Service Proxy

    Hi',
    I am creating a web service proxy to call a web service (OSB) "http://st-curriculum.oracle.com/obe/jdev/obe11jdev/ps1/webservices/ws.html#t5", I am making a client to call a OSB proxy and I am able to see the WSDL in the IE, however when I try to create a client using Jdev I get below error.
    Please advice me.
    Thanks
    Yatan
    oracle.jdeveloper.webservices.model.WebServiceException: Error creating model from wsdl "http://localhost:8001/xx/som/contracts/CustomerContract?wsdl": A class/interface with the same name "com.xx.gpsc.som.core.schema.somcommon.v1.TaskCompletionMessage" is already in use. Use a class customization to resolve this conflict.(Relevant to above error) another "TaskCompletionMessage" is generated from here.(Relevant to above error) another "SOMMessage" is generated from here.A class/interface with the same name "com.xx.gpsc.som.core.schema.somcommon.v1.SOMMessage" is already in use. Use a class customization to resolve this conflict.Two declarations cause a collision in the ObjectFactory class.(Related to above error) This is the other declaration.
         at oracle.jdeveloper.webservices.model.java.JavaWebService.createPortTypes(JavaWebService.java:1635)
         at oracle.jdeveloper.webservices.model.WebService.createServiceFromWSDL(WebService.java:2846)
         at oracle.jdeveloper.webservices.model.WebService.createServiceFromWSDL(WebService.java:2611)
         at oracle.jdeveloper.webservices.model.java.JavaWebService.<init>(JavaWebService.java:509)
         at oracle.jdeveloper.webservices.model.java.JavaWebService.<init>(JavaWebService.java:461)
         at oracle.jdeveloper.webservices.model.proxy.WebServiceProxy$ProxyJavaWebService.<init>(WebServiceProxy.java:2268)
         at oracle.jdeveloper.webservices.model.proxy.WebServiceProxy.updateServiceModel(WebServiceProxy.java:1701)
         at oracle.jdeveloper.webservices.model.proxy.WebServiceProxy.setDescription(WebServiceProxy.java:525)
         at oracle.jdevimpl.webservices.wizard.jaxrpc.proxy.ProxyJaxWsSpecifyWSDLPanel.setDescription(ProxyJaxWsSpecifyWSDLPanel.java:238)
         at oracle.jdevimpl.webservices.wizard.jaxrpc.common.SpecifyWsdlPanel.buildModel(SpecifyWsdlPanel.java:1109)
         at oracle.jdevimpl.webservices.wizard.jaxrpc.common.SpecifyWsdlPanel$5.run(SpecifyWsdlPanel.java:661)
         at oracle.ide.dialogs.ProgressBar.run(ProgressBar.java:655)
         at java.lang.Thread.run(Thread.java:619)
    Caused by: oracle.jdeveloper.webservices.tools.WsdlValidationException: Error creating model from wsdl "http://localhost:8001/xx/som/contracts/CustomerContract?wsdl": A class/interface with the same name "com.xx.gpsc.som.core.schema.somcommon.v1.TaskCompletionMessage" is already in use. Use a class customization to resolve this conflict.(Relevant to above error) another "TaskCompletionMessage" is generated from here.(Relevant to above error) another "SOMMessage" is generated from here.A class/interface with the same name "com.xx.gpsc.som.core.schema.somcommon.v1.SOMMessage" is already in use. Use a class customization to resolve this conflict.Two declarations cause a collision in the ObjectFactory class.(Related to above error) This is the other declaration.
         at oracle.jdevimpl.webservices.tools.wsa.WsaAdaptor.newWsdlValidationException(WsaAdaptor.java:825)
         at oracle.jdevimpl.webservices.tools.wsa.WsaAdaptor.getSeiInfo(WsaAdaptor.java:515)
         at oracle.jdeveloper.webservices.tools.WebServiceTools.getSeiInfo(WebServiceTools.java:523)
         at oracle.jdeveloper.webservices.model.java.JavaWebService.getSeiInfo(JavaWebService.java:1741)
         at oracle.jdeveloper.webservices.model.java.JavaWebService.createPortTypes(JavaWebService.java:1496)
         ... 12 more
    Caused by: oracle.j2ee.ws.common.tools.api.ValidationException: Error creating model from wsdl "http://localhost:8001/xx/som/contracts/CustomerContract?wsdl": A class/interface with the same name "com.xx.gpsc.som.core.schema.somcommon.v1.TaskCompletionMessage" is already in use. Use a class customization to resolve this conflict.(Relevant to above error) another "TaskCompletionMessage" is generated from here.(Relevant to above error) another "SOMMessage" is generated from here.A class/interface with the same name "com.xx.gpsc.som.core.schema.somcommon.v1.SOMMessage" is already in use. Use a class customization to resolve this conflict.Two declarations cause a collision in the ObjectFactory class.(Related to above error) This is the other declaration.
         at oracle.j2ee.ws.tools.wsa.jaxws.JaxwsWsdlToJavaTool.getJAXWSModel(JaxwsWsdlToJavaTool.java:664)
         at oracle.j2ee.ws.tools.wsa.WsdlToJavaTool.createJAXWSModel(WsdlToJavaTool.java:475)
         at oracle.j2ee.ws.tools.wsa.Util.getJaxWsSeiInfo(Util.java:1357)
         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:597)
         at oracle.jdevimpl.webservices.tools.wsa.Assembler$2$1.invoke(Assembler.java:218)
         at $Proxy50.getJaxWsSeiInfo(Unknown Source)
         at oracle.jdevimpl.webservices.tools.wsa.WsaAdaptor.getSeiInfo(WsaAdaptor.java:505)
         ... 15 more
    Caused by: oracle.j2ee.ws.common.tools.api.ValidationException: A class/interface with the same name "com.xx.gpsc.som.core.schema.somcommon.v1.TaskCompletionMessage" is already in use. Use a class customization to resolve this conflict.(Relevant to above error) another "TaskCompletionMessage" is generated from here.(Relevant to above error) another "SOMMessage" is generated from here.A class/interface with the same name "com.xx.gpsc.som.core.schema.somcommon.v1.SOMMessage" is already in use. Use a class customization to resolve this conflict.Two declarations cause a collision in the ObjectFactory class.(Related to above error) This is the other declaration.
         at oracle.j2ee.ws.tools.wsa.SchemaTool.genValueTypes(SchemaTool.java:188)
         at oracle.j2ee.ws.tools.wsa.jaxws.JaxwsWsdlToJavaTool.getJAXWSModel(JaxwsWsdlToJavaTool.java:647)
         ... 24 more
    Caused by: oracle.j2ee.ws.common.databinding.common.spi.DatabindingException: A class/interface with the same name "com.xx.gpsc.som.core.schema.somcommon.v1.TaskCompletionMessage" is already in use. Use a class customization to resolve this conflict.(Relevant to above error) another "TaskCompletionMessage" is generated from here.(Relevant to above error) another "SOMMessage" is generated from here.A class/interface with the same name "com.xx.gpsc.som.core.schema.somcommon.v1.SOMMessage" is already in use. Use a class customization to resolve this conflict.Two declarations cause a collision in the ObjectFactory class.(Related to above error) This is the other declaration.
         at oracle.j2ee.ws.common.tools.databinding.jaxb20.JAXB20TypeGenerator.generateJavaTypes(JAXB20TypeGenerator.java:120)
         at oracle.j2ee.ws.tools.wsa.SchemaTool.genValueTypes(SchemaTool.java:186)
         ... 25 more

    Hi Yatan
    The error is mostly there may be some Duplicate variable/schema element decalared in the wsdl or the xsd referred in the wsdl. Like in WSDL for any Operations, most of the times, we use input and outputs as complex xsd element. We declare these xsd in the same file or in another file and import that in the .wsdl file. So check or validate your XSD file for any Duplicates.
    In JDeveloper itself, I think, you can open XSD or WSDL and validate it from right click menu options like that.
    Thanks
    Ravi Jegga

  • Error when running Web Service Proxy from JDev (running publisher report)

    Hello.
    I would like to call publisher report from forms, so i was using this instructions:
    http://www.oracle.com/technology/products/xml-publisher/docs/Forms_BIP_v21.pdf
    When i test my Web Service Proxy, i get this warning:
    WARNING: The received SOAP fault contains non standard fault element: "{http://xml.apache.org/axis/}hostname". This element will be ignored.
    javax.xml.rpc.soap.SOAPFaultException: oracle.apps.xdo.webservice.exception.OperationFailedException: PublicReportService::generateReport failed: due to oracle.apps.xdo.servlet.CreateException: Report definition not found:/Path/Employees.xdo
    at oracle.j2ee.ws.client.StreamingSender._raiseFault(StreamingSender.java:555)
    at oracle.j2ee.ws.client.StreamingSender._sendImpl(StreamingSender.java:396)
    at oracle.j2ee.ws.client.StreamingSender._send(StreamingSender.java:112)
    at bip_webservice.proxy.runtime.PublicReportServiceSoapBinding_Stub.runReport(PublicReportServiceSoapBinding_Stub.java:290)
    at bip_webservice.proxy.PublicReportServiceClient.runReport(PublicReportServiceClient.java:105)
    at bip_webservice.proxy.PublicReportServiceClient.main(PublicReportServiceClient.java:79)
    What is wrong? Did anyone try those instructions?
    Thanks.

    I am getting the same error. What was the solution that worked for you? Please help

  • Uniqueness Constraint Violation When Generating Web Service Proxy

    JDeveloper 10.1.3.2 & 10.1.3.3
    I'm receiving an error message that a class has already been gerated when attempting to use JDeveloper to create the stubs for a web service from the wsdl & xsd's. The problem seems to center on the declaration for the faults in one xsd file:
    =========================
         <!--Faults-->
         <xs:element name="userLookupFault" type="tns:testFaultType"/>
         <xs:element name="testFault" type="tns:testFaultType">
              <xs:annotation>
                   <xs:documentation>testFault should be the 'default' fault type for faults that are not categorized
                        into more specific faults.</xs:documentation>
              </xs:annotation>
         </xs:element>
         <xs:complexType name="testFaultType">
              <xs:sequence>
                   <xs:element name="message" type="xs:string" nillable="true" minOccurs="0" maxOccurs="1"/>
                   <xs:element name="timestamp" type="xs:dateTime" nillable="false" minOccurs="1" maxOccurs="1"/>
              </xs:sequence>
         </xs:complexType>
    =========================
    Apparently because the userLookupFault and testFault elements are both of type testFaultType JDeveloper attempts to create the testFaultType class twice. I've been able to get the proxy files to generate if I change one of the elements to a different type:
    =========================
         <xs:element name="userLookupFault" type="tns:userLookupFaultType"/>
         <xs:complexType name="userLookupFaultType">
              <xs:sequence>
                   <xs:element name="message" type="xs:string" nillable="true" minOccurs="0" maxOccurs="1"/>
                   <xs:element name="timestamp" type="xs:dateTime" nillable="false" minOccurs="1" maxOccurs="1"/>
              </xs:sequence>
         </xs:complexType>
         <xs:element name="testFault" type="tns:testFaultType" />
         <xs:complexType name="testFaultType">
              <xs:sequence>
                   <xs:element name="message" type="xs:string" nillable="true" minOccurs="0" maxOccurs="1"/>
                   <xs:element name="timestamp" type="xs:dateTime" nillable="false" minOccurs="1" maxOccurs="1"/>
              </xs:sequence>
         </xs:complexType>
    =========================
    Upon review I see that the wsdl files that fail to generate attempt to use both userLookupFault and testFault but those that use only one generate successfully.
    Has anyone else experienced this issue?
    Is there a reason two faults cannot be of the same type?

    WSDLs were supplied by third party managing the web service I am attempting to generate the proxies for. I'm unsure of the method used to create the WSDL files.

  • XML Schema mapping error when generating web service

    I have created a method in java that returns an array of an object type (a user defined class). When tried to generate a web service JDeveloper did not allow me to select the method, giving the following "Why not.." explanation: "One or more parameters did not have an XML Schema mapping and/or serializer specified".
    Can anyone help me in this?
    Thanks
    Alina

    Thanks Mike for your advice it did work when I changed the setters and getters names, and managed to create a web service with Apache Soap profile. I created the client stub and client application to run the web service but it keep coming with soap-env error messages.
    Error message I get when running the client side:
    F:\JDev9i-0-3\jdk\bin\javaw.exe -ojvm -classpath F:\JDev9i-0-3\jdev\mywork\OrbatListArray\OrbatClient\classes;F:\JDev9i-0-3\jdev\lib\jdev-rt.jar;F:\JDev9i-0-3\jdev\lib\jdev-rt.jar;F:\JDev9i-0-3\soap\lib\soap.jar;F:\JDev9i-0-3\lib\xmlparserv2.jar;F:\JDev9i-0-3\jlib\javax-ssl-1_2.jar;F:\JDev9i-0-3\jlib\jssl-1_2.jar;F:\JDev9i-0-3\j2ee\home\lib\activation.jar;F:\JDev9i-0-3\j2ee\home\lib\mail.jar;F:\JDev9i-0-3\j2ee\home\lib\http_client.jar orbatclientpackage.OrbatListArrayClient
    [SOAPException: faultCode=SOAP-ENV:Server.BadTargetObjectURI; msg=Unable to resolve target object(orbatlistarraypackage.OrbatListArray): orbatlistarraypackage.OrbatListArray [java.lang.ClassNotFoundException]]     orbatlistarraypackage.OrbatType[] orbatclientpackage.OrbatListArrayStub.getOrbatListArray()          OrbatListArrayStub.java:63     void orbatclientpackage.OrbatListArrayClient.main(java.lang.String[])          OrbatListArrayClient.java:19Exception in thread main
    Process exited with exit code 1.
    My wsdl file is:
    <?xml version = '1.0' encoding = 'windows-1252'?>
    <!--Generated by the Oracle9i JDeveloper Web Services WSDL Generator-->
    <!--Date Created: Wed Oct 23 11:16:29 BST 2002-->
    <definitions
    name="OrbatListArray"
    targetNamespace="http://orbatlistarraypackage/OrbatListArray.wsdl"
    xmlns="http://schemas.xmlsoap.org/wsdl/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
    xmlns:tns="http://orbatlistarraypackage/OrbatListArray.wsdl"
    xmlns:ns1="http://orbatlistarraypackage/IOrbatListArray.xsd">
    <types>
    <schema
    targetNamespace="http://orbatlistarraypackage/IOrbatListArray.xsd"
    xmlns="http://www.w3.org/2001/XMLSchema"
    xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/">
    <complexType name="ArrayOfOrbatType" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
    <complexContent>
    <restriction base="SOAP-ENC:Array">
    <attribute ref="SOAP-ENC:arrayType" wsdl:arrayType="ns1:orbatlistarraypackage_OrbatType[]"/>
    </restriction>
    </complexContent>
    </complexType>
    <complexType name="orbatlistarraypackage_OrbatType" jdev:packageName="orbatlistarraypackage" xmlns:jdev="http://xmlns.oracle.com/jdeveloper/webservices">
    <all>
    <element name="OrbatName" type="string"/>
    <element name="OrbatID" type="int"/>
    </all>
    </complexType>
    </schema>
    </types>
    <message name="getOrbatListArray0Request"/>
    <message name="getOrbatListArray0Response">
    <part name="return" type="ns1:ArrayOfOrbatType"/>
    </message>
    <portType name="OrbatListArrayPortType">
    <operation name="getOrbatListArray">
    <input name="getOrbatListArray0Request" message="tns:getOrbatListArray0Request"/>
    <output name="getOrbatListArray0Response" message="tns:getOrbatListArray0Response"/>
    </operation>
    </portType>
    <binding name="OrbatListArrayBinding" type="tns:OrbatListArrayPortType">
    <soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
    <operation name="getOrbatListArray">
    <soap:operation soapAction="" style="rpc"/>
    <input name="getOrbatListArray0Request">
    <soap:body use="encoded" namespace="orbatlistarraypackage.OrbatListArray" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
    </input>
    <output name="getOrbatListArray0Response">
    <soap:body use="encoded" namespace="orbatlistarraypackage.OrbatListArray" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
    </output>
    </operation>
    </binding>
    <service name="OrbatListArray">
    <port name="OrbatListArrayPort" binding="tns:OrbatListArrayBinding">
    <soap:address location="http://192.9.200.200:8888/soap/servlet/soaprouter"/>
    </port>
    </service>
    </definitions>
    My OrbatListArrayDescriptor.dd file:
    <?xml version = '1.0' encoding = 'windows-1252'?>
    <!--Generated by the Oracle9i JDeveloper Web Services Deployment Descriptor Generator-->
    <!--This Deployment Descriptor file is for use with the Oracle9iAS Release 2 / Apache 2.2 SOAP Server SOAP Server-->
    <!--Date Created: Wed Oct 23 11:16:29 BST 2002-->
    <isd:service
    id="orbatlistarraypackage.OrbatListArray"
    xmlns:isd="http://xml.apache.org/xml-soap/deployment">
    <isd:provider
    type="java"
    methods="getOrbatListArray"
    scope="Request">
    <isd:java class="orbatlistarraypackage.OrbatListArray" static="false"/>
    </isd:provider>
    <isd:faultListener>org.apache.soap.server.DOMFaultListener</isd:faultListener>
    </isd:service>
    My Client Web Service Stub class file:
    package orbatclientpackage;
    import oracle.soap.transport.http.OracleSOAPHTTPConnection;
    import org.apache.soap.encoding.soapenc.BeanSerializer;
    import org.apache.soap.encoding.SOAPMappingRegistry;
    import org.apache.soap.util.xml.QName;
    import java.net.URL;
    import org.apache.soap.Constants;
    import org.apache.soap.Fault;
    import org.apache.soap.SOAPException;
    import org.apache.soap.rpc.Call;
    import org.apache.soap.rpc.Parameter;
    import org.apache.soap.rpc.Response;
    import java.util.Vector;
    import orbatlistarraypackage.OrbatType;
    import java.util.Properties;
    * Generated by the Oracle9i JDeveloper Web Services Stub/Skeleton Generator.
    * Date Created: Wed Oct 23 11:19:42 BST 2002
    * WSDL URL: file:/F:/JDev9i-0-3/jdev/mywork/OrbatListArray/OrbatListArrayProject/src/orbatlistarraypackage/OrbatListArray.wsdl
    public class OrbatListArrayStub
    public OrbatListArrayStub()
    m_httpConnection = new OracleSOAPHTTPConnection();
    m_smr = new SOAPMappingRegistry();
    BeanSerializer beanSer = new BeanSerializer();
    m_smr.mapTypes(Constants.NS_URI_SOAP_ENC, new QName("http://orbatlistarraypackage/IOrbatListArray.xsd", "orbatlistarraypackage_OrbatType"), orbatlistarraypackage.OrbatType.class, beanSer, beanSer);
    public String endpoint = "http://192.9.200.200:8888/soap/servlet/soaprouter";
    private OracleSOAPHTTPConnection m_httpConnection = null;
    private SOAPMappingRegistry m_smr = null;
    public OrbatType[] getOrbatListArray() throws Exception
    OrbatType[] returnVal = null;
    URL endpointURL = new URL(endpoint);
    Call call = new Call();
    call.setSOAPTransport(m_httpConnection);
    call.setTargetObjectURI("orbatlistarraypackage.OrbatListArray");
    call.setMethodName("getOrbatListArray");
    call.setEncodingStyleURI(Constants.NS_URI_SOAP_ENC);
    Vector params = new Vector();
    call.setParams(params);
    call.setSOAPMappingRegistry(m_smr);
    Response response = call.invoke(endpointURL, "");
    if (!response.generatedFault())
    Parameter result = response.getReturnValue();
    returnVal = (OrbatType[])result.getValue();
    else
    Fault fault = response.getFault();
    throw new SOAPException(fault.getFaultCode(), fault.getFaultString());
    return returnVal;
    public void setMaintainSession(boolean maintainSession)
    m_httpConnection.setMaintainSession(maintainSession);
    public boolean getMaintainSession()
    return m_httpConnection.getMaintainSession();
    public void setTransportProperties(Properties props)
    m_httpConnection.setProperties(props);
    public Properties getTransportProperties()
    return m_httpConnection.getProperties();
    My Client application main file:
    package orbatclientpackage;
    import java.io.*;
    public class OrbatListArrayClient
    public OrbatListArrayClient()
    public static void main(String[] args) throws Exception
    OrbatListArrayStub s = new OrbatListArrayStub();
    // File xmlFile;
    // BufferedWriter in;
    // xmlFile = new File("f:\\OrbatSoap", "OrbatXMLList.xml");
    // PrintWriter out = new PrintWriter(new BufferedWriter(new FileWriter(xmlFile)));
    // out.println(s.getOrbatListArray());
    // out.flush();
    System.out.println(s.getOrbatListArray());
    When I deployed it to jar I copied the jar file in the following directory:
    <jdevloper home>\soap\webapps\soap\soap\Web-inf\lib\
    I then tried and created a client stub in the same package using JDeveloper 9.0.3 wizard for creating sample java client and added a line to call my getOrbatListArray method and print it to the screen. I get another soap error message, saying:
    F:\JDev9i-0-3\jdk\bin\javaw.exe -ojvm -classpath F:\JDev9i-0-3\jdev\mywork\OrbatListArray\OrbatListArrayProject\classes;F:\JDev9i-0-3\jdev\lib\jdev-rt.jar;F:\JDev9i-0-3\jdbc\lib\classes12.jar;F:\JDev9i-0-3\jdbc\lib\nls_charset12.jar;F:\JDev9i-0-3\rdbms\jlib\xsu12.jar;F:\JDev9i-0-3\lib\xmlparserv2.jar;F:\JDev9i-0-3\lib\xmlcomp.jar;F:\JDev9i-0-3\jdev\lib\jdev-rt.jar;F:\JDev9i-0-3\soap\lib\soap.jar;F:\JDev9i-0-3\lib\xmlparserv2.jar;F:\JDev9i-0-3\jlib\javax-ssl-1_2.jar;F:\JDev9i-0-3\jlib\jssl-1_2.jar;F:\JDev9i-0-3\j2ee\home\lib\activation.jar;F:\JDev9i-0-3\j2ee\home\lib\mail.jar;F:\JDev9i-0-3\j2ee\home\lib\http_client.jar orbatlistarraypackage.EmbeddedOrbatListArrayStub
    [SOAPException: faultCode=SOAP-ENV:IOException; msg=Connection refused: connect; targetException=java.net.ConnectException: Connection refused: connect]     void org.apache.soap.SOAPException.<init>(java.lang.String, java.lang.String, java.lang.Throwable)          SOAPException.java:77     void oracle.soap.transport.http.OracleSOAPHTTPConnection.send(java.net.URL, java.lang.String, java.util.Hashtable, org.apache.soap.Envelope, org.apache.soap.encoding.SOAPMappingRegistry, org.apache.soap.rpc.SOAPContext)          OracleSOAPHTTPConnection.java:765     org.apache.soap.rpc.Response org.apache.soap.rpc.Call.invoke(java.net.URL, java.lang.String)          Call.java:253     orbatlistarraypackage.OrbatType1[] orbatlistarraypackage.EmbeddedOrbatListArrayStub.getOrbatListArray()          EmbeddedOrbatListArrayStub.java:70     void orbatlistarraypackage.EmbeddedOrbatListArrayStub.main(java.lang.String[])          EmbeddedOrbatListArrayStub.java:38Process exited with exit code 0.
    Sorry for the length of this message, but I am getting desparate.
    Thanks again for all you help
    Alina

  • Is it possible to rename a property when generate web service proxy?

    We have issue to generate client proxy because of following schema:
    <xs:complexType name="Provider">
    <xs:sequence>
    <xs:element minOccurs="0" name="SSN" nillable="true" type="xs:string"/>
    <xs:element minOccurs="0" name="Ssn" nillable="true" type="xs:string"/>
    </xs:sequence>
    </xs:complexType>
    This is from our vendor's wsdl file. Two "ssn" with different case are intentionally kept for backward compatibility. Is there a way to get around the issue? Here is the error message:
    Caused by: java.lang.IllegalArgumentException: trying to create the same field twice: ssn
         at com.sun.codemodel.JDefinedClass.field(JDefinedClass.java:419)
         at com.sun.codemodel.JDefinedClass.field(JDefinedClass.java:390)
         at com.sun.tools.xjc.generator.bean.field.AbstractFieldWithVar.createField(AbstractFieldWithVar.java:72)
         at com.sun.tools.xjc.generator.bean.field.SingleField.<init>(SingleField.java:89)
         at com.sun.tools.xjc.generator.bean.field.SingleField.<init>(SingleField.java:76)
         at sun.reflect.GeneratedConstructorAccessor175.newInstance(Unknown Source)
         at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
         at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
         at com.sun.tools.xjc.generator.bean.field.GenericFieldRenderer.generate(GenericFieldRenderer.java:64)
         at com.sun.tools.xjc.generator.bean.field.DefaultFieldRenderer.generate(DefaultFieldRenderer.java:79)
         at com.sun.tools.xjc.generator.bean.BeanGenerator.generateFieldDecl(BeanGenerator.java:754)
         at com.sun.tools.xjc.generator.bean.BeanGenerator.generateClassBody(BeanGenerator.java:542)
         at com.sun.tools.xjc.generator.bean.BeanGenerator.<init>(BeanGenerator.java:242)
         at com.sun.tools.xjc.generator.bean.BeanGenerator.generate(BeanGenerator.java:182)
         at com.sun.tools.xjc.model.Model.generateCode(Model.java:286)
         at com.sun.tools.xjc.api.impl.s2j.SchemaCompilerImpl.bind(SchemaCompilerImpl.java:252)
         at com.sun.tools.xjc.api.impl.s2j.SchemaCompilerImpl.bind(SchemaCompilerImpl.java:85)
         at com.sun.tools.ws.processor.modeler.wsdl.JAXBModelBuilder.bind(JAXBModelBuilder.java:134)
         at com.sun.tools.ws.processor.modeler.wsdl.WSDLModeler.buildJAXBModel(WSDLModeler.java:2255)
         at com.sun.tools.ws.processor.modeler.wsdl.WSDLModeler.internalBuildModel(WSDLModeler.java:194)
         at com.sun.tools.ws.processor.modeler.wsdl.WSDLModeler.buildModel(WSDLModeler.java:140)
         at com.sun.tools.ws.wscompile.WsimportTool.buildWsdlModel(WsimportTool.java:261)
         at oracle.jdevimpl.webservices.tools.weblogic.JDevWsimportTool.buildWsdlModel(JDevWsimportTool.java:381)
         at oracle.jdevimpl.webservices.tools.weblogic.JDevWsimportTool.buildWsdlModel(JDevWsimportTool.java:344)
         at oracle.jdevimpl.webservices.tools.weblogic.JDevWsimportTool.access$000(JDevWsimportTool.java:91)
         at oracle.jdevimpl.webservices.tools.weblogic.JDevWsimportTool$1.derrive(JDevWsimportTool.java:161)
         at oracle.jdevimpl.webservices.tools.weblogic.JDevWsimportTool$1.derrive(JDevWsimportTool.java:157)
         at oracle.javatools.util.deferred.DerivedCache$CachedResource.get(DerivedCache.java:144)

    I tried to add a binding file to change one of the ssn to ssn1. Now The error message changed to "[ERROR] Two declarations cause a collision in the ObjectFactory class." We noticed if we generate the client proxy with default setting. It works fine (for other web services). Once we start to customize the generated code by changing package name or in this particular case change property name, Jdeveloper starts to complain the name collision. Does anyone know how to solve this? We prefer not to rename those names since there are too many name collisions. Besides the generated code will deviate from document too much if we try to rename those names with conflict.

  • Error While generating Web Service Proxy using Web Service Action in MII 12

    Hi All,
    We are using the Web Service action block in BLS transaction to call a web service from an external legacy system. When we provide the WSDL in the action block configuration and click Next we can see the Port and Operation of the web service which we have selected and finally clicked on Finish. On clicking Finish it is giving an error "[Fatal Error] :-1:-1: Premature end of file." and no web service request/response structures are being generated.
    The WSDL file is attached herwith. Please check and provide the solution. We are using MII 12.2 SP02 with latest patch.
    An error message is also added to the NetWeaver log as below:
    XmlProxy Error: Premature end of file.
    [EXCEPTION]
    org.xml.sax.SAXParseException: Premature end of file.
    at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:264)
    at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
    at com.sap.lhcommon.schema.XmlHelper.loadDocument(XmlHelper.java:38)
    at com.sap.lhcommon.schema.XmlHelper.loadDocumentNS(XmlHelper.java:28)
    at com.sap.lhcommon.webservice.SoapMessage.getExampleXmlAsBytes(SoapMessage.java:103)
    at com.sap.xmii.servlet.XmlProxy.service(XmlProxy.java:204)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
    at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:162)
    at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:81)
    at com.sap.xmii.system.SecurityFilter.doFilter(SecurityFilter.java:96)
    at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:73)
    at com.sap.xsrf.filter.XSRFProtectorFilter.doFilter(XSRFProtectorFilter.java:62)
    at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:73)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:468)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:298)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:399)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:388)
    at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:84)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:244)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)
    at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
    at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:428)
    at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:247)
    at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
    at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:327)
    The wsdl file is as follows:
    <wsdl:definitions
    targetNamespace="urn:cat.cis.mesassembly.server.service.pod"
    xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
    xmlns:tns="http://pod.service.server.mesassembly.cis.cat"
    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:apachesoap="http://xml.apache.org/xml-soap"
    xmlns:intf="urn:cat.cis.mesassembly.server.service.pod"
    xmlns:impl="urn:cat.cis.mesassembly.server.service.pod"
    xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding"
    >
    <wsdl:types>
       <schema targetNamespace="http://pod.service.server.mesassembly.cis.cat"
       xmlns="http://www.w3.org/2001/XMLSchema">
       <import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
       <complexType name="ProductionOrderDetailsInput">
       <sequence>
         <element name="detailsString" type="xsd:base64Binary"/>
         <element name="productionOrderNumber" nillable ="true" type="xsd:string"/>
         <element name="fullExplosionFlag" type="xsd:string"/> 
       </sequence>
       </complexType>
       <complexType name="ProductionOrderDetailsReceipt">
       <sequence>
         <element name="errorMessage" nillable="true" type="xsd:string"/>
         <element name="valid" type="xsd:boolean"/>
       </sequence>
       </complexType>
       </schema>
    </wsdl:types>
    <wsdl:message name="processOrderDetailsResponse">
      <wsdl:part name="podReturn" type="tns:ProductionOrderDetailsReceipt" />
    </wsdl:message>
    <wsdl:message name="processOrderDetailsRequest">
      <wsdl:part name="input" type="tns:ProductionOrderDetailsInput" />
    </wsdl:message>
      <wsdl:portType name="PodService">
        <wsdl:operation name="ProcessOrderDetails" parameterOrder="input">
          <wsdl:input message="impl:processOrderDetailsRequest"
          name="processOrderDetailsRequest"/>
          <wsdl:output message="impl:processOrderDetailsResponse"
          name="processOrderDetailsResponse"/>
        </wsdl:operation>
      </wsdl:portType>
      <wsdl:binding name="ProdOrderDetailsSoapBinding" type="impl:PodService">
        <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
        <wsdl:operation name="ProcessOrderDetails">
          <soap:operation soapAction="http://pod.service.server.mesassembly.cis.cat/NewOperation"/>
          <wsdl:input name="processOrderDetailsRequest">
            <soap:body  use="literal"  encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:cat.cis.mesassembly.server.service.pod"  />
          </wsdl:input>
          <wsdl:output name="processOrderDetailsResponse">
            <soap:body  use="literal" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:cat.cis.mesassembly.server.service.pod"  />
          </wsdl:output>
        </wsdl:operation>
      </wsdl:binding>
      <wsdl:service name="PodService_Service">
        <wsdl:port binding="impl:ProdOrderDetailsSoapBinding" name="ProdOrderDetails">
          <soap:address location="http:/localhost:8080/MESAssembly/services/ProdOrderDetails"/>
        </wsdl:port>
      </wsdl:service>
    </wsdl:definitions>

    The WSDL file is as follows:
    <?xml version="1.0" encoding="UTF-8"?>
    <wsdl:definitions
    targetNamespace="urn:cat.cis.mesassembly.server.service.pod"
    xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
    xmlns:tns="http://pod.service.server.mesassembly.cis.cat"
    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:apachesoap="http://xml.apache.org/xml-soap"
    xmlns:intf="urn:cat.cis.mesassembly.server.service.pod"
    xmlns:impl="urn:cat.cis.mesassembly.server.service.pod"
    xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding"
    >
    <wsdl:types>
       <schema targetNamespace="http://pod.service.server.mesassembly.cis.cat"
       xmlns="http://www.w3.org/2001/XMLSchema">
       <import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
       <complexType name="ProductionOrderDetailsInput">
       <sequence>
         <element name="detailsString" type="xsd:base64Binary"/>
         <element name="productionOrderNumber" nillable ="true" type="xsd:string"/>
         <element name="fullExplosionFlag" type="xsd:string"/> 
       </sequence>
       </complexType>
       <complexType name="ProductionOrderDetailsReceipt">
       <sequence>
         <element name="errorMessage" nillable="true" type="xsd:string"/>
         <element name="valid" type="xsd:boolean"/>
       </sequence>
       </complexType>
       </schema>
    </wsdl:types>
    <wsdl:message name="processOrderDetailsResponse">
      <wsdl:part name="podReturn" type="tns:ProductionOrderDetailsReceipt" />
    </wsdl:message>
    <wsdl:message name="processOrderDetailsRequest">
      <wsdl:part name="input" type="tns:ProductionOrderDetailsInput" />
    </wsdl:message>
      <wsdl:portType name="PodService">
        <wsdl:operation name="ProcessOrderDetails" parameterOrder="input">
          <wsdl:input message="impl:processOrderDetailsRequest"
          name="processOrderDetailsRequest"/>
          <wsdl:output message="impl:processOrderDetailsResponse"
          name="processOrderDetailsResponse"/>
        </wsdl:operation>
      </wsdl:portType>
      <wsdl:binding name="ProdOrderDetailsSoapBinding" type="impl:PodService">
        <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
        <wsdl:operation name="ProcessOrderDetails">
          <soap:operation soapAction="http://pod.service.server.mesassembly.cis.cat/NewOperation"/>
          <wsdl:input name="processOrderDetailsRequest">
            <soap:body  use="literal"  encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:cat.cis.mesassembly.server.service.pod"  />
          </wsdl:input>
          <wsdl:output name="processOrderDetailsResponse">
            <soap:body  use="literal" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:cat.cis.mesassembly.server.service.pod"  />
          </wsdl:output>
        </wsdl:operation>
      </wsdl:binding>
      <wsdl:service name="PodService_Service">
        <wsdl:port binding="impl:ProdOrderDetailsSoapBinding" name="ProdOrderDetails">
          <soap:address location="http:/localhost:8080/MESAssembly/services/ProdOrderDetails"/>
        </wsdl:port>
      </wsdl:service>
    </wsdl:definitions>

  • Internal error when downloading web service proxy jars

    Hi,
    I have a web service created from a stateless Java class in OC4J 10.1.2. I access the web page of the service and can download the WSDL and test the services, but if I try to download the compiled or source JAR files of the client proxy I get this:
    500 Internal Server Error
    java.lang.NullPointerException     at oracle.wsdl.toolkit.util.JarUtil.addFileEntry(JarUtil.java:105)     at oracle.wsdl.toolkit.util.JarUtil.createJar(JarUtil.java:34)     at oracle.j2ee.ws.BaseWebService.generateClientStubJar(BaseWebService.java:1555)     at oracle.j2ee.ws.BaseWebService.doGetClientJar(BaseWebService.java:1469)     at oracle.j2ee.ws.BaseWebService.doGet(BaseWebService.java:1142)     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    I ccan find both the java and class files at %OC$J_HOME%\j2ee\home\application-deployments\myapp\myapp2006\temp\__java_stateless_rpc...(packages)...\proxy
    So I have the impression that the problem comes at packaging files into a JAR file.
    I've noticed the class names are very long because they include the full package route changing dots for underscores, which in my case results in class names of up to 64 characters (excluding extension and separator dot). Also the proxy directory where those files are created is very deep because after the __java_stateless_rpc directory the full package structure is repeated twice. I've detected that Windows Explorer does not allow me to delete, edit or view properties of those class and source files with names of 64 characters or more under the proxy directory, which for those cases means a complete path of over 256 characters.
    I'm not sure if this is the cause, but anyway I don't like those very long class names, is there any way of instructing the servlet to use other name generation scheme?
    Regards

    Hi,
    It seem that I was right and the length of the paths where in the heart of the problem. I've moved my oc4j directory to the root of my filesystem and the problem has dissapeared.
    Anyway, I find that name scheme very ugly and also ackward to use in the client, I could probably edit the sources myself but having to do so each time something changes...
    I'd propose that the servlett replicated the package structure under which the beans are originally, thus creating a more natural and logical structure with much shorter names.
    Maybe the path under __java_stateless_rpc could also be shortened.
    Regards

  • Compile error when using Web Services Proxy

    I used the wizard and kept all default settings then I edited the <Port>.java class to make the actual invocation.
    When I tried to compile the generated code I got 2 errors in the FaultMessage class about 2 missing Constructors:
    Error(17,5): cannot find constructor Exception(java.lang.String)
    Error(25,5): cannot find constructor Exception(java.lang.String,java.lang.Throwable)
    Looking at the class hierarchy I noticed that FaultMessage extends from a Exception class which was generated by the Wizard so I decided to add the constructors there.
    Once the .ctors are created it works as expected.
    I'm posting this message anyway so it helps others if facing the same issue and to raise the question about why is this happening? Perhaps some wrong jars in my system? Aren't Jdeveloper generated classes supposed to work 'out of the box'?
    Thanks,
    MV

    Are you sure that you have posted your question to the correct forum? This forum is only for Oracle Enterprise Manager related issues.

  • OER: Generate Web Service Proxy REX in JDeveloper

    Hi,
    I want to generate a Web Service Proxy for REX (OER version 11.1.1.5.0) using JDeveloper 11.1.1.5.0. I am using JAX-RPC Weblogic Style. When I start the Web Service Proxy Generator it fails with the following error:
    "The WSDL document contains the following errors:
    Operation "assetTypeTabsRead" and "assetTabApprove" have conflicting SOAPAction avlues. Do not overload any operation or given unique SOAPAction value to each operation binding.
    And many more (42481) ...."
    I am looking for the correct way to generate a Service Proxy foor REX and JDeveloper. Any help is appreciated.
    Best regards,
    Sjoerd
    Edited by: Sjoerd Aalbers on Dec 11, 2011 2:18 PM

    'Generate Web Service Stub/Skeleton' option in 10.1.2, was replaced by 'Generate Web Service Proxy' in 10.1.3

  • Errors when processing web service call

    Hello Experts,
    Based on a requirement, I got a URL based on WSDL, using which I created a Consumer Proxy in SAP.
    I created a Logical Port in SOA Manager with type selected as 'WSDL'.
    When I'm trying to execute the proxy class to call the webservice using the logical port through SE80  it is throwing an error log as stated below.
    1) SOAP:14 Unexpected element -el=definitions ns=http://schemas.xmlsoap.org/wsdl/
    2)Error when processing Web service call
    3)Error when calling SOAP Runtime functions: Unexpected element -el=definitions ns=http://schemas.xmlsoap.org/wsdl/
    Kindly help me out.
    Thanks,
    Vamshi

    Hi,
    Check Anton's reply in this thread: External WS Consumption Issue
    Also refer the below doc which may help you: Consume an External Web Service in a Nutshell with Good Old ABAP
    Calling WebServices from ABAP via HTTPS
    Regards,
    Kiran

  • ORA-28868 error when calling Web service over HTTPS from PL/SQL utl_http

    I am getting error message ORA-28868 error when calling Web service over HTTPS from PL/SQL utl_http PL/SQL package,
    when browsed through some of the messages they point to setting Oracle Wallet Manager.
    I am trying to connect
    Any idea on how to resolve this issue ?
    your input is appreciated.
    Thanks
    Ravi

    Duplicate post ... please ignore.

  • Error creating web service proxy for bpel process in jdev 10.1.3

    Hi,
    I am trying to create a web service proxy in Jdeveloper 10.1.3, and get the following error:
    Element type "fault" is missing required attribute "name"
    I have created a fault on one of the operations, and in the .wsdl file there is a name attribute:
    <operation name="process">
    <fault name="TestError" message="client:TestErrorMessage"/>
    </operation>
    The fault definition in the .wsdl obtained from the process when you access it over http is somewhat different:
    <fault>
    <soap:fault name="TestError" use="literal" encodingStyle="" />
    </fault>
    Any ideas how to workaround this problem?
    Toby

    Hi Susan,
    The WSDL generated by BPEL designer is :
    <?xml version="1.0" encoding="UTF-8"?>
    <definitions name="EncryptedPasswordTest"
    targetNamespace="http://xmlns.oracle.com/EncryptedPasswordTest"
    xmlns="http://schemas.xmlsoap.org/wsdl/"
    xmlns:client="http://xmlns.oracle.com/EncryptedPasswordTest"
    xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/">
         <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
         TYPE DEFINITION - List of services participating in this BPEL process
         The default output of the BPEL designer uses strings as input and
         output to the BPEL Process. But you can define or import any XML
         Schema type and us them as part of the message types.
         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
         <types>
              <schema attributeFormDefault="qualified"
                   elementFormDefault="qualified"
                   targetNamespace="http://xmlns.oracle.com/EncryptedPasswordTest"
                   xmlns="http://www.w3.org/2001/XMLSchema">
                   <element name="EncryptedPasswordTestProcessRequest">
                        <complexType>
                             <sequence>
                                  <element name="username" type="string"/>
                             </sequence>
                        </complexType>
                   </element>
                   <element name="EncryptedPasswordTestProcessResponse">
                        <complexType>
                             <sequence>
                                  <element name="password" type="string"/>
                             </sequence>
                        </complexType>
                   </element>
                   <element name="EncryptedPasswordTestProcessError">
                        <complexType>
                             <sequence>
                                  <element name="code" type="string"/>
                                  <element name="description" type="string"/>
                             </sequence>
                        </complexType>
                   </element>
              </schema>
         </types>
         <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
         MESSAGE TYPE DEFINITION - Definition of the message types used as
         part of the port type defintions
         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
         <message name="EncryptedPasswordTestRequestMessage">
              <part name="payload" element="client:EncryptedPasswordTestProcessRequest"/>
         </message>
         <message name="EncryptedPasswordTestResponseMessage">
              <part name="payload" element="client:EncryptedPasswordTestProcessResponse"/>
         </message>
         <message name="EncryptedPasswordTestErrorMessage">
              <part name="payload" element="client:EncryptedPasswordTestProcessError"/>
         </message>
         <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
         PORT TYPE DEFINITION - A port type groups a set of operations into
         a logical service unit.
         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
         <!-- portType implemented by the EncryptedPasswordTest BPEL process -->
         <portType name="EncryptedPasswordTest">
              <operation name="process">
                   <input message="client:EncryptedPasswordTestRequestMessage" />
                   <output message="client:EncryptedPasswordTestResponseMessage"/>
    <fault name="EncryptedPasswordTestError" message="client:EncryptedPasswordTestErrorMessage"/>
              </operation>
         </portType>
         <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
         PARTNER LINK TYPE DEFINITION
         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
         <plnk:partnerLinkType name="EncryptedPasswordTest">
              <plnk:role name="EncryptedPasswordTestProvider">
                   <plnk:portType name="client:EncryptedPasswordTest"/>
              </plnk:role>
         </plnk:partnerLinkType>
    </definitions>
    And the WSDL produced when you access the ws endpoint is:
    <?xml version="1.0" encoding="UTF-8"?>
    <definitions
    name="EncryptedPasswordTest"
    targetNamespace="http://xmlns.oracle.com/EncryptedPasswordTest"
    xmlns="http://schemas.xmlsoap.org/wsdl/"
    xmlns:tns="http://xmlns.oracle.com/EncryptedPasswordTest"
    xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
    xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
    xmlns:client="http://xmlns.oracle.com/EncryptedPasswordTest"
    >
    <types>
    <schema attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://xmlns.oracle.com/EncryptedPasswordTest"
    xmlns="http://www.w3.org/2001/XMLSchema">
    <element name="EncryptedPasswordTestProcessRequest">
    <complexType>
    <sequence>
    <element name="username" type="string"/>
    </sequence>
    </complexType>
    </element>
    <element name="EncryptedPasswordTestProcessResponse">
    <complexType>
    <sequence>
    <element name="password" type="string"/>
    </sequence>
    </complexType>
    </element>
    <element name="EncryptedPasswordTestProcessError">
    <complexType>
    <sequence>
    <element name="code" type="string"/>
    <element name="description" type="string"/>
    </sequence>
    </complexType>
    </element>
    </schema>
    </types>
    <message name="EncryptedPasswordTestErrorMessage">
    <part name="payload" element="tns:EncryptedPasswordTestProcessError"/>
    </message>
    <message name="EncryptedPasswordTestResponseMessage">
    <part name="payload" element="tns:EncryptedPasswordTestProcessResponse"/>
    </message>
    <message name="EncryptedPasswordTestRequestMessage">
    <part name="payload" element="tns:EncryptedPasswordTestProcessRequest"/>
    </message>
    <portType name="EncryptedPasswordTest">
    <operation name="process">
    <input message="tns:EncryptedPasswordTestRequestMessage"/>
    <output message="tns:EncryptedPasswordTestResponseMessage"/>
    <fault name="EncryptedPasswordTestError" message="tns:EncryptedPasswordTestErrorMessage"/>
    </operation>
    </portType>
    <binding name="EncryptedPasswordTestBinding" type="tns:EncryptedPasswordTest">
    <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
    <operation name="process">
    <soap:operation style="document" soapAction="process"/>
    <input>
    <soap:body use="literal"/>
    </input>
    <output>
    <soap:body use="literal"/>
    </output>
    <fault>
    <soap:fault name="EncryptedPasswordTestError" use="literal" encodingStyle=""/>
    </fault>
    </operation>
    </binding>
    <service name="EncryptedPasswordTest">
    <port name="EncryptedPasswordTestPort" binding="tns:EncryptedPasswordTestBinding">
    <soap:address location="http://bpel5.lon.domroot.com:7779/orabpel/default/EncryptedPasswordTest/1.0"/>
    </port>
    </service>
    <plnk:partnerLinkType name="EncryptedPasswordTest">
    <plnk:role name="EncryptedPasswordTestProvider">
    <plnk:portType name="tns:EncryptedPasswordTest"/>
    </plnk:role>
    </plnk:partnerLinkType>
    </definitions>

  • How to generate a Web Service Proxy for an ESB Routing Service?

    Hi,
    I have a SOAP service behind an ESB Routing Service. I am aware that i can call this ESB Service at the SOAP endpoint which can be found at the ESB Console after registration.
    But, i want to invoke this service using a Web Service Proxy. My understanding is that, i need to use the WSDL generated for the ESB Routing Service to generate the proxy. The WSDL which can be seen in JDeveloper does not have any soap bindings and hence the tool does not allow me to generate any proxy.
    Also, the two WSDLs whose URLs can be found at the ESB Console do not have the soap endpoint properties.
    Can someone help me out on the same?
    Thanks and regards,
    Priya.

    Priya,
    Just take the SOAP endpoint and suffix it with a ?wsdl
    Even the Concrete WSDL endpoint should be having a SOAP endpoint.
    HTH
    Uday

  • Have problem when generate Web Service from bapi function

    Dear all,
    Please kindly help me about generating Web Service from BAPI function, It does not success only this attached function.
    I have done so many function without any problems.
    I found 1 case that I use specific variable to be an import/ export then, it can't create as well.
    As for this one, I try so many changes but I can't success it as well.
    This is my function on R/3 4.6C, Dot net connector 2.0, Dot net Frame Work 1.1.
    FUNCTION Z_BAPI_ATTACHMENT_CREATE.
    ""Local interface: Type: Remote-enabled module
    *"  IMPORTING
    *"     VALUE(P_BOTYPE) LIKE  BORIDENT-OBJTYPE
    *"     VALUE(P_BO_ID) LIKE  BORIDENT-OBJKEY
    *"     VALUE(P_MSGTYP) LIKE  SOFM-DOCTP
    *"     VALUE(P_DOCTY) LIKE  BORIDENT-OBJTYPE
    *"     VALUE(P_RELTYP) LIKE  BRELTYP-RELTYPE
    *"     VALUE(P_FNAME) LIKE  RLGRAP-FILENAME
    *"     VALUE(P_OBJDES) TYPE  SO_OBJ_DES
    *"  EXPORTING
    *"     VALUE(RETURNMESSAGE) TYPE  CHAR50
    INCLUDE : <cntn01>.
    P_BOTYPE  TYPE  BORIDENT-OBJTYPE DEFAULT 'BUS2105'
    P_BO_ID   TYPE  BORIDENT-OBJKEY
    P_MSGTYPE TYPE  SOFM-DOCTP DEFAULT 'URL'
    P_DOCTY   TYPE  BORIDENT-OBJTYPE DEFAULT 'MESSAGE'
    P_RELTYP  TYPE  BRELTYP-RELTYPE DEFAULT 'ATTA'
    P_FNAME   TYPE  RLGRAP-FILENAME
    P_OBJDES  TYPE  SO_OBJ_DES
    TYPES: BEGIN OF ty_message_key,
    foltp TYPE so_fol_tp,
    folyr TYPE so_fol_yr,
    folno TYPE so_fol_no,
    doctp TYPE so_doc_tp,
    docyr TYPE so_doc_yr,
    docno TYPE so_doc_no,
    fortp TYPE so_for_tp,
    foryr TYPE so_for_yr,
    forno TYPE so_for_no,
    END OF ty_message_key.
    DATA : lv_message_key TYPE ty_message_key.
    DATA : lo_message TYPE swc_object.
    DATA : lt_doc_content TYPE STANDARD TABLE OF soli-line
    WITH HEADER LINE.
    First derive the Attachment's ( MESSAGE )document type.
    p_docty = 'MESSAGE'.
    CASE p_reltyp.
    In case of URls
      WHEN 'URL'.
        p_msgtyp = 'URL'.
    In case of Notes / Private Notes
      WHEN 'NOTE' OR 'PNOT'.
        p_msgtyp = 'RAW'.
      WHEN 'ATTA'.
    Take given parameter e.g. 'DOC', 'PDF' etc.
    P_MSGTYP = 'EXT'.
      WHEN OTHERS.
    ....exit
        EXIT.
    ENDCASE.
    Create an initial instance of BO 'MESSAGE' - to call the
    instance-independent method 'Create'.
    swc_create_object lo_message 'MESSAGE' lv_message_key.
    define container to pass the parameter values to the method call
    in next step.
    swc_container lt_message_container.
    Populate container with parameters for method
    swc_set_element lt_message_container 'DOCUMENTTITLE' p_objdes.
    swc_set_element lt_message_container 'DOCUMENTLANGU' 'E'.
    swc_set_element lt_message_container 'NO_DIALOG' 'X'.
    swc_set_element lt_message_container 'DOCUMENTNAME' p_docty.
    swc_set_element lt_message_container 'DOCUMENTTYPE' p_msgtyp.
    In case of URLs..it should be concatenated with &KEY& in the begining.
    CASE p_msgtyp.
      WHEN 'URL'.
      lt_doc_content = '&KEY&http://www.rmtiwari.com' .
        CONCATENATE '&KEY&' p_fname INTO lt_doc_content.
        APPEND lt_doc_content.
    In case of Notes or Private Notes, get the data from files on appl
    server or from wherever(? - remember background).
      WHEN 'RAW'.
        lt_doc_content = p_fname.
        APPEND lt_doc_content.
    In case of PC File attachments
      WHEN OTHERS.
        OPEN DATASET p_fname FOR INPUT IN BINARY MODE.
        IF sy-subrc EQ 0.
          DO.
            READ DATASET p_fname INTO lt_doc_content.           "2 of 27
            IF sy-subrc EQ 0.
              APPEND lt_doc_content.
            ELSE.
              EXIT.
            ENDIF.
          ENDDO.
          CLOSE DATASET p_fname.
        ENDIF.
    ENDCASE.
    'DocumentContent' is a multi-line element ( itab ).
    swc_set_table lt_message_container 'DocumentContent' lt_doc_content.
    Size is required in case of File attachments
    DATA : lv_doc_size TYPE i.
    DATA : l_file_lines TYPE i.
    DESCRIBE TABLE lt_doc_content LINES l_file_lines.
    READ TABLE lt_doc_content INDEX l_file_lines.
    lv_doc_size = ( 255 * ( l_file_lines - 1 ) ) +
    STRLEN( lt_doc_content ).
    swc_set_element lt_message_container 'DOCUMENTSIZE' lv_doc_size .
    Refresh to get the reference of create 'MESSAGE' object for attachment
    swc_refresh_object lo_message.
    swc_call_method lo_message 'CREATE' lt_message_container.
    Get Key of new object
    swc_get_object_key lo_message lv_message_key.
    Now we have attachment as a business object instance. We can now
    attach it to our main business object instance.
    Create main BO object_a
    data: LO_IS_OBJECT_A type SIBFLPORB. "type SIBFLPORB is unknown, so I
    DATA: lo_is_object_a TYPE borident.
    lo_is_object_a-objkey = p_bo_id.
    lo_is_object_a-objtype = p_botype.
    LO_IS_OBJECT_A-CATID = 'BO'.
    Create attachment BO object_b
    data: LO_IS_OBJECT_B type SIBFLPORB. "type SIBFLPORB is unknown
    DATA: lo_is_object_b TYPE borident.
    lo_is_object_b-objkey = lv_message_key.
    lo_is_object_b-objtype = p_docty.
    LO_IS_OBJECT_B-CATID = 'BO'.
    *TRY.
    *CALL METHOD CL_BINARY_RELATION=&gtCREATE_LINK
    EXPORTING
    IS_OBJECT_A = LO_IS_OBJECT_A
    IS_OBJECT_B = LO_IS_OBJECT_B
    IP_RELTYPE = P_RELTYP.
    CALL FUNCTION 'BINARY_RELATION_CREATE'
      EXPORTING
        obj_rolea    = lo_is_object_a
        obj_roleb    = lo_is_object_b
        relationtype = p_reltyp
      EXCEPTIONS
        OTHERS       = 1.
    Check if everything OK...who cares!!
    COMMIT WORK.
    if sy-subrc = 0.
      RETURNMESSAGE = 'S-Success'.
    else.
      RETURNMESSAGE = 'E-Error'.
    endif.
    ENDFUNCTION.
    Thanks in advance,
    Benjawan
    Edited by: Nitipat Chadchavalpanichaya on Oct 20, 2008 9:02 AM

    There is no any error message show up. It just the class
    Z_BAPI_ATTACHMENT_CREATE  doesn't create autometically as normal. I showed you as below.
    That means I can't call class z_bapi_attachment_create.
    ' <autogenerated>
    '     This code was generated by a SAP. NET Connector Proxy Generator Version 2.0
    '     Created at 21/10/2551
    '     Created from Windows
    '     Changes to this file may cause incorrect behavior and will be lost if
    '     the code is regenerated.
    ' </autogenerated>
    Imports System
    Imports System.Text
    Imports System.Collections
    Imports System.ComponentModel
    Imports System.Runtime.InteropServices
    Imports System.Xml.Serialization
    Imports System.Web.Services
    Imports System.Web.Services.Description
    Imports System.Web.Services.Protocols
    Imports SAP.Connector
      '@ <summary>
      '@ Client SAP proxy class
      '@ </summary>
      <WebServiceBinding(Name:="dummy.Binding", Namespace:="urn:sap-com:document:sap:rfc:functions")> _
      Public Class PRAttachment
        Inherits SAPClient
        '@ <summary>
        '@ Initializes a new PRAttachment.
        '@ </summary>
        Public Sub New()
        End Sub
        '@ <summary>
        '@ Initializes a new PRAttachment with a new connection based on the specified connection string.
        '@ </summary>
        '@ <param name="connectionString">A connection string (e.g. RFC or URL) specifying the system where the proxy should connect to.</param>
        Public Sub New(ByVal ConnectionString As String)
          MyBase.New(ConnectionString)
        End Sub
        '@ <summary>
        '@ Initializes a new PRAttachment and adds it to the given container.
        '@ This allows automated connection mananged by VS component designer:
        '@ If container is disposed, it will also dispose this SAPClient instance,
        '@ which will dispose a contained connection if needed.
        '@ </summary>
        '@ <param name="Cont">The container where the new SAPClient instance is to be added.</param>
        Public Sub New(ByVal Cont As Container)
          MyBase.New(Cont)
        End Sub
      End Class

Maybe you are looking for

  • Dynamic Tree and TreeNode Issue

    I am using JSC2 (060120) on Win2K pro, exporting the WAR and running in JBoss 4.0.3 running under JDK 1.5.0_04. I am trying to dynamically build a tree as the user clicks on nodes and am not having success following the example at http://developers.s

  • Using string data as html

    I have a javabean that uses a collection to set my nav bars depending on what section of the site you are in. I have a column in my collection that has html code as to what to show after the link (an arro, line, etc). When I display this on the page,

  • SD Queries

    I need guidance related to below issues...request you to reply me at the earliest.. 1)Fields in Customer master recoreds are not populating properly while taking  printouts... what camn be wrong in configuration/printer settings....it is basis settin

  • Oo abap to get the fldcat in class

    HI friends, i have to know is their any class available to generate field catalog as like reuse_alv_fieldcataloge_merge in alv.

  • How to add different sections in the documentation of objects

    Hi all, I started to document my scenarios via the "build in documentation functionality". It works well for a short overlook, define contact persons, etc. I could also choose a section, but the only value that I can select is u201CUseu201D. How can