WSDl files with SOPAui

Team,
I want to know how i can integrate WSDl files with SOPAui.
what setting i have to do at Inegration Level.
Can user integrate from his desktop or he need to login into the server to configure WSDl files with SOPAui.
=======================
I also need a doc which will enable my URL into internet enable URL. So, that anyone across the globe can access it.
======================

Just to details more about my requirment,
So mainly we want to build application that hit data and modify data in ERP/CRM system, via SOAP envelope (first we will construct request in SoapUI and next, move it into MicroStrategy platform). In this particular example we want to build whole functionality on top of Peoplesoft.
I have given them WSDL files. but when doing he got the message, “Server not found” .
I think that it could be something with external IP, even developer can't connect to IIS of this machine.
Can any one tell me what I have to do ?

Similar Messages

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.

Java code to connect to WSDL file with custom header

Hi all,
I am an absolute noob when it comes to Java. I need to write a Java app that can connect to a WSDL file with a custom header. Basically, all I need to do is connect to the web service and pass a username and password.
Any help would be appreciated.
Thanks,
A

Better you use tools which can generate code(interface,proxy and stub classes) which can take care of calling all the WSDL defined methods..i generally use RAD not an open source as per OP use eclipse open source or netbeans which can do the trick

Create a wsdl file - with schemas inline - in JDeveloper

Hi,
We are trying to create a wsdl file using schemas in jdeveloper 11.1.1.3. We could generate the wsdl file using options available in jdeveloper, but the wsdl generated contains <types> element that has schemas referenced by only an "import" statement as below.
<types>
<xsd:schema>
<xsd:import schemaLocation="../../../Test.xsd" namespace="http://www.openuri.org"/>
</xsd:schema>
</types>
But, I would like get the schemas inlined or embedded within the wsdl instead of just an import statement.. This helps me in using the wsdl anywhere (creating webservices or use in my applications or give it to some one to use) without worrying about the actual schema definition files. The <types> element within the wsdl must have the schemas embedded, something like below.
<types>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="http://testWSDLproject/type" elementFormDefault="qualified">
<xsd:element name="testIn">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="name" type="xsd:string"/>
<xsd:element name="value" type="xsd:integer"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
</types>
Is there any way forward, with the Jdeveloper to create wsdl files with schemas inline ?

Hi Vohra,
The schema snippet pasted previously was just a sample.
In actual, there are mulitple cross referencing xsd files that must be embedded within my wsdl file. Sometimes, such manual editing of wsdl (embedding so many schema definitions) is prone to errors.
If there is an option in Jdeveloper which automatically does this embedding for us, then it becomes more handy. Have you come across any such options ?

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

Cannot generate WSDL file with wscompile

I get an error while generating the WSDL file using wscompile tool.
my compile line is "wscompile -gen:server CRAWS.xml -keep" and I get a RmiModeler error with an ClassNotFoundException .
I have put my jar file in the bin folder (same folder of wscompile) and I've also copied my service build files in the same folder (under the package subfolders).
Here is the code of the xml configuration:
<?xml version="1.0" encoding="UTF-8"?>
<configuration xmlns="http://java.sun.com/xml/ns/jax-rpc/ri/config">
<service name="CraWS_Service" targetNamespace="urn:com.servepath.cra/wsdl/CraService"
      typeNamespace="urn:com.servepath.cra/types/CraService"
      packageName="com.servepath.CraWebService">
    <interface name="com.servepath.CraWebService.CraWSIF" servantName="com.servepath.CraWebService.CraWS_Impl"/>
</service>
</configuration>

I'm new to Web Services so I'm just guessing, but perhaps you need to add -classpath lib/foo.jar;lib/bar.jar to specify where your class-files are.

Wsdl file with import

Hi Experts,
I have received a WSDL file from third party system which PI should invoke.
The WSDL file is inturn using other WSDL file using import namespace and schema location. The message elements types are defined in the sub WSDL file.
Please let me know if we can handle this scenario in PI. If yes do I have to import both WSDL's in external definition and how can I get the target structure?
Thanks
Suma

Can you refer below links
How to refer multiple xsd's in a single xsd and finally import it in XI.
XSD with multiple import/includes

AquaLogic Service Bus Perspective - WSDL Files with External Schemas

I am using the AquaLogic Service Bus Perspective in WebLogic Workshop to create my proxy services, business services, wsdls, schemas, etc. I have a wsdl that imports a schema based on its registered namepsace...not its schemaLocation. This works fine in the ALSB console, but in the WebLogic Workshop perspective, I cannot Publish my WSDL because the WSDL is not aware of any global resources...such as this Schema definition that is external to the WSDL. How do you make Globally aware resources in WebLogic Workshop? The same thing works in through the ALSB Web-based console...but that same file produces a wsdl validation error in my IDE because it has no idea about that schema.
Thanks -jay

Thanks to both of you who replied to my question - it is very much appreciated
We had a theory that you could just store everything under 'sbconfig' in CVS and restore it - but I thought that might be a bit hacky and less upgrade resistant.
Do you use build scripts for setting up dev/qa/prod endpoints because 'customisation files' are new or did you find a problem with 'customisation files' that made you resort to using a build script?
We were hoping to have some process like
Export JAR
Export Customisation File for Dev/QA/Prod
In Dev, we import the JAR + dev customisation file
In QA, we import the JAR + QA customisation file
In Prod, we import the JAR + prod customisation file
I know I have no chance, but you wouldn't care to share said document for my reading (not copying) pleasure? No worries if you don't :)
Thanks for your comments guys :)
Dan.
just in case
email is daniel prosser at gmail com
dots between my name and com
Edited by dan_prosser at 08/14/2007 6:33 PM

Problem in web services wsdl file with tomcat 5

Hi to all JGurus,
I am sunil, i have one problem with simple web service, i made a simple web service and deployed on my tomcat 5, my tomcat showing the web service but when i click on the wsdl link it throws the exception:
javax.servlet.ServletException: JAXRPCSERVLET35: failed to create a template object
     com.sun.xml.rpc.server.http.JAXRPCServletDelegate.doGetDefault(JAXRPCServletDelegate.java:351)
     com.sun.xml.rpc.server.http.JAXRPCServletDelegate.doGet(JAXRPCServletDelegate.java:157)
     com.sun.xml.rpc.server.http.JAXRPCServlet.doGet(JAXRPCServlet.java:111)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
please help me, thanks in advance.

Hi Rama,
I used JAX-RPC with WSDp 2.0 first i created my interface then implemented class then i have used the wscompile to generate wsdl. then i packed with jaxrpc-ri and web.xml in a war file, this raw war file i used to generate my original final war with the help of wsdeploy command.
I deployed this file on tomcat its showing the service but while clicking on wsdl link it throws the above exception.
Please let me know any thing else u want to know i can fwd my sample war file also to u.
Thanks in advance.
Sunil

Cannot generate WSDL files With B1WS Wsdl Services Generator

Hello
I am trying to use the WSDL service generate for SAP web services and its causing me a bit of grief.
Whenever I run it crashes and dies I assume it is because I putting the wrong information in the fields. I have performed all the actions in the help file but I don't seem to be able to find anything anywhere that gives me the exact details of what should go in the text boxes in the generator :
Server -- I assume itu2019s the windows computer name (i.e. TEST)
DbSever type -- No worries itu2019s a drop down even I can figure that out
License Sever -- I assume itu2019s the License server as shown settings :3000 (i.e. TEST:30000)
User Name -- I assume itu2019s the SQL username
Password -- I assume itu2019s the SQL password
Hopefully I have something really simple really wrong.
Thanks in advance for any help.
Darren

This forum is for Crystal Reports. Post your question to the B1 forum.

Error in WSDL file with Inline schemas in RAD

Hi,
I am having a WSDL which is generated in Weblogic workshop. I need to generate a client for that WSDL in RAD 7.0 with websphere 6.1.
WSDL is having inline schemas. when i used the same WSDL in RAD it is showing compile time errors at complex types.
My scenario: I am getting error at type="*_Type1_*" , it saying type reference is unresolved.
<xs:schema xmlns="XXXX" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="XXXX" elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:complexType name="complextype1">
<xs:sequence>
<xs:element name="Location" type="*_Type1_*" nillable="true"/>
</xs:sequence>
</xs:complexType>
</xs:schema>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns="XXXX" targetNamespace="XXXX" elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:simpleType name="Type1">
<xs:restriction base="xs:string"/>
</xs:simpleType>
</xs:schema>
Thanks in advance.

Hi,
I am also getting the same problem on a Web Service created from a function module. This happens when I try to create a new endpoint and save.
Did you manage to find a solution to this.
Regards,
Andy.

Error creating WSDL file

Hi all,
I'm trying to create a WSDL file with wsdeploy from my server classes, but it fails. My build.xml process-war syntax is somewhat similar to that of the Hello example, and the procedure is just the same; first create WEB-INF, then create portable war-file and finally create deployable war-file. The deployable war, src-jaxrpc.war is created, but it doesn't contain the WSDL file. Here are its contents:
META-INF/MANIFEST.MF
src/Harj2IF.class
src/Harj2Impl.class
WEB-INF/classes/src/LibImpl.class
WEB-INF/classes/src/LibIF.class
WEB-INF/web.xml
WEB-INF/jaxrpc-ri-before.xml
WEB-INF/Library_model.xml.gz
WEB-INF/web-before.xml
WEB-INF/jaxrpc-ri-runtime.xml
The error message I get with wsdeploy is this:
[exec] info: created temporary directory: D:\Service\build\wsdeploy-generated\jaxrpc-deploy-ec04fc
[exec] info: processing endpoint: Library
[exec] error: class java.lang.StackTraceElement does not have a public accessible empty constructor
[exec] info: created output war file: D:\Service\dist\src-jaxrpc.war
My config.xml looks like this:
<?xml version="1.0" encoding="UTF-8"?>
<configuration
xmlns="http://java.sun.com/xml/ns/jax-rpc/ri/config">
<wsdl location="http://localhost:9080/src-jaxrpc/src?WSDL"
packageName="src"/>
</configuration>
And my jaxrpc-ri.xml looks like this:
<?xml version="1.0" encoding="UTF-8"?>
<webServices
xmlns="http://java.sun.com/xml/ns/jax-rpc/ri/dd"
version="1.0"
targetNamespaceBase="http://com.test/wsdl"
typeNamespaceBase="http://com.test/types"
urlPatternBase="/ws">
<endpoint
name="Library"
displayName="Example Library v.1.0"
description="A simple Web application"
interface="src.LibIF"
implementation="src.LibImpl"/>
<endpointMapping
endpointName="Library"
urlPattern="/src"/>
</webServices>
My LibIF.java looks like this:
package src;
import java.rmi.Remote;
import java.io.IOException;
import javax.xml.parsers.ParserConfigurationException;
import org.xml.sax.SAXException;
import java.rmi.RemoteException;
public interface LibIF extends Remote {
public boolean initDocument(String fileName) throws IOException, ParserConfigurationException, SAXException, RemoteException;
public boolean addB(String fileName) throws IOException, RemoteException;
public boolean removeB(String fileName) throws IOException, RemoteException;
public boolean showB(String fileName) throws IOException, ParserConfigurationException, SAXException, RemoteException;
public boolean findB() throws IOException, RemoteException;
public boolean rewriteB(String fileName) throws IOException, RemoteException;
Could someone even suggest any solution based on this information?

Are u trying out the example frm that Web Service Book frm that some publisher, He must be using xrpcc. Ok
.........For WSDL file not to be created there are few reasons and in them I kno one. For wsdeploy tool to create the wsdl file it reads the jaxrpc-ri.xml file and the war file.
........for the proper working of this, the impl file shd have methods which throw Remote exceptions and no errors, of course It does compile in the earlier command execution but.. few minute errors like the above might prevent the creation of wsdl file, chk these and try
........Hope it wrks..........|ABY|

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>

<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>
          
          <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>
          
          <variable name="smsmultiRequest" messageType="tns:SMSMulticast2RequestMessage"/>
          
          <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>
     
     
     
     
     
     <sequence name="main">
          
          <receive name="receiveInput" partnerLink="client" portType="tns:SMSMulticast2PT" operation="process" variable="smsmultiRequest" createInstance="yes"/>
          
          <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') > 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>
          
          <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.

How to make a WSDL file generate Java Code

Hi, I'm quite new in web services. I used the ebay shopping service importing the WSDL file with wsimport, and NetBeans automagically created the Ebay libraries while parsing the WSDL.
Now I'm trying to implement my own soap WS, i'm quite finished but when I try to use it importing the WSDL in a new project, my classes are not imported.
So, where's the trick? How can I include code generationi n my WSDL?
thanks in advance :)

hi,
since the wsdl parsing was complet, for sure the classes are copied (.java), to see them check the following path
YourService\build\generated\wsimport\client\YourService
and the .class file will be in
YourService\build\generated\wsimport\binaries\YourService

Client Proxy(WSDL file) via Se80

Hello
We have a client proxy created against a WSDL file (http/url) in SE80 and we are using it currently it.
Now the WSDL file is going to change a little. I want to use the same client proxy and only change the WSDL file with the new WSDL file? How can i acheive this?
I can create a new client proxy and associate WSDL file but i need to change a lot of place in code where we create instances of this abap proxy class.Hence i want to reuse the same client proxy while changing the WSDL file alone.
Any guidance or pointers will be greatly appreciated.
Thanks
Abishek

Hi Stuart,
Cool. This solves my issue. If I choose the "regenerate" button(see attached image) then I am prompted to enter a new WSDL URL or file.
Thanks!
Regards, Yashu

WSDl files with SOPAui

Similar Messages

Maybe you are looking for