WSDL Policy references in WSDL FILE

Hi Folks ,
I am working on PI 7.3 ( Web service to Proxy scenario )
I have generated a WSDl file from my integrated configuration object to give it to sender system personell
In that WSDL file I see references of WSDL POLICY due to which the client is not able to upload that in his landscape
If I remove those policy references , he is able to upload the WSDL and do his coding to be able to hit PI system
Does this policy refrences absolutely necessary ?
If I remove them does it have some implication going forward ?
xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy"
     xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
     xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
     <wsdl:documentation/>
     <wsp:UsingPolicy wsdl:required="true"/>
     <wsp:Policy wsu:Id="OP_xyz_Async"/>
Please Guide
Thanks
Ninad Sane

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

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

Error while uploading WSDL file in Interactive Form Data Connection!

I have created we service to return some data based on user input.
I am trying to link this webservice to Interactive adobe form! and While creating new data connection->uploading WSDL file--> I am receiving error i.e. Invalid File.
Please help me in resolving this issue.
I have created this WSDL file copy/pasting XML code generates from "Open WSDL document for selected binding" link in SOAMANAGER.
Regards,
Naveen.I

Hello,
This is a Webservice created for the FM : HRXSS_PER_READ_EMERGENCY_AR
Here is the sample of the WSDL file generated, as asked by you.
<?xml version="1.0" encoding="utf-8" ?>
- <wsdl:definitions targetNamespace="urn:sap-com:document:sap:soap:functions:mc-style" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="urn:sap-com:document:sap:soap:functions:mc-style" xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:n1="urn:sap-com:document:sap:rfc:functions">
- <wsdl:documentation>
<sidl:sidl xmlns:sidl="http://www.sap.com/2007/03/sidl" />
</wsdl:documentation>
<wsp:UsingPolicy wsdl:required="true" />
- <wsp:Policy wsu:Id="BN_BN_ZHR_READ_EMERGENCY">
<saptrnbnd:OptimizedXMLTransfer uri="http://xml.sap.com/2006/11/esi/esp/binxml" xmlns:saptrnbnd="http://www.sap.com/webas/710/soap/features/transportbinding/" wsp:Optional="true" />
<saptrnbnd:OptimizedXMLTransfer uri="http://www.w3.org/2004/08/soap/features/http-optimization" xmlns:saptrnbnd="http://www.sap.com/webas/710/soap/features/transportbinding/" wsp:Optional="true" />
- <wsp:ExactlyOne xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:sapsp="http://www.sap.com/webas/630/soap/features/security/policy" xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702" xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns:wsu="http://schemas.xmlsoap.org/ws/2002/07/utility">
- <wsp:All>
- <sp:TransportBinding>
- <wsp:Policy>
- <sp:TransportToken>
- <wsp:Policy>
<sp:HttpsToken />
</wsp:Policy>
</sp:TransportToken>
- <sp:AlgorithmSuite>
- <wsp:Policy>
<sp:TripleDesRsa15 />
</wsp:Policy>
</sp:AlgorithmSuite>
- <sp:Layout>
- <wsp:Policy>
<sp:Strict />
</wsp:Policy>
</sp:Layout>
</wsp:Policy>
</sp:TransportBinding>
</wsp:All>
</wsp:ExactlyOne>
</wsp:Policy>
- <wsp:Policy wsu:Id="IF_IF_ZHR_READ_EMERGENCY">
- <sapsession:Session xmlns:sapsession="http://www.sap.com/webas/630/soap/features/session/">
<sapsession:enableSession>false</sapsession:enableSession>
</sapsession:Session>
<sapcentraladmin:CentralAdministration xmlns:sapcentraladmin="http://www.sap.com/webas/700/soap/features/CentralAdministration/" wsp:Optional="true" />
</wsp:Policy>
- <wsp:Policy wsu:Id="OP_IF_OP_HrxssPerReadEmergencyAr">
<sapcomhnd:enableCommit xmlns:sapcomhnd="http://www.sap.com/NW05/soap/features/commit/">false</sapcomhnd:enableCommit>
<sapblock:enableBlocking xmlns:sapblock="http://www.sap.com/NW05/soap/features/blocking/">true</sapblock:enableBlocking>
<saptrhnw05:required xmlns:saptrhnw05="http://www.sap.com/NW05/soap/features/transaction/">no</saptrhnw05:required>
<saprmnw05:enableWSRM xmlns:saprmnw05="http://www.sap.com/NW05/soap/features/wsrm/">false</saprmnw05:enableWSRM>
</wsp:Policy>
- <wsdl:types>
- <xsd:schema attributeFormDefault="qualified" targetNamespace="urn:sap-com:document:sap:rfc:functions">
- <xsd:simpleType name="char1">
- <xsd:restriction base="xsd:string">
<xsd:maxLength value="1" />
</xsd:restriction>
</xsd:simpleType>
"More simple types
<xsd:pattern value="\d*" />
</xsd:restriction>
</xsd:simpleType>
</xsd:schema>
- <xsd:schema attributeFormDefault="qualified" targetNamespace="urn:sap-com:document:sap:soap:functions:mc-style" xmlns:n0="urn:sap-com:document:sap:rfc:functions">
<xsd:import namespace="urn:sap-com:document:sap:rfc:functions" />
- <xsd:complexType name="Bapiret2">
- <xsd:sequence>
"More element names
- <xsd:complexType>
- <xsd:sequence>
<xsd:element name="Messages" type="tns:Bapirettab" />
<xsd:element name="Records" type="tns:HcmtBspPaArR0006Tab" />
<xsd:element name="Records2" type="tns:HcmtBspPaArR0021Tab" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
</wsdl:types>
- <wsdl:message name="HrxssPerReadEmergencyAr">
<wsdl:part name="parameters" element="tns:HrxssPerReadEmergencyAr" />
</wsdl:message>
- <wsdl:message name="HrxssPerReadEmergencyArResponse">
<wsdl:part name="parameter" element="tns:HrxssPerReadEmergencyArResponse" />
</wsdl:message>
- <wsdl:portType name="ZHR_READ_EMERGENCY">
- <wsp:Policy>
<wsp:PolicyReference URI="#IF_IF_ZHR_READ_EMERGENCY" />
</wsp:Policy>
- <wsdl:operation name="HrxssPerReadEmergencyAr">
- <wsp:Policy>
<wsp:PolicyReference URI="#OP_IF_OP_HrxssPerReadEmergencyAr" />
</wsp:Policy>
<wsdl:input message="tns:HrxssPerReadEmergencyAr" />
<wsdl:output message="tns:HrxssPerReadEmergencyArResponse" />
</wsdl:operation>
</wsdl:portType>
- <wsdl:binding name="ZHR_READ_EMERGENCY" type="tns:ZHR_READ_EMERGENCY">
- <wsp:Policy>
<wsp:PolicyReference URI="#BN_BN_ZHR_READ_EMERGENCY" />
</wsp:Policy>
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" />
- <wsdl:operation name="HrxssPerReadEmergencyAr">
<soap:operation soapAction="" style="document" />
- <wsdl:input>
<soap:body use="literal" />
</wsdl:input>
- <wsdl:output>
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
- <wsdl:service name="service">
- <wsdl:port name="ZHR_READ_EMERGENCY" binding="tns:ZHR_READ_EMERGENCY">
<soap:address location="http://cieh4-srvr.collabera.com:8000/sap/bc/srt/rfc/sap/zhr_read_emergency/900/zhr_read_emergency/zhr_read_emergency" />
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
Cheers,
Remi

Failed to read wsdl file from url

Hi all,
I am struggling with WL 9.2, consuming a WSRP enabled portlet at the following point:
Having created a proxy portlet, refering to the WSDL of the WSRP producer, I did successfully deploy the portal. When accessing the portal and consuming the portlet the following exception is thrown:
com.bea.wsrp.faults.TransportException: Failed to read wsdl file from url due to -- java.net.ConnectException: Tried all: '8' addresses, but could not connect over HTTP to server: 'www.w3.org', port: '80';
The WSDL includes a schema (http://www.w3.org/2001/XMLSchema). The URL is definetely accessible by the server.
I am open for any kind of support ;) Thanks in advance!
Kind regards,
Matthias

Yes, they are all local schemas. The way ALSB works, even if the import path in the wsdl or parent schema doesn't exist, relative to the current directory, you can specify which schema resolves that reference. My WSDL imports several schemas, all of which import others. When I was done importing all the schemas and resolving references, all the references in WSDLs and XSDs were assigned and valid. However, after all of those imports and reference resolution, it still says the WSDL is invalid, with the following odd error message:
The WSDL is not semantically valid: Failed to read wsdl file from url due to -- java.net.MalformedURLException: no protocol: /XMLSchema/PaymentServices/Resources/PaymentServices-200802.
That path listed refers to one of the schemas imported by the WSDL. The reference to that schema in the WSDL was resolved, and it doesn't complain about that reference.

Not able to read the wsdl file from server Premature EOF encounter

Hi All,
I am facing issue while accessing a web Service from server. Here is the clear view about it.
I created a simple SyncBpel process in a composite and deployed in to the server and it is working fine. Later i created a new Asyn bpel process in a composite and in the external reference i dragged a web Service and imported the wsdl url from server of the SyncBpel and wired the Asynbpel process to webserive .
Now here i am facing peculiar behavior which i am not able to trace it out.
1) For the first time when i import the url of syncBpel from the server i am not facing any error and it is working fine as expected but when i close the Jdeveloper and open it i am not able to user the web Service and it is saying as "Not able to read the wsdl file from server Premature EOF encounter"
2)When i close and open the Jdeveloper i can see the url of the wsdl which imported in webserver is changing from http://stcfmw03.satyam.com:8021/soa-infra/services/Tarak/synchronousBpel/bpelsync_client_ep?WSDL to http://stcfmw03.satyam.com:8021/soa-infra/services/Tarak/synchronousBpel/BPELsync.wsdl
3)when I open and see the url http://stcfmw03.satyam.com:8021/soa-infra/services/Tarak/synchronousBpel/bpelsync_client_ep?WSDL I can see the soap address as *<soap:address location="http://stcfmw03.satyam.com:8021/soa-infra/services/Tarak/synchronousBpel!1.0*soa_5cfb8416-c106-40a2-a53b-9054bbe04b9c/bpelsync_client_ep"/>*
I don’t understand why the soap end contains “*soa_5cfb8416-c106-40a2-a53b-9054bbe04b9c” and this kind of url for soap address is coming to all the bpel process which I am deploying in the server.
I checked the in Jdeveloper where webproxy is uncheck and the server is also up but still I am facing issue of reading the error.
Can someone please help in resolving the issue.
I am using SOA 11g 11.1.1.5 and Jdeveloper 11.1.1.5
Many thanks.
Tarak
Edited by: user11896572 on Jan 17, 2012 5:22 PM

Hi,
Setting default from the jdeveloper -
During composite deployment from Jdeveloper (wizard driven), you will be given an option to choose the version of the composite and there will also be an option for you to choose if the composite needs to be deployed as default.
Setting default from the em console -
After deploying a composite, login to the em console and click on the composite that you want to set as default, and you will find a tab - "Set as Default". please note that this tab will not be seen, if the composite is already set as default.
Refer -
http://docs.oracle.com/cd/E12839_01/integration.1111/e10226/soacompapp_mang.htm
8.2 Managing the State of Deployed SOA Composite Applications
Thanks

How to Consume a WSDL file in Webdynpro JAVA Application 7.30

Hi Experts,
My requirement is,I have a wsdl file(Provided by the SAP PI) which i need to consume in Webdynpro Java 7.3(NWDS 7.30).
I has been tried in the follwing way
1.First click on the Model --> Adaptive Web Service Model -->Model Name--Package Name
2.Choose Remote Location/File System.
3.After that choose the WSDL file from my project which i added earlier.
4.After that I get the node in the context menu.But I am uneble to set some data into the node and also uneble to get data data from the node
After deploying my project I get the following error.
Error ::
The initial exception that caused the request to fail, was:
com.sap.esi.esp.service.server.query.discovery.ExtendedServiceException: Configuration not found for service reference with ID: c73e38ff-a4d8-4e4c-89c2-827fd5cf17ac from application demo.sap.com/mwebsrvc. Either you have not assigned the Service Group to a Provider System or the generation of the configuration has failed. Check the configuration details from SAP NetWeaver Administrator -> Application Communication. --> Details about the Service Reference: {urn://TestSOAPtoRFCSender}SI_TestSOAPtoRFCSender_OB; Service Group: com.tsecl.SITestSOAPtoRFCSender_OB.pidev_nerapdrp_gov_in; Service Group Software Component: demo.sap.com/mwebsrvc; Service Group Application: demo.sap.com/mwebsrvc; Configuration state: Not configured
    at com.sap.esi.esp.service.server.dynamic.DIIServiceRefConfigContextImpl.prepareContext(DIIServiceRefConfigContextImpl.java:275)
    at com.sap.esi.esp.service.server.dynamic.DIIServiceRefConfigContextImpl.<init>(DIIServiceRefConfigContextImpl.java:59)
    at com.sap.esi.esp.service.server.dynamic.DIIContextCreatorImpl.createDIIServiceRefConfigContext(DIIContextCreatorImpl.java:18)
    at com.sap.engine.services.webservices.espbase.client.dynamic.configuration.DIIContextFactory.createDIIConfigurationsContext(DIIContextFactory.java:12)
    at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService_NewInstance(GenericServiceFactory.java:368)
    ... 67 more
Please help me about this.
Thanks and Regards,
Amit Basak

Hi Amit,
Create provider system in NWA -> SOA management -> System Connections. After ping is successful go to NWA -> Application Communication and select your DC and assign the provide system for your service configuration group.
I hope it will works fine as we also did the same.
- Pradeep

Error while Generating WSDL File from SAP WSDLGenerator

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
   at WebServiceDescription.SelectOperation.ShowUDOsList(String sessionID)
   at WebServiceDescription.SelectOperation..ctor(String sessionID)
   at WebServiceDescription.WsdlServicesGenerator.ShowOptions()
   at WebServiceDescription.Form1.btCreateWsdl_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3082 (QFE.050727-3000)
    CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
WsdlServicesGenerator
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Program%20Files/SAP/SAP%20Business%20One%20Web%20Services/WsdlServicesGenerator/WsdlServicesGenerator.exe
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3082 (QFE.050727-3000)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
System.Web.Services
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Web.Services/2.0.0.0__b03f5f7f11d50a3a/System.Web.Services.dll
System.Configuration
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
axh7tjvl
    Assembly Version: 1.0.0.0
    Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
o_2nbqv_
    Assembly Version: 1.0.0.0
    Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
I am facing problem While Generating WSDL File from WSDL Geerator which is provided by SAP Business One
If any body has resolved this. Please help Me...!
Thanks
Mritunjay

Hi.
We've seen that error too few times.
We downloaded the sourcecode for the wdsl generator and discovered,
that in our case, it was because we had no user defined objects.
Its actually a bug as far as I can see, where the wdsl generator tries
to enumerate a empty recordset, and crashes.
Regards
Jørgen T.

Error when trying to create a web service from a wsdl file using jdeveloper

Hello,
I'm using the latest jdeveloper and jdk 6 update 20 on solaris sparc 10.
When I'm trying to create a web service from a wsdl on the java EE 1.5 platform i get the following error:
Validation failed:
java.lang.NoSuchMethodException: com.sun.tools.xjc.generator.annotation.spec.XmlElementRefWriter.required(boolean)
I've tried the endorsed mechanism with the latest jaxws-api.jar and jaxb-api.jar packages with no help.
It works fine when i use the java EE 1.4 platform....
The full Error description:
oracle.jdeveloper.webservices.model.WebServiceException: Error creating model from wsdl "file:/vobs/NMS/NorthBoundIF/MTOSI/MTOSI_Documentation/DDPs/ResourceTroubleManagement/IIS/wsdl/AlarmRetrieval/AlarmRetrievalHttp.wsdl": java.lang.NoSuchMethodException: com.sun.tools.xjc.generator.annotation.spec.XmlElementRefWriter.required(boolean)
+     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.setDescription(JavaWebService.java:745)+
+     at oracle.jdevimpl.webservices.wizard.jaxrpc.topdown.TDJaxWsSpecifyWsdlPanel.setDescription(TDJaxWsSpecifyWsdlPanel.java:364)+
+     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 "file:/vobs/NMS/NorthBoundIF/MTOSI/MTOSI_Documentation/DDPs/ResourceTroubleManagement/IIS/wsdl/AlarmRetrieval/AlarmRetrievalHttp.wsdl": java.lang.NoSuchMethodException: com.sun.tools.xjc.generator.annotation.spec.XmlElementRefWriter.required(boolean)
+     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)+
+     ... 8 more+
Caused by: oracle.j2ee.ws.common.tools.api.ValidationException: Error creating model from wsdl "file:/vobs/NMS/NorthBoundIF/MTOSI/MTOSI_Documentation/DDPs/ResourceTroubleManagement/IIS/wsdl/AlarmRetrieval/AlarmRetrievalHttp.wsdl": java.lang.NoSuchMethodException: com.sun.tools.xjc.generator.annotation.spec.XmlElementRefWriter.required(boolean)
+     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 $Proxy34.getJaxWsSeiInfo(Unknown Source)+
+     at oracle.jdevimpl.webservices.tools.wsa.WsaAdaptor.getSeiInfo(WsaAdaptor.java:505)+
+     ... 11 more+
Caused by: java.lang.RuntimeException: java.lang.NoSuchMethodException: com.sun.tools.xjc.generator.annotation.spec.XmlElementRefWriter.required(boolean)
+     at com.sun.tools.xjc.generator.bean.field.AbstractField.getMRequired(AbstractField.java:186)+
+     at com.sun.tools.xjc.generator.bean.field.AbstractField.annotateReference(AbstractField.java:209)+
+     at com.sun.tools.xjc.generator.bean.field.AbstractField.annotate(AbstractField.java:164)+
+     at com.sun.tools.xjc.generator.bean.field.AbstractFieldWithVar.createField(AbstractFieldWithVar.java:75)+
+     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.GeneratedConstructorAccessor53.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:75)+
+     at com.sun.tools.xjc.generator.bean.BeanGenerator.generateFieldDecl(BeanGenerator.java:751)+
+     at com.sun.tools.xjc.generator.bean.BeanGenerator.generateClassBody(BeanGenerator.java:539)+
+     at com.sun.tools.xjc.generator.bean.BeanGenerator.<init>(BeanGenerator.java:241)+
+     at com.sun.tools.xjc.generator.bean.BeanGenerator.generate(BeanGenerator.java:181)+
+     at com.sun.tools.xjc.model.Model.generateCode(Model.java:286)+
+     at com.sun.tools.xjc.api.impl.s2j.SchemaCompilerImpl.bind(SchemaCompilerImpl.java:251)+
+     at com.sun.tools.xjc.api.impl.s2j.SchemaCompilerImpl.bind(SchemaCompilerImpl.java:85)+
+     at oracle.j2ee.ws.common.tools.databinding.jaxb20.JAXB20TypeGenerator.generateJavaTypes(JAXB20TypeGenerator.java:117)+
+     at oracle.j2ee.ws.tools.wsa.SchemaTool.genValueTypes(SchemaTool.java:186)+
+     at oracle.j2ee.ws.tools.wsa.jaxws.JaxwsWsdlToJavaTool.getJAXWSModel(JaxwsWsdlToJavaTool.java:647)+
+     ... 20 more+
Caused by: java.lang.NoSuchMethodException: com.sun.tools.xjc.generator.annotation.spec.XmlElementRefWriter.required(boolean)
+     at java.lang.Class.getMethod(Class.java:1605)+
+     at com.sun.tools.xjc.generator.bean.field.AbstractField.getMRequired(AbstractField.java:184)+
+     ... 40 more+
Thanks,
Roy.

Guys,
You are asking about an issue that was a pain in the nick for me few months ago. The problem is that you won't find mych help here as I figured out that Apex geeks here either did not do much webservices or ended up hating it as i do :) . This is an error that can be due many different reason, let me ask you this:
1- Does your the other system you are trying to call through webservices using HTTPS ?
2- If yes, did you create a valid oracle wallet for that https connection ?
3- Make sure you are using the correct URL ( am sure you do, just double check )
4- If using a proxy, then you have to define that in the web service reference creation page
provide more info and I hope I can help you with this,
Sam
Please reward good answers by marking them correct or helpful!

Error while loading WSDL File in Eclipse

Hi Experts
We are getting the following Error while Loading WSDL File in Eclipse.
IWAB0399E Error in generating Java from WSDL: WSDLException (at /wsdl:definitions/wsdl:portType/wsp:Policy): faultCode=INVALID_WSDL: Encountered unexpected element 'Policy'.:
Please advice how to resolve it.
Regards
Prashant

It seems that your WSDL is not well defined, you need to test your wsdl via WS-I compliance in order to check if the wsdl is well created, you can do this via soapui, just create a new project, import the wsdl file or set the URL, left click in the project and select check WS-I compliance, this tool will test your wsdl and gives you a detailed report of what might be the problem.

C# Proxy Classes from SAP WSDL files

We are trying to generate proxy classes for SAP eSOA web services using C# and Visual Studio 2005.
When we try to run Microsoft's proxy class generation utility, WSDL.exe, errors are generated that attribute incorrect syntax to the SAP WSDL file:
> Microsoft (R) Web Services Description Language Utility [Microsoft (R)
> .NET Framework, Version 2.0.50727.42] Copyright (C) Microsoft
> Corporation. All rights reserved.
> Warning: This web reference does not conform to WS-I Basic Profile v1.1.
> R2028, R2029: A DESCRIPTION using the WSDL namespace and the WSDL SOAP
> binding n amespace MUST be valid according to the XML Schemas found at
> http://schemas.xmls oap.org/wsdl/2003-02-11.xsd and http://schemas.xmlsoap.org/wsdl/soap/2003-02-11.
> xsd.
> - Warning: The element 'definitions' in namespace
> 'http://schemas.xmlsoap.org /wsdl/' has invalid child element 'properties' in namespace 'urn:com-sap:ifr:v2:
> wsdl'. List of possible elements expected: 'import, types, message,
> portType, bi nding, service' in namespace
> 'http://schemas.xmlsoap.org/wsdl/'. Line 1748, posi tion 4.
>
> SOAP 1.1 binding was not found: WS-I's Basic Profile 1.1 consists of
> implementat ion guidelines that recommend how a set of core Web
> services specifications shou ld be used together to develop
> interoperable Web services. For the 1.1 Profile, those specifications are SOAP 1.1, WSDL 1.1, UDDI 2.0, XML 1.0 and XML Schema.
>
> For more details on the WS-I Basic Profile v1.1, see the specification
> at http://www.ws-i.org/Profiles/BasicProfile-1.1.html.
The WSDL file is obtained from the SAP ES Workplace, from the following URL:
http://erp.esworkplace.sap.com/socoview(bD1lbiZjPTgwMCZkPW1pbg==)/render.asp?&id=4FFC1A97663611DA36BB000F20DAC9EF&fragID=&packageid=DBBB6D8AA3B382F191E0000F20F64781&iv=
We have already tried both SAP files available from this location; neither works.
Any insight you can offer to help us generate these proxy classes is welcome. Note that the SAP PDF file, "ESOA-Roadmap-Workshop.PDF" talks about one syntactic incompatibility with Microsoft WSDL (on page 70), but this solution does not work, and indeed the token 'parameters' does not appear anywhere in either SAP WSDL file for Create Maintenance Request eSOA.
Thanks for any help you can offer!
-- Julian Mensch

I have the same problem after renaming "parameters" to "parameter" and I'm using the same example ES that's in the document:
http://erp.esworkplace.sap.com/sap/bc/srt/xip/sap/ECC_EMPLOYEEBASICDBYEMPLOYEEQR/version3?sap-client=800&wsdl=1.1
wsdl.exe from .NET Framework 2.0.50727.42 gives me
Microsoft (R) Web Services Description Language Utility
[Microsoft (R) .NET Framework, Version 2.0.50727.42]
Copyright (C) Microsoft Corporation. All rights reserved.
Warning: This web reference does not conform to WS-I Basic Profile v1.1.
SOAP 1.1 binding was not found: WS-I's Basic Profile 1.1 consists of implementat
ion guidelines that recommend how a set of core Web services specifications shou
ld be used together to develop interoperable Web services. For the 1.1 Profile,
those specifications are SOAP 1.1, WSDL 1.1, UDDI 2.0, XML 1.0 and XML Schema.
For more details on the WS-I Basic Profile v1.1, see the specification
at http://www.ws-i.org/Profiles/BasicProfile-1.1.html.
Warning: no classes were generated.
Warnings were encountered. Review generated source comments for more details.
I'm sure it's something really stupid since this example worked at some point for whoever wrote the doc...
It's sad that there is basically no .NET support from the SAP side and apart from a few documents there is basically no developer documentation or samples...

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 can i include Services and Bindung in a generated WSDL file?

Hi,
i what to use a generated wsdl file from an erp system, to build a web service client with WSDL2Java (org.apache.axis.wsdl.WSDL2Java).
I noticed, that services an bindings are missing, also a policy is included.
How can i include services and bindings in the wsdl and exclude the policy?
Thanks!

well, I assume you have SOAMANAGER.
choose your service & "Apply Selection" (very useless button btw)
select a binding in the dropdown box or create on if you do not have one yet
Click button "Show WSDL options" (actually they do not really look like buttons in WD; call it yellow blot)
Some extra config area is thrown onto your screen (without any sense for usability or design); Change the radio button for WSDL format from "WS policy" to "Standard"; make sure the first radio button group is on "True" for monolithic
Now click the link (why is this a link and no blot?) called "Display selected bindings WSDL URL"
an extra text field is again thrown onto your screen somwhere between the dropdown and the WSDL option config area containing an URL (get out your glasses if you don't see the sub-10pt-letters)
hope it helps,
anton

Problem with old namespace in WSDL file

I have a problem with my WSDL file. My scenario is SOAP to IDOC.
Originally the ESB data types were configured under namespace urn:test1:xxx for development purposes. When it came time to implement and test, we copied the data types from the old name space to a new namespace http://company.com:interface.
After the new objects were created, all the old test objects were deleted, including the old namespace definition. Now when I generate the WSDL file, the top part of the WSDL file looks correct, but toward the bottom, there are references to the old namespace.
Does anyone know why these reference are appearing, and is there any way to correct this without deleting all my objects and rebuilding everything?
Thanks in advance for any help. Will award points for help.
Terri

Found the problem....the XML namespace in the Message type still contained the old namespace. When this was changed to the new namespace, second target namespace was no longer generated.

Problem with WSDL file

Hi,
I'm new with web services and want to publish a stateless Java class as web service.
I've created the WSDL file by means of the Web Service Publishing Wizard.
when I run the "Web service stub/Skeleton Wizard" in step 1 of 2 appears the following warning message:
"WSDL validation failed with the following exception:
oracle.xml.parser.v2.XML.ParseException:
Withespace required".
Some idea ??
Thanks in advance
Alejandro von Eckenbrecher
[email protected]

Mike,
I'm working with the example of OTN "Publish a Stateless Pure Java Web Service".
I've find that the WSDL file is not being generated correctly, the latest two lines are:
<binding name="HelloImplBinding" type="tns:HelloImplPortType">
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"
If I manually correct them as these:
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
</definitions>
(add the tags in bold),the XML parser don't report erros and can run the stub/skeleton wizard but in step 2 of 2 don't find any service.
I believe that the problem this in the WSDL file but them
are generated automatically from the example files.
below will find the complete file for reference.
Thanks
Alejandro
<?xml version = '1.0' encoding = 'UTF-8'?>


<definitions
name="HelloImpl"
targetNamespace="http://HelloImpl.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://HelloImpl.wsdl"
xmlns:ns1="http://IHelloImpl.xsd">
<types>
<schema
targetNamespace="http://IHelloImpl.xsd"
xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"/>
</types>
<message name="sayHello0Request">
<part name="param" type="xsd:string"/>
</message>
<message name="sayHello0Response">
<part name="return" type="xsd:string"/>
</message>
<portType name="HelloImplPortType">
<operation name="sayHello">
<input name="sayHello0Request" message="tns:sayHello0Request"/>
<output name="sayHello0Response" message="tns:sayHello0Response"/>
</operation>
</portType>
<binding name="HelloImplBinding" type="tns:HelloImplPortType">
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"

How to override generated WSDL with existing WSDL file?

Hi there,
I am migrating our weblogic 8.1 web services to weblogic 10.1. As documented it is not possible to start implementing the web services from WSDL if the web services are based on XML Beans. Therefore I started from scratch, using an XML Beans Utility project and a web service started from Java. This works fine.
I now have a web service with a generated WSDL file, but there are slight differences with the existing WSDL file.
Is it possible to stop generating the WSDL file and just point to the existing WSDL files?
I already tried to expose the WSDL and change the WSDL location but it still returns the generated WSDL instead of the WSDL file that I want.
Thanks in advance,
Martijn Baels
Software Architect
www.leanapps.com

The value of an element is stored in a child node of that element. For example, let's say that "e" references the node <Description> then:
e.getFirstChild().getNodeValue() => "My Test Case"

WSDL Policy references in WSDL FILE

Similar Messages

Maybe you are looking for