CustomizeWSDL, importing xsd in wsdl file.

We have requirement of importing centralized XSD files in WSDL,
1) based on best practices I believe we should do following:
<types>
<schema xmlns="http://www.w3.org/2001/XMLSchema" >
<import namespace="http://xmlns.oracle.com/HelloWorld" schemaLocation="http://localhost:7777/xsd/HelloWorld.xsd"/>
</schema>
</types>
2) Now, for life cycle management I thought of writing custom Ant task, but I believe customizeWSDL should take care of it,
I tried,
<customizeWSDL inFile="${process.dir}/bpel/WriteToMyFile.wsdl" outFile="${process.dir}/bpel/WriteToMyFile.wsdl">
<wsdlImport namespace="http://xmlns.oracle.com/HelloWorld" locationURI="http://${http.hostname}:${http.port}/xsd/HelloWorld.xsd" />
</customizeWSDL>
but it didn't work. I know it is for wsdl import, but based document it says XSD and WSDL import are both supported in customizeWSDL.
I looked at the source code of customizeWSDL as well, it doesn't look like there is any special xsdImport child tag inside customizeWSDL.
Can anybody please help me here??
Thanks a lot!
Chintan

Hi Ninad,
WS Policy is  Standard that is used by any intregration tools while generating the .WSDL's, If the 3 party systems cannot understand WS Policy, you can easily remove them by using tools like XML notepad, XML spy in deleting them and feed in your WSDL files to the 3rd party systems.
Hope this clears your issue.
Thanks,
KishoreJ.

Similar Messages

  • Consuming URL renames XSD and WSDL files in OSB

    We try to define a proxy service in the OSB 11g by consuming an URL.
    We have all our WSDLs, XSDs etc online available, that is references like import of include in a WSDL uses URLs to identify other WSDLs or XSDs. In fact a webservice has a concrete WSDL which imports an abstract WSDL. The abstract WSDL imports XSD's. The XSD's file can import another XSD's as well. It is more or less a tree structure of XML documents.
    When we try to define a proxy or business service on the concrete WSDL in Eclipse by consuming the URL ending on ?wsdl, all meaningfull names of XSD's are replaced by generated names i.e. common.xsd becomes xml_1233.xsd. And all URL references are replaced by file references. The depencency tree is preserved, everthing is still valid however the names are no longer human readable.
    Is there any way to preserve the filenames of XML documents?
    With kinds regards,
    Jornica

    Hi Anuj,
    I followed this link to create the MDS connection and local MDS repository, should I create an empty composite project and place the
    zip file of my xsd's in this and bundle that in to an MAR file? Are there any documents that talks about MAR creation?
    Thanks,
    Jai.

  • Getting response object field value as null when importing xsd file in wsdl

    I have created a java webservice using X-Fire 1.2.6 framework and deployed on Tomcat 6.0 server. The response of the service is a java object named LoginDetail.
    Inorder to reuse the basic elements and types we have defined them in a separate Types.xsd file which have been imported in the WSDl file using xsd:import by giving the path to the xsd file.
    Below you can see the portion of the wsdl file
         <wsdl:types>
              <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
                   attributeFormDefault="qualified" elementFormDefault="qualified"
                   targetNamespace="http://webservices.gtl.de/xsd">
                   <xsd:import namespace="http://webservices.gtl.de/xsd"
                        schemaLocation="file:///D:/wsdl/LoginTypes.xsd"></xsd:import>
              </xsd:schema>
         </wsdl:types>
    After deploying the application on Tomcat I could access the WSDL using a web browser and after that I could successfully generate webservice client code using using XFire wsgen ant build.
    But when tried to call the service the fields of the response object(in my case it is LoginDetail object) returns null.
    Follwing are the main class used for running the client and the output received as webservice respone.
    Main class
    public static void main(String[] args) {
    CCLoginNewClient client = new CCLoginNewClient();
    CCLoginNewPortType service     = client.getCCLoginNewHttpPort();                         
    LoginDetail loginDetail = service.getLogin("CCLoginNew", "DE", "DE", "100", "0", "CC", "15","9344");
    System.out.println("service got in response : "+loginDetail.getService());                    
    Output
    service got in response : null
    is this the right way to import an xsd file in a wsdl file?
    Any input would be appreciated!
    Thanks in advance

    PramodDas wrote:
    Output
    service got in response : nullCheck with Apache TCPMonitor what response you are receiving from web service.
    is this the right way to import an xsd file in a wsdl file?Make sure that you really need import, not the include. However, I guess it has nothing do with the actual issue. It just to make sure that you are using right option.

  • Problem in Importing wsdl file in IR

    Hi ,
    I am doing soap receiver scenario.I had a wsdl generated from .Net and i imported the wsdl , i am not able to find teh methods in the external defination ,
    Wat wil be theproblem.
    Regards,
    Shaik

    Hi,
    problems occur during the import of xsd and wsdl files as external definitions if the target namespace contains more than 60 characters. The system does not issue any error message, however, the list of the
    recognized messages remains empty.
    Solution;
    For a wsdl file, you simply need to edit the target namespace manually ( attribute "targetNamespace" of the wsdl:definitions element) and reduce the number of characters to less than 60. For the structure of the extracted messages (exception: import assuming rpc style binding, see below), this target namespace does not have any importance.
    Regards,
    Jayasimha Jangam

  • Netbeans creating wsdl file having message with more than one part...

    Hi,
    I am using netbeans 6.0.1. I made an xml schema, then I wanted to make an wsdl that uses that schema.
    I wanted to put in a message more parts(3), and it would not let me. Then, i made the message with just one part, and added the other parts afterwards.
    But now, when I try to make a web service from that wsdl, it says that there is no service in the specified wsdl file.
    And if i let that message with just one part, it will make the Web Service.
    here is the xml schema and the wsdl file:
    XML Schema:
    <?xml version="1.0" encoding="UTF-8"?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    targetNamespace="http://xml.netbeans.org/schema/Abruf38"
    xmlns:tns="http://xml.netbeans.org/schema/Abruf38"
    elementFormDefault="qualified">
    <xsd:complexType name="FormRequest">
    <xsd:sequence>
    <xsd:element name="newRequest" type="xsd:boolean"/>
    <xsd:element name="requestNumber" type="xsd:int"/>
    <xsd:element name="vehicleClass" type="xsd:string"/>
    <xsd:element name="vehiclesNumber" type="xsd:int"/>
    <xsd:element name="prefferedType" type="xsd:string"/>
    <xsd:element name="kombi" type="xsd:boolean"/>
    <xsd:element name="usageMission" type="xsd:boolean"/>
    <xsd:element name="usageEducation" type="xsd:boolean"/>
    <xsd:element name="usageGeneral" type="xsd:boolean"/>
    <xsd:element name="usageOthers" type="xsd:string"/>
    <xsd:element name="eqVehicle" type="xsd:boolean"/>
    <xsd:element name="eqDangerous" type="xsd:boolean"/>
    <xsd:element name="eqPlaneSpriegel" type="xsd:boolean"/>
    <xsd:element name="eqBegrstll" type="xsd:boolean"/>
    <xsd:element name="eqMSitzBTruck" type="xsd:boolean"/>
    <xsd:element name="eqVerzurrAusst" type="xsd:boolean"/>
    <xsd:element name="eqOthers" type="xsd:string"/>
    <xsd:element name="bringService" type="xsd:boolean"/>
    <xsd:element name="holService" type="xsd:boolean"/>
    <xsd:element name="chauffService" type="xsd:boolean"/>
    <xsd:element name="otherService1" type="xsd:string"/>
    <xsd:element name="otherService1Chk" type="xsd:boolean"/>
    <xsd:element name="otherService2" type="xsd:string"/>
    <xsd:element name="otherService2Chk" type="xsd:boolean"/>
    <xsd:element name="otherService3" type="xsd:string"/>
    <xsd:element name="otherService3Chk" type="xsd:boolean"/>
    <xsd:element name="activity" type="xsd:string"/>
    <xsd:element name="costPayer" type="xsd:string"/>
    <xsd:element name="costCenter" type="xsd:string"/>
    <xsd:element name="vehicleCost" type="xsd:float"/>
    <xsd:element name="chauffServiceCost" type="xsd:float"/>
    <xsd:element name="holBringServiceCost" type="xsd:float"/>
    <xsd:element name="totalCost" type="xsd:float"/>
    <xsd:element name="tripPurpose" type="xsd:string"/>
    <xsd:element name="fixTermin" type="xsd:boolean"/>
    <xsd:element name="justificationFix" type="xsd:string"/>
    <xsd:element name="requestID" type="xsd:string"/>
    <xsd:element name="rentalPeriod" type="tns:RentalPeriod"/>
    <xsd:element name="carPool" type="tns:CarPool"/>
    </xsd:sequence>
    </xsd:complexType>
    <xsd:complexType name="CarPool">
    <xsd:sequence>
    <xsd:element name="poolID" type="xsd:string"/>
    <xsd:element name="poolName" type="xsd:string"/>
    <xsd:element name="orgNumber" type="xsd:string"/>
    <xsd:element name="vehicle" maxOccurs="unbounded" type="tns:Vehicle"/>
    </xsd:sequence>
    </xsd:complexType>
    <xsd:complexType name="RentalPeriod">
    <xsd:sequence>
    <xsd:element name="rentalPeriodID" type="xsd:string"/>
    <xsd:element name="startDate" type="xsd:date"/>
    <xsd:element name="endDate" type="xsd:date"/>
    <xsd:element name="startTime" type="xsd:time"/>
    <xsd:element name="endTime" type="xsd:time"/>
    <xsd:element name="startLocation" type="xsd:string"/>
    <xsd:element name="endLocation" type="xsd:string"/>
    </xsd:sequence>
    </xsd:complexType>
    <xsd:complexType name="Vehicle">
    <xsd:sequence>
    <xsd:element name="vehicleID" type="xsd:string"/>
    <xsd:element name="vehicleClass" type="xsd:string"/>
    <xsd:element name="vehicleRegisterNo" type="xsd:int"/>
    <xsd:element name="vehicleType" type="xsd:string"/>
    <xsd:element name="seatsNumber" type="xsd:int"/>
    <xsd:element name="cost" type="xsd:float"/>
    <xsd:element name="available" type="xsd:boolean"/>
    </xsd:sequence>
    </xsd:complexType>
    <xsd:complexType name="Contact">
    <xsd:sequence>
    <xsd:element name="contactID" type="xsd:string"/>
    <xsd:element name="contactName" type="xsd:string"/>
    <xsd:element name="telNumber" type="xsd:int"/>
    <xsd:element name="faxNumber" type="xsd:int"/>
    <xsd:element name="loNo" type="xsd:string"/>
    </xsd:sequence>
    </xsd:complexType>
    <xsd:complexType name="Person">
    <xsd:sequence>
    <xsd:element name="personID"/>
    <xsd:element name="department" type="xsd:string"/>
    <xsd:element name="serviceNumber" type="xsd:int"/>
    <xsd:element name="contact" type="tns:Contact"/>
    </xsd:sequence>
    </xsd:complexType>
    <xsd:complexType name="Department">
    <xsd:sequence>
    <xsd:element name="departmentID" type="xsd:string"/>
    <xsd:element name="fundsDepartment" type="xsd:string"/>
    <xsd:element name="mvwdst" type="xsd:int"/>
    <xsd:element name="distributionNumber" type="xsd:int"/>
    <xsd:element name="contact" type="tns:Contact"/>
    </xsd:sequence>
    </xsd:complexType>
    <xsd:element name="formRequestElement" type="tns:FormRequest"/>
    <xsd:element name="personElement" type="tns:Person"/>
    <xsd:element name="departmentElement" type="tns:Department"/>
    <xsd:element name="vehicle" type="tns:Vehicle"/>
    <xsd:element name="loadFormReturn" type="xsd:boolean"/>
    <xsd:element name="editFormReturn" type="xsd:boolean"/>
    </xsd:schema>
    Wsdl File:
    <?xml version="1.0" encoding="UTF-8"?>
    <definitions name="userWS" targetNamespace="http://j2ee.netbeans.org/wsdl/userWS"
    xmlns="http://schemas.xmlsoap.org/wsdl/"
    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ns="http://xml.netbeans.org/schema/Abruf38" xmlns:plnk="http://docs.oasis-open.org/wsbpel/2.0/plnktype" xmlns:tns="http://j2ee.netbeans.org/wsdl/userWS" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">
    <types>
    <xsd:schema targetNamespace="http://j2ee.netbeans.org/wsdl/userWS">
    <xsd:import namespace="http://xml.netbeans.org/schema/Abruf38" schemaLocation="Abruf38.xsd"/>
    </xsd:schema>
    </types>
    <message name="loadFormRequest">
    <part name="formRequest" element="ns:formRequestElement"/>
    <part name="person" element="ns:personElement"/>
    <part name="department" element="ns:departmentElement"/>
    </message>
    <message name="loadFormReply">
    <part name="retVal" element="ns:loadFormReturn"/>
    </message>
    <portType name="userWSPortType">
    <operation name="loadForm">
    <input name="input1" message="tns:loadFormRequest"></input>
    <output name="output1" message="tns:loadFormReply"/>
    </operation>
    </portType>
    <binding name="userWSBinding" type="tns:userWSPortType">
    <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
    <operation name="loadForm">
    <soap:operation/>
    <input name="input1">
    <soap:body use="literal"/>
    </input>
    <output name="output1">
    <soap:body use="literal"/>
    </output>
    </operation>
    </binding>
    <service name="userWSService">
    <port name="userWSPort" binding="tns:userWSBinding">
    <soap:address location="http://localhost:18181/userWSService/userWSPort"/>
    </port>
    </service>
    <plnk:partnerLinkType name="userWS1">
    <!-- A partner link type is automatically generated when a new port type is added. Partner link types are used by BPEL processes.
    In a BPEL process, a partner link represents the interaction between the BPEL process and a partner service. Each partner link is associated with a partner link type.
    A partner link type characterizes the conversational relationship between two services. The partner link type can have one or two roles.-->
    <plnk:role name="userWSPortTypeRole" portType="tns:userWSPortType"/>
    </plnk:partnerLinkType>
    </definitions>
    The message that Netbeans says when trying to put more parts to the message is:
    WS-I Basic Profile Rule R2210: If a document-literal binding in a DESCRIPTION does not specify the parts attribute on a soapbind:body element, the corresponding abstract wsdl:message MUST define zero or one wsdl:parts.
    Please...I am desperate, cause I am pressed by time!
    Can anyone tell me how can I make it work. Cause it is very common to use a Web service operation that has more than ONE parameter.
    I am waiting for your replys!

    Hi,
    Change the <soap:binding style="document"... to <soap:binding style="rpc"... and see if that works.
    I'm not sure how to get <soap:binding style="document"... working yet - I'm not that experienced in web services yet.
    Hope this helps and is not too late.
    Regards,
    Greg Nye

  • Troubleshooting Custom WSDL files and duplication

    I am attempting to provide a web service for my company's CRM with Siebel, requiring multiple types(Specifically: Lead, Campaign, Contact, Activity).
    However, when I import the custom WSDL files for these into my C# project, there are roughly alot of build errors due to the duplication of partial classes(and the fields therein)
    Is there anyway around this besides manually going through the duplicates and removing them?

    Thanks for the response.
    I have it working now.
    I used wsdl.exe to create .cs files and imported those.
    Each .cs file has its own namespace(I just used the class name again).
    So instead of calling Campaign.CampaignInsert(CampaignWS_CampaignInsert_Input), its Campaign.Campaign.CampaignInsert(Campaign.CampaignWS_CampaignInsert_Input)
    and so on for the other classes/methods.

  • How to use wscompile to generate code using a WSDL file?

    I am working with JAX-RPC of Java Web Service ver: 1.1. I am intrested in making the WSDL file first and generating Java code from the WSDL file. On the following link:
    http://java.sun.com/webservices/docs/1.1/tutorial/doc/JAXRPC6.html#wp80094
    it says that wscompile can generate code using a WSDL file..:
    <quote>
    Table 11-3 wscompile Options
    -import : read a WSDL file, generate the service's RMI interface and a template of the class that implements the interface
    </quote>
    and the wscompile software says this:
    <quote>
    C:\>wscompile
    -import : generate interfaces and value types only
    </quote>
    can anyone tell me how to generated Java code from a WSDL file. As in, make the WSDL file (e.g. using XMLSpy) and then use that WSDL generate Java code.
    Thanks

    I'm trying to generate code using wscompile under the struction in JAXRPC_Tutorial.pdf.
    I issued the following command:
    wscompile.sh -keep -gen:client -f:wsi -verbose config.xml
    But I met with the following warning and I cann't find the produced java code, who know why? Thanks in advance!
    warning: ignoring SOAP port "EmployeeDBPort": unrecognized transport
    warning: Service "EmployeeDatabase" does not contain any usable ports
    the config.xml file is:
    <?xml version="1.0" encoding="UTF-8"?>
    <configuration
    xmlns="http://java.sun.com/xml/ns/jax-rpc/ri/config">
    <wsdl name="EmployeeDBService"
    location="EmployeeDB.wsdl"
    packageName="com.sun.xml.rpc.xml.EmployeeDB">
    </wsdl>
    </configuration>

  • Oracle text search not working for  WSDL files

    I have a table (resources) with blob data type column (xml_data) and I've created context type index on that column. I've XSD and WSDL files stored in that blob column.
    I can search XSD and XML files with a query with contains operator. But any search on the words from wsdl file returns zero results.I am not able to perform search on wsdl file.
    Please advise me whether oracle text can work for WSDL files also ?
    Query details
    ===========
    create index myIndex on resources (xml_data) indextype is ctxsys.context;
    select * from resources where contains(xml_data, 'searchword') > 0
    Thanks a lot,
    Santhi

    Even though it isn't listed specifically, I can't see why it wouldn't work. The WSDL file should be a simple XML file, so in theory it shouldn't be any different to Oracle Text than the XML file that you loaded and searched successfully. Did you get any errors during indexing, and what do your tokens look like in the DR$MYINDEX$I.TOKEN_TEXT column?
    Do you have a mini test case that didn't work for you? Perhaps we could play with it a bit.
    Long term you might want to consider using section groups so that you can search "within" tags.
    -Ron

  • PI 7.1: Importing a wsdl file with references to other xsd files

    Hi Experts,
    I am trying to import a wsdl file that has got references to other xsd files. When i do this with SOAP UI, i can get the full message structure for the other xsd files. But when i try to import the same wsdl in the ESR, i only get to the messages and not the referenced xsd.
    Any ideas!
    Thank you in Advance,
    Danny

    Hi,
    First convert your main WSDL in to XSD,use Stylus or any XML editors to convert the same,thecn check the genarated XSD refering sun XSD tsrutures.then zip the all xsd in to one File and import in PI,then select you main xsd in the folder,and select root element.
    Normally withour converting in to XSD only if you group al import it in to PI,it wil work.
    or
    if you have some good knowledge about XSD then convert WSDL in to XSD and remove referece tags and include XSD content of sub xsds in to main XSD,and validate that one,and imnprt one XSD.
    Regards,
    Raj

  • Import WSDL file along with XSD

    Hi,
    I have a WSDL file which has complex Data types (abc.wsdl). This complex data types are defined in the XSD file (abc-data.xsd).
    If I just import WSDL file in ED I am unable to find the Complex Data types in Message Mapping.
    How can I use the XSD file along with the WSDL file? Is there any source path as to give or what?
    Could you please help me out…?

    first i will tell how my wsdl file is defined
    <xs:element name="authInfo" type="<b>xx:AuthInfo</b>">                                   <xs:annotation>                              <xs:documentation xml:lang="en">                                   Authentication information                         </xs:documentation>                    </xs:annotation>                              </xs:element>
    and in my xsd file for xx:AuthInfo
    <xs:complexType name="AuthInfo">
              <xs:sequence>
                   <xs:element name="acctName" type="tns:CustName">
                        <xs:annotation>
                             <xs:documentation xml:lang="en">
                             account name.
                        </xs:documentation>
                        </xs:annotation>
                   </xs:element>
                   <xs:element name="password" type="tns:AcctPswd">
                        <xs:annotation>
                             <xs:documentation xml:lang="en">
                            Specify the password                    </xs:documentation>
                        </xs:annotation>
                   </xs:element>
              </xs:sequence>
         </xs:complexType>
    when i import wsdl file in Ed i will get two inputs there but only one as "AuthInfo"
    but "AuthInfo" has two inputs.
    this is how my Target Message Look like
    Tree          Occurences          Type
    authInfo     1..1                      xx:AuthInfo
    i hope i have cleared u..

  • To Import XSD file along with WSDL file in ED

    Dear All,
    I am doing a scenario web service1 —XI—RFC—web service2. Web service1 sends request to XI and XI sends to RFC and RFC response to web service2 and web service2 response (acknowledge) back to XI and XI sends back to web service1.
    My client (web service2) has given me the web service (WSDL) file along with XSD file.
    In the wsdl file there are number of elements and complex types.
    <xs:element name="GetCustomer">
         <xs:complexType>
              <xs:sequence>
                   <xs:element name="authentication" type="xx:AuthInfo"/>
                   <xs:element name="CompanyName" type=" xx:AuthInfo "/>
              </xs:sequence>
         </xs:complexType>
    </xs:element>
    The type (xx:AuthInfo and xx:AuthInfo) are defined in XSD file.
    My questions are
    1)     Do I have to import the XSD file in ED or not.
    2)     How do I map this XSD
    3)     As WS1, RFC and WS2 all are synchronous MT do I have to use BPM for it.
    4)     Can some one help with any docs please..
    Thanks in advance

    Hi,
    >>Do I have to import the XSD file in ED or not
    If you are having the wSDL files then you can take the structure from there itself. Just import the wsdl files in IR. You can also use XSD.
    >>How do I map this XSD
    XSD are same as Message Types. So create a MM and choose your XSD.
    >>As WS1, RFC and WS2 all are synchronous MT do I have to use BPM for it.
    Yes you have to because you are taking the responce from RFC and going to give it to WS2.
    BPM steps:
    1) receive (open sync bridge)
    2) transformation 1
    3) send (snyc)
    4)transformation 2
    3) send (close sync bridge)
    https://weblogs.sdn.sap.com/pub/wlg/1403 [original link is broken] [original link is broken] [original link is broken] [original link is broken]
    Regards
    Suraj

  • FB3B2 unable to import WSDL files that contain XSD imports

    Much to my dismay, the new WSDL import wizard does not seem
    to work on WSDL files that import XSD files. When "Finish" is
    pressed, an error dialog states "The WSDL definition could not be
    parsed. The wizard cannot complete successfully."
    I created a sample WSDL that uses the most basic of XSD
    files to demonstrate. Remove the import line from the WSDL and it
    will import, with the line it will not.

    Hi Jeff,
    How are you specifying the WSDL URI?
    - If as an absolute path on your machine, make sure there are
    no spaces in that path – there is a known issue about path
    with spaces and WSDL with imports, and we’re on it. We tried
    out your sample WSDL this way and it works.
    - If you are specifying it as an HTTP url (accessing it over
    the Apache HTTP server, for example), the workaround is a little
    more complicated. There are indeed some unresolved issues with the
    ActionScript generator. Try putting the wsdl and xsd files inside a
    folder in the webroot, and another copy of the xsd in the webroot.
    This worked for me - the problem is about locating the imported
    document correctly: the introspection correctly uses the sibling
    xsd file, while the generator incorrectly looks for that file one
    level up. We’ll look into this and fix it.
    Please let me know if it starts working or if it still does
    not generate the ActionScript client classes. Thank you.
    Also, please be aware of another known issue about WSDL with
    imports:
    http://bugs.adobe.com/jira/browse/FB-7678
    (For WSDLs that import other documents, the cached WSDL file should
    include the content of the imported documents).
    Lacra

  • Xsl schema import from within a wsdl file

    I have a namespace conflict issue validating a bpel process.
    The message error is as follow:
    [bpelc] [Error] SMSSenderEnablerSEIWrapper.wsdl.2.wsdl:19:80: src-resolve.4.2: Error resolving component 'tns2:InvocationContext'. It was detected that 'tns2:InvocationContext' is in namespace 'http://com.osa.mdsp.enabler.ecf/SMSEnabler/V1.0/SMSSenderSEI', but components from this namespace are not referenceable from schema document 'file:/D:/home/guillaume/workspace/SMSMulticast2/services/SMSSenderEnablerSEIWrapper.wsdl.2.wsdl'. If this is the incorrect namespace, perhaps the prefix of 'tns2:InvocationContext' needs to be changed. If this is the correct namespace, then an appropriate 'import' tag should be added to 'file:/D:/home/guillaume/workspace/SMSMulticast2/services/SMSSenderEnablerSEIWrapper.wsdl.2.wsdl'.
    [bpelc] [Error] SMSSenderEnablerSEIWrapper.wsdl.2.wsdl:20:76: src-resolve.4.2: Error resolving component 'tns1:SMSMessageETO'. It was detected that 'tns1:SMSMessageETO' is in namespace 'http://com.osa.mdsp.enabler.sei.eto/SMSEnabler/V1.0/SMSSenderSEI', but components from this namespace are not referenceable from schema document 'file:/D:/home/guillaume/workspace/SMSMulticast2/services/SMSSenderEnablerSEIWrapper.wsdl.2.wsdl'. If this is the incorrect namespace, perhaps the prefix of 'tns1:SMSMessageETO' needs to be changed. If this is the correct namespace, then an appropriate 'import' tag should be added to 'file:/D:/home/guillaume/workspace/SMSMulticast2/services/SMSSenderEnablerSEIWrapper.wsdl.2.wsdl'.
    I've already seen this kind of error in other posts, but this was encountered with xsd files. In my case, I'm trying to use complexTypes defined in a schema, defined itself in a WSDL file. The needed file (SMSSenderEnablerSEI) is referenced in the bpel.xml file.
    // Here the BPEL file (SMSMulticast2.bpel)
    <pre>
    <!-- SMSMulticast2 BPEL Process [Generated by the Oracle BPEL Designer] -->
    <process name="SMSMulticast2" targetNamespace="http://com.osa.mdsp.csp.ena.smms.smsmulti/V1.0" suppressJoinFailure="yes" xmlns:tns="http://com.osa.mdsp.csp.ena.smms.smsmulti/V1.0" xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/" xmlns:bpelx="http://schemas.oracle.com/bpel/extension" xmlns:ora="http://schemas.oracle.com/xpath/extension" xmlns:nsxml0="http://com.osa.mdsp.enabler.sei/SMSEnabler/V1.0/SMSSenderSEI" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/" xmlns:nsxml1="http://com.osa.mdsp.enabler.sei/PimEnabler:DirectService/2004/V1.0">
         <!-- ================================================================= -->
         <!-- PARTNERLINKS -->
         <!-- List of services participating in this BPEL process -->
         <!-- ================================================================= -->
         <partnerLinks>
              <!--
    The 'client' role represents the requester of this service. It is
    used for callback. The location and correlation information associated
    with the client role are automatically set using WS-Addressing.
    -->
              <partnerLink name="client" partnerLinkType="tns:SMSMulticast2" myRole="SMSMulticast2Provider"/>
              <partnerLink name="SMSEnabler" partnerLinkType="nsxml0:SMSSenderEnablerRemoteLink" partnerRole="SMSSenderEnablerRemoteProvider"/>
              <partnerLink name="PIMEnabler" partnerLinkType="nsxml1:PimDirectServiceEnablerSEIImplLink" partnerRole="PimDirectServiceEnablerSEIImplProvider"/>
         </partnerLinks>
         <!-- ================================================================= -->
         <!-- VARIABLES -->
         <!-- List of messages and XML documents used within this BPEL process -->
         <!-- ================================================================= -->
         <variables>
              <!-- Reference to the message passed as input during initiation -->
              <variable name="smsmultiRequest" messageType="tns:SMSMulticast2RequestMessage"/>
              <!-- Reference to the message that will be sent back to the
    requester during callback
    -->
              <variable name="smsmultiResponse" messageType="tns:SMSMulticast2ResponseMessage"/>
              <variable name="count" type="xsd:integer"/>
              <variable name="contactRequest" messageType="nsxml1:retrieveContactRequest"/>
              <variable name="smsRequest" messageType="nsxml0:sendSMSRequest"/>
              <variable name="smsResponse" messageType="nsxml0:sendSMSResponse"/>
              <variable name="contactResponse" messageType="nsxml1:addContactResponse"/>
         </variables>
         <!-- ================================================================= -->
         <!-- ORCHESTRATION LOGIC -->
         <!-- Set of activities coordinating the flow of messages across the -->
         <!-- services integrated within this business process -->
         <!-- ================================================================= -->
         <sequence name="main">
              <!-- Receive input from requestor.
    Note: This maps to operation defined in SMSMulticast2.wsdl
    -->
              <receive name="receiveInput" partnerLink="client" portType="tns:SMSMulticast2PT" operation="process" variable="smsmultiRequest" createInstance="yes"/>
              <!-- Asynchronous callback to the requester.
    Note: the callback location and correlation id is transparently handled
    using WS-addressing.
    -->
              <assign name="setProperties">
                   <copy>
                        <from expression="5"></from>
                        <to variable="count"/>
                   </copy>
                   <copy>
                        <from variable="smsmultiRequest" part="parameter" query="/tns:SMSMulticast2Request/tns:inputMSISDN"></from>
                        <to variable="smsRequest" part="parameters" query="/nsxml0:sendSMS/nsxml0:sms/nsxml0:senderAddress"/>
                   </copy>
                   <copy>
                        <from variable="smsmultiRequest" part="parameter" query="/tns:SMSMulticast2Request/tns:inputMessage"></from>
                        <to variable="smsRequest" part="parameters" query="/nsxml0:sendSMS/nsxml0:sms/nsxml0:content"/>
                   </copy>
              </assign>
              <while name="foreach" condition="bpws:getVariableData('count') &gt; 0"><sequence><invoke name="invoke-1" partnerLink="SMSEnabler" portType="nsxml0:SMSSenderEnablerRemote" operation="sendSMS" inputVariable="smsRequest" outputVariable="smsResponse"/>
                        <assign name="decrease"><copy>
                                  <from expression="bpws:getVariableData('count') - 1"></from>
                                  <to variable="count"/>
                             </copy>
                        </assign>
                   </sequence>
              </while>
              <!--invoke name="callbackClient" partnerLink="client" portType="tns:SMSMulticast2Callback" operation="onResult" inputVariable="output"/-->
              <reply name="sendResult" partnerLink="client" portType="tns:SMSMulticast2PT" operation="process" variable="smsmultiResponse"/>
         </sequence>
    </process>
    // Here the WSDL file: SMSSenderEnablerSEIWrapper.wsdl
    <?xml version="1.0" encoding="UTF-8"?>
    <wsdl:definitions
         name="SMSSenderEnablerSEI"
    targetNamespace="http://com.osa.mdsp.enabler.sei/SMSEnabler/V1.0/SMSSenderSEI"
         xmlns="http://com.osa.mdsp.enabler.sei/SMSEnabler/V1.0/SMSSenderSEI"
         xmlns:apachesoap="http://xml.apache.org/xml-soap"
    xmlns:impl="http://com.osa.mdsp.enabler.sei/SMSEnabler/V1.0/SMSSenderSEI"
    xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
    xmlns:tns1="http://com.osa.mdsp.enabler.sei.eto/SMSEnabler/V1.0/SMSSenderSEI"
    xmlns:tns2="http://com.osa.mdsp.enabler.ecf/SMSEnabler/V1.0/SMSSenderSEI"
    xmlns:tns4="http://com.osa.mdsp.enabler.sei.exception/SMSEnabler/V1.0/SMSSenderSEI"
    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>
         <xsd:schema
              elementFormDefault="qualified"
              targetNamespace="http://com.osa.mdsp.enabler.ecf/SMSEnabler/V1.0/SMSSenderSEI"
              xmlns="http://www.w3.org/2001/XMLSchema"
              xmlns:tns="http://com.osa.mdsp.enabler.ecf/SMSEnabler/V1.0/SMSSenderSEI">
              <xsd:complexType name="InvocationContext">
              <xsd:sequence>
              <xsd:element
              maxOccurs="unbounded"
              name="properties"
              nillable="true"
              type="xsd:string"/>
              </xsd:sequence>
              </xsd:complexType>
              <xsd:complexType name="EnablerException">
              <xsd:sequence>
              <xsd:element name="errorMessage" nillable="true" type="xsd:string"/>
              <xsd:element name="errorCode" type="xsd:int"/>
              </xsd:sequence>
              </xsd:complexType>
              <xsd:element name="EnablerException" nillable="true" type="tns:EnablerException"/>
              </xsd:schema>
    <xsd:schema
    elementFormDefault="qualified"
    targetNamespace="http://com.osa.mdsp.enabler.sei/SMSEnabler/V1.0/SMSSenderSEI"
    xmlns="http://www.w3.org/2001/XMLSchema"
                   xmlns:tns1="http://com.osa.mdsp.enabler.sei.eto/SMSEnabler/V1.0/SMSSenderSEI"
                   xmlns:tns2="http://com.osa.mdsp.enabler.ecf/SMSEnabler/V1.0/SMSSenderSEI">
    <xsd:element name="sendSMS">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="ctx" nillable="true" type="tns2:InvocationContext"/>
    <xsd:element name="sms" nillable="true" type="tns1:SMSMessageETO"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    <xsd:element name="sendSMSResponse">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="sendSMSReturn" nillable="true" type="xsd:string"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    <xsd:element name="sendSMSWithNotification">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="ctx" nillable="true" type="tns2:InvocationContext"/>
    <xsd:element name="sms" nillable="true" type="tns1:SMSMessageETO"/>
    <xsd:element name="notificationURL" nillable="true" type="xsd:string"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    <xsd:element name="sendSMSWithNotificationResponse">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="sendSMSWithNotificationReturn" nillable="true" type="xsd:string"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    <xsd:element name="sendSMSToAlias">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="ctx" nillable="true" type="tns2:InvocationContext"/>
    <xsd:element name="sms" nillable="true" type="tns1:SMSMessageETO"/>
    <xsd:element name="serviceId" nillable="true" type="xsd:string"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    <xsd:element name="sendSMSToAliasResponse">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="sendSMSToAliasReturn" nillable="true" type="xsd:string"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    <xsd:element name="sendSMSWithNotificationToAlias">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="ctx" nillable="true" type="tns2:InvocationContext"/>
    <xsd:element name="sms" nillable="true" type="tns1:SMSMessageETO"/>
    <xsd:element name="serviceId" nillable="true" type="xsd:string"/>
    <xsd:element name="notificationURL" nillable="true" type="xsd:string"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    <xsd:element name="sendSMSWithNotificationToAliasResponse">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element
    name="sendSMSWithNotificationToAliasReturn"
    nillable="true"
    type="xsd:string"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    </xsd:schema>
    <xsd:schema
    elementFormDefault="qualified"
    targetNamespace="http://com.osa.mdsp.enabler.sei.eto/SMSEnabler/V1.0/SMSSenderSEI"
    xmlns="http://www.w3.org/2001/XMLSchema"
    xmlns:apachesoap="http://xml.apache.org/xml-soap"
    xmlns:impl="http://com.osa.mdsp.enabler.sei/SMSEnabler/V1.0/SMSSenderSEI"
    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
                   xmlns:tns1="http://com.osa.mdsp.enabler.sei.eto/SMSEnabler/V1.0/SMSSenderSEI"
                   xmlns:tns2="http://com.osa.mdsp.enabler.ecf/SMSEnabler/V1.0/SMSSenderSEI">
                   <xsd:complexType name="SMSMessageETO">
    <xsd:sequence>
    <xsd:element name="content" nillable="true" type="xsd:string"/>
    <xsd:element name="earliestDeliveryTime" nillable="true" type="xsd:dateTime"/>
    <xsd:element name="expiryDate" nillable="true" type="xsd:dateTime"/>
    <xsd:element name="priority" nillable="true" type="xsd:string"/>
    <xsd:element name="recipient" nillable="true" type="xsd:string"/>
    <xsd:element name="senderAddress" nillable="true" type="xsd:string"/>
    <xsd:element name="contentSentEncoding" nillable="true" type="xsd:string"/>
    <xsd:element name="smsContentSentInGsm7Bits" type="xsd:boolean"/>
    <xsd:element name="smsContentSentInUcs2" type="xsd:boolean"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:schema>
    <xsd:schema
    elementFormDefault="qualified"
    targetNamespace="http://com.osa.mdsp.enabler.sei.exception/SMSEnabler/V1.0/SMSSenderSEI"
    xmlns="http://www.w3.org/2001/XMLSchema"
    xmlns:apachesoap="http://xml.apache.org/xml-soap"
    xmlns:impl="http://com.osa.mdsp.enabler.sei/SMSEnabler/V1.0/SMSSenderSEI"
    xmlns:tns4="http://com.osa.mdsp.enabler.sei.exception/SMSEnabler/V1.0/SMSSenderSEI"
                   xmlns:tns1="http://com.osa.mdsp.enabler.sei.eto/SMSEnabler/V1.0/SMSSenderSEI"
                   xmlns:tns2="http://com.osa.mdsp.enabler.ecf/SMSEnabler/V1.0/SMSSenderSEI"
    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
    <xsd:complexType name="SMSException">
    <xsd:sequence>
    <xsd:element name="errorCode" type="xsd:int"/>
    <xsd:element name="message" nillable="true" type="xsd:string"/>
    </xsd:sequence>
    </xsd:complexType>
    <xsd:element name="SMSException" nillable="true" type="tns4:SMSException"/>
    </xsd:schema>
    </wsdl:types>
    <wsdl:message name="sendSMSRequest">
    <wsdl:part element="impl:sendSMS" name="parameters"/>
    </wsdl:message>
    <wsdl:message name="sendSMSToAliasResponse">
    <wsdl:part element="impl:sendSMSToAliasResponse" name="parameters"/>
    </wsdl:message>
    <wsdl:message name="EnablerException">
    <wsdl:part element="tns2:EnablerException" name="fault"/>
    </wsdl:message>
    <wsdl:message name="sendSMSToAliasRequest">
    <wsdl:part element="impl:sendSMSToAlias" name="parameters"/>
    </wsdl:message>
    <wsdl:message name="sendSMSWithNotificationToAliasRequest">
    <wsdl:part element="impl:sendSMSWithNotificationToAlias" name="parameters"/>
    </wsdl:message>
    <wsdl:message name="sendSMSWithNotificationToAliasResponse">
    <wsdl:part
    element="impl:sendSMSWithNotificationToAliasResponse"
    name="parameters"/>
    </wsdl:message>
    <wsdl:message name="SMSException">
    <wsdl:part element="tns4:SMSException" name="fault"/>
    </wsdl:message>
    <wsdl:message name="sendSMSWithNotificationResponse">
    <wsdl:part element="impl:sendSMSWithNotificationResponse" name="parameters"/>
    </wsdl:message>
    <wsdl:message name="sendSMSWithNotificationRequest">
    <wsdl:part element="impl:sendSMSWithNotification" name="parameters"/>
    </wsdl:message>
    <wsdl:message name="sendSMSResponse">
    <wsdl:part element="impl:sendSMSResponse" name="parameters"/>
    </wsdl:message>
    <wsdl:portType name="SMSSenderEnablerRemote">
    <wsdl:operation name="sendSMS">
    <wsdl:input message="impl:sendSMSRequest" name="sendSMSRequest"/>
    <wsdl:output message="impl:sendSMSResponse" name="sendSMSResponse"/>
    <wsdl:fault message="impl:SMSException" name="SMSException"/>
    <wsdl:fault message="impl:EnablerException" name="EnablerException"/>
    </wsdl:operation>
    <wsdl:operation name="sendSMSWithNotification">
    <wsdl:input
    message="impl:sendSMSWithNotificationRequest"
    name="sendSMSWithNotificationRequest"/>
    <wsdl:output
    message="impl:sendSMSWithNotificationResponse"
    name="sendSMSWithNotificationResponse"/>
    <wsdl:fault message="impl:SMSException" name="SMSException"/>
    <wsdl:fault message="impl:EnablerException" name="EnablerException"/>
    </wsdl:operation>
    <wsdl:operation name="sendSMSToAlias">
    <wsdl:input message="impl:sendSMSToAliasRequest" name="sendSMSToAliasRequest"/>
    <wsdl:output
    message="impl:sendSMSToAliasResponse"
    name="sendSMSToAliasResponse"/>
    <wsdl:fault message="impl:SMSException" name="SMSException"/>
    <wsdl:fault message="impl:EnablerException" name="EnablerException"/>
    </wsdl:operation>
    <wsdl:operation name="sendSMSWithNotificationToAlias">
    <wsdl:input
    message="impl:sendSMSWithNotificationToAliasRequest"
    name="sendSMSWithNotificationToAliasRequest"/>
    <wsdl:output
    message="impl:sendSMSWithNotificationToAliasResponse"
    name="sendSMSWithNotificationToAliasResponse"/>
    <wsdl:fault message="impl:SMSException" name="SMSException"/>
    <wsdl:fault message="impl:EnablerException" name="EnablerException"/>
    </wsdl:operation>
    </wsdl:portType>
    <wsdl:binding
    name="SMSSenderEnablerRemoteSoapBinding"
    type="impl:SMSSenderEnablerRemote">
    <wsdlsoap:binding
    style="document"
    transport="http://schemas.xmlsoap.org/soap/http"/>
    <wsdl:operation name="sendSMS">
    <wsdlsoap:operation soapAction=""/>
    <wsdl:input name="sendSMSRequest">
    <wsdlsoap:body use="literal"/>
    </wsdl:input>
    <wsdl:output name="sendSMSResponse">
    <wsdlsoap:body use="literal"/>
    </wsdl:output>
    <wsdl:fault name="SMSException">
    <wsdlsoap:fault name="SMSException" use="literal"/>
    </wsdl:fault>
    <wsdl:fault name="EnablerException">
    <wsdlsoap:fault name="EnablerException" use="literal"/>
    </wsdl:fault>
    </wsdl:operation>
    <wsdl:operation name="sendSMSWithNotification">
    <wsdlsoap:operation soapAction=""/>
    <wsdl:input name="sendSMSWithNotificationRequest">
    <wsdlsoap:body use="literal"/>
    </wsdl:input>
    <wsdl:output name="sendSMSWithNotificationResponse">
    <wsdlsoap:body use="literal"/>
    </wsdl:output>
    <wsdl:fault name="SMSException">
    <wsdlsoap:fault name="SMSException" use="literal"/>
    </wsdl:fault>
    <wsdl:fault name="EnablerException">
    <wsdlsoap:fault name="EnablerException" use="literal"/>
    </wsdl:fault>
    </wsdl:operation>
    <wsdl:operation name="sendSMSToAlias">
    <wsdlsoap:operation soapAction=""/>
    <wsdl:input name="sendSMSToAliasRequest">
    <wsdlsoap:body use="literal"/>
    </wsdl:input>
    <wsdl:output name="sendSMSToAliasResponse">
    <wsdlsoap:body use="literal"/>
    </wsdl:output>
    <wsdl:fault name="SMSException">
    <wsdlsoap:fault name="SMSException" use="literal"/>
    </wsdl:fault>
    <wsdl:fault name="EnablerException">
    <wsdlsoap:fault name="EnablerException" use="literal"/>
    </wsdl:fault>
    </wsdl:operation>
    <wsdl:operation name="sendSMSWithNotificationToAlias">
    <wsdlsoap:operation soapAction=""/>
    <wsdl:input name="sendSMSWithNotificationToAliasRequest">
    <wsdlsoap:body use="literal"/>
    </wsdl:input>
    <wsdl:output name="sendSMSWithNotificationToAliasResponse">
    <wsdlsoap:body use="literal"/>
    </wsdl:output>
    <wsdl:fault name="SMSException">
    <wsdlsoap:fault name="SMSException" use="literal"/>
    </wsdl:fault>
    <wsdl:fault name="EnablerException">
    <wsdlsoap:fault name="EnablerException" use="literal"/>
    </wsdl:fault>
    </wsdl:operation>
    </wsdl:binding>
    <wsdl:service name="SMSSenderEnablerRemoteService">
    <wsdl:port
    binding="impl:SMSSenderEnablerRemoteSoapBinding"
    name="SMSSenderEnablerRemote">
    <wsdlsoap:address
    location="http://localhost:8888/Simulateur/services/SMSSenderEnablerRemote?wsdl"/>
    </wsdl:port>
    </wsdl:service>
    <plnk:partnerLinkType name="SMSSenderEnablerRemoteLink">
    <plnk:role name="SMSSenderEnablerRemoteProvider">
    <plnk:portType name="impl:SMSSenderEnablerRemote"/>
    </plnk:role>
    </plnk:partnerLinkType>
    </wsdl:definitions>
    Is that possible to reuse (in a BPEL file) schemas types defined in a wsdl file with Oracle PM? Could you give me a hint to solve this problem?
    Many Thanks
    Guillaume

    You need to use the XSLT before you do assignment to achieve this, to
    change the message to the correct namespace.
    Please refer to sample at
    "orabpel\samples\tutorials\114.XSLTTransformations" which talks about
    how to use XSLT transformation.
    And please refer to
    "orabpel\samples\tutorials\121.FileAdapter\ComplexStructure" sample
    especially "InvToPo.xslt" which talks about doing transformations
    between 2 structures pointing to different namespaces.

  • PI does not combine .wsdl file with .xsd files.

    Hi,
    I imported .wsdl file with necessary .xsd files in PI system (7.1).
    PI does not find fields in .wsdl already necessary .xsd files imported with .wsdl file.
    Is there anyone to help me to solve problem with test it in PI system.
    I send .wsdl file and necessary .xsd files as attachment his mail address.
    Thanks.

    Did you try opening the wsdl file in some XML tool...if there is problem in referring the XSD then it will be visible in the tool itself.....even I am working on PI7.1 and some of the WSDLs are referring XSDs...and i had no problem in using them.....dont know what is failing in your case
    Do you want me to send .wsdl and .xsd files zipped into your mail box
    instead you can post your wsdl file and the corresponding XSD here in SDN....even a dummy structure would do....we are not allowed to do personal email comunication
    Regards,
    Abhishek.

  • Messages not adviced in extern definition after import wsdl-file from WAS

    Hi friends,
    after importing the three wsld-files in repository (extern definitions) the messages are not adviced. The referendes to the files are fine, because the name is shown at the tab externe...
    But i´m not shure wheather i tool the right link ant Web Service Navigator. It is right to download the default SAP WSDL Files or the default one? Because in the SAP WSDL-files there will be an exception during import in XI repository (tag sap:useFeatur). What is the problem that the messages are not shown on the tab messages in externe definitions?
    Thanks in advance,
    Frank

    I've the same problem. Here is my WSDL:
    <?xml version="1.0" encoding="UTF-8"?>
    <wsdl:definitions targetNamespace="http://blablabla.de:8080/jboss-net/services/MyServices" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://blablabla.de:8080/jboss-net/services/MyServices" xmlns:intf="http://blablabla.de:8080/jboss-net/services/MyServices" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns1="blablabla.de" xmlns:tns2="http://net.jboss.org/jmx" 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 targetNamespace="blablabla.de" xmlns="http://www.w3.org/2001/XMLSchema">
                   <import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
                   <complexType name="MSOBean">
                        <sequence>
                             <element name="installationName" nillable="true" type="xsd:string"/>
                             <element name="requestId" nillable="true" type="xsd:string"/>
                             <element name="returnCode" type="xsd:int"/>
                             <element name="returnMessage" nillable="true" type="xsd:string"/>
                        </sequence>
                   </complexType>
                   <complexType name="MSIBean">
                        <sequence>
                             <element name="password" nillable="true" type="xsd:string"/>
                             <element name="project" nillable="true" type="xsd:string"/>
                             <element name="requestId" nillable="true" type="xsd:string"/>
                             <element name="userId" nillable="true" type="xsd:string"/>
                        </sequence>
                   </complexType>
              </schema>
         </wsdl:types>
         <wsdl:message name="actualizeRequest">
              <wsdl:part name="inData" type="tns1:MSIBean"/>
         </wsdl:message>
         <wsdl:message name="actualizeResponse">
              <wsdl:part name="actualizeReturn" type="tns1:MSOBean"/>
         </wsdl:message>
         <wsdl:portType name="MSService">
              <wsdl:operation name="actualize" parameterOrder="inData">
                   <wsdl:input message="impl:actualizeRequest" name="actualizeRequest"/>
                   <wsdl:output message="impl:actualizeResponse" name="actualizeResponse"/>
              </wsdl:operation>
         </wsdl:portType>
         <wsdl:binding name="MyServicesSoapBinding" type="impl:MSService">
              <wsdlsoap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
              <wsdl:operation name="actualize">
                   <wsdlsoap:operation soapAction=""/>
                   <wsdl:input name="actualizeRequest">
                        <wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://blablabla.de" use="encoded"/>
                   </wsdl:input>
                   <wsdl:output name="actualizeResponse">
                        <wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://blablabla.de:8080/jboss-net/services/MyServices" use="encoded"/>
                   </wsdl:output>
              </wsdl:operation>
         </wsdl:binding>
         <wsdl:service name="MSServiceService">
              <wsdl:port binding="impl:MyServicesSoapBinding" name="MyServices">
                   <wsdlsoap:address location="http://blablabla.de:8080/jboss-net/services/MyServices"/>
              </wsdl:port>
         </wsdl:service>
    </wsdl:definitions>
    No Idea.

Maybe you are looking for