Exposing original WSDL files from EJB3/JAX-WS

Hello,
I have a JEE5 Web Service that was built on an existing WSDL and XSD files.
This Web service is an EJB 3 stateless with JAX-WS annotations.
When I deploy my Web Service on Oracle WebLogic Server 10gR3, I would like to expose the service contact (WSDL and XSD files) from my original files rather that let the application server generating these files for me.
Is there a way to deploy my files on the EAR and expose them through WLS?
Thanks for your help
S.
Edited by: eloudsa on 4 nov. 2009 14:20

I'm not a WSDL guru, but it seems that the location of the web service implementation is defaulted to the local host in the WSDL:
<port binding="s0:DecisionControllerWSSoapBinding" name="DecisionControllerWS">
<s1:address location="http://localhost:7001/rtds/webservices-adapter/DecisionControllerWS"/>
</port>
That's why i put the original WSDL location when i created the service, to point to the web service implementation, Was i wrong? because i found a property which can achieve that for me:
javax.xml.ws.BindingProvider.ENDPOINT_ADDRESS_PROPERTY
What if i edited the address location in the trimmed WSDL to point to the implementation, and used the default Service constructor to point to the local trimmed WSD file?

Similar Messages

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

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.

Problems with WSDL file from Webservice definition

Hi all,
I trying to import into XI the WSDL file from a web service. I´m doing it following the blog /people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi
But I do not why but it is not creating the messages.
Any Idea,
Many thanks and Regards
Noelia

Hi thnaks for your help!!
this is the wsdl file. I think this is correct,but i´m not very familiar with this!
<?xml version="1.0" encoding="utf-8"?>
<wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:ns0="urn:WS_ExtraccionNombramientoVi" targetNamespace="urn:WS_ExtraccionNombramientoWsd/WS_ExtraccionNombramientoVi/document" xmlns:tns="urn:WS_ExtraccionNombramientoWsd/WS_ExtraccionNombramientoVi/document">
<wsdl:types>
 <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:WS_ExtraccionNombramientoVi" xmlns:tns="urn:WS_ExtraccionNombramientoVi" elementFormDefault="qualified">
 <xs:element name="ejecutarExtraccionNS">
 <xs:complexType>
 <xs:sequence>
 <xs:element name="fechaExplotacion" type="xs:string" nillable="true"/>
 <xs:element name="tipoXML" type="xs:string" nillable="true"/>
 </xs:sequence>
 </xs:complexType>
 </xs:element>
 <xs:element name="ejecutarExtraccionNSResponse">
 <xs:complexType>
 <xs:sequence>
 <xs:element name="Response" type="xs:string" nillable="true"/>
 </xs:sequence>
 </xs:complexType>
 </xs:element>
 </xs:schema>
</wsdl:types>
<wsdl:message name="ejecutarExtraccionNSIn_doc">
 <wsdl:part name="parameters" element="ns0:ejecutarExtraccionNS"/>
</wsdl:message>
<wsdl:message name="ejecutarExtraccionNSOut_doc">
 <wsdl:part name="parameters" element="ns0:ejecutarExtraccionNSResponse"/>
</wsdl:message>
<wsdl:portType name="WS_ExtraccionNombramientoVi_Document">
 <wsdl:operation name="ejecutarExtraccionNS">
 <wsdl:input message="tns:ejecutarExtraccionNSIn_doc"/>
 <wsdl:output message="tns:ejecutarExtraccionNSOut_doc"/>
 </wsdl:operation>
</wsdl:portType>
</wsdl:definitions>
Regards Noelia

Does wscompile generate "fault" tag in WSDL file from Java exception class?

I'm trying to generate WSDL files from Java classes. I defined some of my own exception that inherits from "RemoteException", but wscompile doesn't generate the corresponding complex type and "fault" tag. Does anyone know if this is a bug or wscompile doesn't support from Java Exception to fault?
Thanks

It will if the exceptions do not inherit from RemoteException.

How do you create a wsdl file from a FM?

Hello friends,
Could some one please let me know how to create a wsdl file from a function module?
I have gone up to the stage of creating webservice and also released it for SOAP runtime using tranasaction code wsconfig.
But I don't know how to proceed from there and create a wsdl file.
Your help will be greatly appreciated.
Tks
Ram
Edited by: Ram Prasad on Nov 18, 2008 4:44 PM

I was able to solve the issue with a friends help. Here are the steps
STEPS in CREATING WSDL file from a FM:
1.Goto SE80 Create a package or select a package in which you want to create a web service.
2.Right click and select Create -> Enterprise Serve/Web Service -> Web Service
3.Follow the wizard steps answering all the questions until complete. This creates the service definition.
4.Goto transaction code <WSCONFIG> and enter the service definition name you have created in previous step. Enter the same name in both u2018service definitionu2019 and u2018variantu2019 fields.
5.Then click on Create button and save. This releases the webservice you created in to soap Runtime.
6.Goto transaction <WSADMIN>
7.Open the tree structure to see the webservice that you just released and click on the right most button (Globe shape).
8.Select u2018Document Styleu2019
9.You have now created the wsdl file for the FM.

Unable to generate WebService Client with Exported (BAPI) WSDL file from XI

Hi there,
I, trying to setup a simple Web Service environment where I'll be exposing a BAPI as Web Service via XI.
So these are the steps I followed:
1) first I imported the BAPI meta data into my SWC in the repository. 2) Second I defined my interrface etc.. 3) Third I exported the generated BAPI WSDL file. 4) Fourth, I tried to generate a Java proxy/client for my Web Service using a Java IDE (IBM WebSphere Application Developer and XML Spy).
Now the problem is that Im not able to generate the Web Service client using the exported WSDL file, the WSDL seems not to be valid...From the generated errors in the IDE, I can see that the problem has to do somewhere/somehow with the WSDL Binding element, which input parameters do not match the input parameters of the port type.
This is a small part of the WSDL file as generated by XI:
 <wsdl:message name="BAPI_AR_ACC_GETOPENITEMS.Input">
 <wsdl:part name="parameters" element="s0:BAPI_AR_ACC_GETOPENITEMS" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"/>
 </wsdl:message>
 <wsdl:message name="BAPI_AR_ACC_GETOPENITEMS.Output">
 <wsdl:part name="parameters" element="s0:BAPI_AR_ACC_GETOPENITEMS.Response" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"/>
 </wsdl:message>
 <wsdl:portType name="BAPI_AR_ACC_GETOPENITEMS.PortType">
 <wsdl:operation name="BAPI_AR_ACC_GETOPENITEMS">
 <wsdl:input message="s0:BAPI_AR_ACC_GETOPENITEMS.Input"/>
 <wsdl:output message="s0:BAPI_AR_ACC_GETOPENITEMS.Output"/>
 </wsdl:operation>
 </wsdl:portType>
 <wsdl:binding name="BAPI_AR_ACC_GETOPENITEMS.SAPBinding" type="s0:BAPI_AR_ACC_GETOPENITEMS.PortType" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
 <s0:binding style="rfc"/>
Has anyone faced a situation like this before? Any clues where to look? I appreciate any feedback, thanks!
Rob.
Message was edited by: rob viana

Hi Rob!
I'm facing the same problem - how did you solve your issue then? I'm getting following error during generation on .NET side:
============================================================================================
Error: There was an error processing 'http://server/wsdl/MIAMI_ACCDOCPost.wsdl'.
- The document at the url http://server/wsdl/MIAMI_ACCDOCPost.wsdl
was not recognized as a known document type.
The error message from each known type may help you fix the problem:
- Report from 'DISCO Document' is 'Discovery document at the URL http://server/wsdl/MIAMI_ACCDOCPost.wsdl could not be found.'.
- The document format is not recognized (the content type is 'content/unknown').
- Report from 'WSDL Document' is 'There is an error in XML document (2, 70138).'.
- Value cannot be null.
Parameter name: name
- Report from 'XML Schema' is 'The root element of a W3C XML Schema should be <schema> and its namespace should be 'http://www.w3.org/2001/XMLSchema'.'.
============================================================================================
kr Martin

Error in WSDL file from soamanager

Hi,
I am taking SalesorderCreatefromdat2 bapi and trying to expose as webservice, I have the steps fromt the Tcode:SE80, after completing the steps, I am trying to get the WSDL file which i can use in the PI.
But i am getting and error:
SRT Framework exception: Cofiguration is invalid: Subject type:'op' is not in scope 'bo' of property 'http://www.sap.com/webas/710/soap/feauters/transpo:SOAPAction'
Advance Thanks...
Ashok

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.

Invoking a method in WSDL file from client class

Hi,
I have got a WSDL file and I have to invoke certian methods from a client class from the WSDL file. What exactly should I do to invoke them from a Java standalone program /servlet/JSP. There is a sayHello() method in the WSDL. Please tell me how to invoke that method from client side. Aslo please let me know the jar files that are needed.
Below is the WSDL file
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions targetNamespace="http://tutorial.com" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://tutorial.com" xmlns:intf="http://tutorial.com" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

<wsdl:message name="sayHelloResponse">
</wsdl:message>
<wsdl:message name="sayHelloResponse1">
<wsdl:part name="sayHelloReturn" type="xsd:string"/>
</wsdl:message>
<wsdl:message name="addRequest">
<wsdl:part name="a" type="xsd:int"/>
<wsdl:part name="b" type="xsd:int"/>
</wsdl:message>
<wsdl:message name="sayHelloRequest">
</wsdl:message>
<wsdl:message name="addResponse">
<wsdl:part name="addReturn" type="xsd:int"/>
</wsdl:message>
<wsdl:message name="sayHelloRequest1">
<wsdl:part name="name" type="xsd:string"/>
</wsdl:message>
<wsdl:portType name="Hello">
<wsdl:operation name="sayHello">
<wsdl:input message="impl:sayHelloRequest" name="sayHelloRequest"/>
<wsdl:output message="impl:sayHelloResponse" name="sayHelloResponse"/>
</wsdl:operation>
<wsdl:operation name="sayHello" parameterOrder="name">
<wsdl:input message="impl:sayHelloRequest1" name="sayHelloRequest1"/>
<wsdl:output message="impl:sayHelloResponse1" name="sayHelloResponse1"/>
</wsdl:operation>
<wsdl:operation name="add" parameterOrder="a b">
<wsdl:input message="impl:addRequest" name="addRequest"/>
<wsdl:output message="impl:addResponse" name="addResponse"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="HelloSoapBinding" type="impl:Hello">
<wsdlsoap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="sayHello">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="sayHelloRequest">
<wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://tutorial.com" use="encoded"/>
</wsdl:input>
<wsdl:output name="sayHelloResponse">
<wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://tutorial.com" use="encoded"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="sayHello">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="sayHelloRequest1">
<wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://tutorial.com" use="encoded"/>
</wsdl:input>
<wsdl:output name="sayHelloResponse1">
<wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://tutorial.com" use="encoded"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="add">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="addRequest">
<wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://tutorial.com" use="encoded"/>
</wsdl:input>
<wsdl:output name="addResponse">
<wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://tutorial.com" use="encoded"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="HelloService">
<wsdl:port binding="impl:HelloSoapBinding" name="Hello">
<wsdlsoap:address location="http://localhost/WebService1/services/Hello"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
Thanks in advance
Prashanth

Hi.
Please put this line in the google search engine "Invoking java web service" u will get lots of the links.
Sanjay Kumar Gupta
[email protected]

Generate WSDL File from Management Console?

Hi,
I am trying to enable a batch job as a web service. So I registered the batch I want and I copied the whole file from the u201CView WSDLu201D button. Now I am trying to use axis1.1 to generate the code and am getting errors. Is this supposed to generate a fully working WSDL file?
The first error I get is
org.xml.sax.SAXException: Error: URI=file:/c:/axis/BO.wsdl Line=10: Undeclared prefix in name: "xsd:schema".
        at org.apache.axis.utils.XMLUtils$ParserErrorHandler.error(XMLUtils.java:619)
        at org.apache.crimson.parser.Parser2.error(Unknown Source)
        at org.apache.crimson.parser.Parser2.processName(Unknown Source)
        at org.apache.crimson.parser.Parser2.maybeElement(Unknown Source)
        at org.apache.crimson.parser.Parser2.content(Unknown Source)
        at org.apache.crimson.parser.Parser2.maybeElement(Unknown Source)
        at org.apache.crimson.parser.Parser2.content(Unknown Source)
        at org.apache.crimson.parser.Parser2.maybeElement(Unknown Source)
        at org.apache.crimson.parser.Parser2.parseInternal(Unknown Source)
        at org.apache.crimson.parser.Parser2.parse(Unknown Source)
        at org.apache.crimson.parser.XMLReaderImpl.parse(Unknown Source)
        at org.apache.crimson.jaxp.DocumentBuilderImpl.parse(Unknown Source)
        at org.apache.axis.utils.XMLUtils.newDocument(XMLUtils.java:322)
        at org.apache.axis.utils.XMLUtils.newDocument(XMLUtils.java:367)
        at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:384)
        at org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:245)
        at java.lang.Thread.run(Unknown Source)
So I add
xmlns:xsd=http://www.w3.org/2001/XMLSchema
to my WSDL file. Then I get
org.xml.sax.SAXException: Error: URI=file:/c:/axis/BO.wsdl Line=1393: Undeclared prefix
        at org.apache.axis.utils.XMLUtils$ParserErrorHandler.error(XMLUtils.java:619)
        at org.apache.crimson.parser.Parser2.error(Unknown Source)
        at org.apache.crimson.parser.Parser2.processName(Unknown Source)
        at org.apache.crimson.parser.Parser2.maybeElement(Unknown Source)
        at org.apache.crimson.parser.Parser2.content(Unknown Source)
        at org.apache.crimson.parser.Parser2.maybeElement(Unknown Source)
        at org.apache.crimson.parser.Parser2.content(Unknown Source)
        at org.apache.crimson.parser.Parser2.maybeElement(Unknown Source)
        at org.apache.crimson.parser.Parser2.parseInternal(Unknown Source)
        at org.apache.crimson.parser.Parser2.parse(Unknown Source)
        at org.apache.crimson.parser.XMLReaderImpl.parse(Unknown Source)
        at org.apache.crimson.jaxp.DocumentBuilderImpl.parse(Unknown Source)
        at org.apache.axis.utils.XMLUtils.newDocument(XMLUtils.java:322)
        at org.apache.axis.utils.XMLUtils.newDocument(XMLUtils.java:367)
        at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:384)
        at org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:245)
        at java.lang.Thread.run(Unknown Source)
So I add
xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/
Now I am getting other errors
C:\axis>java -classpath C:\j2sdk1.4.2_18\lib\tools.jar;C:\axis\axis-1_1\lib\axis.jar;C:\axis\axis-1_1\lib\axis-ant.jar;C:\axis\axis-1_1\lib\commons-lo
gging.jar;C:\axis\axis-1_1\lib\commons-discovery.jar;C:\axis\axis-1_1\lib\saaj.jar;C:\axis\axis-1_1\lib\jaxrpc.jar;C:\axis\axis-1_1\lib\wsdl4j.jar;C:\
axis\axis-1_1\lib\log4j-1.2.8.jar org.apache.axis.wsdl.WSDL2Java -a c:\axis\BO.wsdl
WSDLException (at /definitions/message[1]/part): faultCode=INVALID_WSDL: Unable to determine namespace of 'di_Wait_Profiling_Task_Output:PF_Task_Response'.:
        at com.ibm.wsdl.util.xml.DOMUtils.getQName(Unknown Source)
        at com.ibm.wsdl.util.xml.DOMUtils.getQualifiedAttributeValue(Unknown Source)
        at com.ibm.wsdl.xml.WSDLReaderImpl.parsePart(Unknown Source)
        at com.ibm.wsdl.xml.WSDLReaderImpl.parseMessage(Unknown Source)
        at com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(Unknown Source)
        at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
        at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
        at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
        at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:406)
        at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:393)
        at org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:245)
        at java.lang.Thread.run(Unknown Source)
So I was curious if this was supposed to be the complete WSDL file?
Thanks in advance

I tried with 11.7.3.7, using the following command and using axis jar files that are bundled with DI
it did generate the java classes successfully
I don't think there is much difference between 11.7.3.5 and 11.7.3.7
java -classpath "C:\j2sdk1.4.2_18\lib\tools.jar;%LINK_DIR%\ext\lib\axis.jar;%LINK_DIR%\ext\lib\commons-logging.jar;%LINK_DIR%\ext\lib\commons-discovery.jar;%LINK_DIR%\ext\lib\saaj.jar;%LINK_DIR%\ext\lib\jaxrpc.jar;%LINK_DIR%\ext\lib\wsdl4j.jar;%LINK_DIR%\ext\lib\log4j-1.2.8.jar" org.apache.axis.wsdl.WSDL2Java -a c:\axis\BO.wsdl
let me know if its works for you, otherwise will check in 11.7.3.5
how are you using these classes ? for calling a Job published as web service, you could write a simple java client application and passing the SOAP request for calling the batch job

WSDL file from sap

Hi all
I need sap data as WSDL file for a requirement. What I am thinking is to create a BAPI and export to WSDL. Is it possible to do this? I am in a conception that using WSDL file, the SAP data is always latest. hope this is correct.
Else pls let me know how we have to export sap data as WSDL/XML schema as applicable.
I have to use this WSDL file in Adobe form to create a offline interactive PDF which should always contain the latest data when opened.
I know that ABAP WD is one option but that is not suitable for me because, I have to get this PDF doc uploaded to a collaborative environment(similar to forums) and whenever the user downloads the document , it has to fetch data from SAP.
Please help me proceed further.
Thanks in advance
Karthika

I fail to see how this question is Web Dynpro ABAP related. You even state in your description that Web Dynpro ABAP isn't a suitable option for your requirement. Then why post the question in the Web Dynpro ABAP forum? Please post your questions in the correct forum.

To keep a back up of original Jpeg files from camera or not?

Somewhat new to Mac coming from PC world. I also have a PC lap top that I have some of my pictures on. I have all of my actual jpeg files from my old PC on the Mac and then have imported copies of them into iphoto.
I have searched these discussions and can't find my question answered so hope I can explain and get an answer.
I think I understand how iphoto works and about the library. I am enjoying using it, but with problems others have from time to time I would think most people would still want a backup of their actual jpeg files stored on DVDs or external hard disk is storage space is not a problem. I can see if you only use a Mac and keep a backup of your iphoto library you would be fine, but if you changed back to a PC this library backup would not work and you would still want a copy of all your original jpeg files to start over on a PC.
Do any of you keep a backup of your original files backed up?

I definitely know not to make any changes in the iphoto library itself.
Good that goes a LONG way toward avoiding problesm
If I understand you correctly is there a way from within iPhoto to isolate all of your orginal files, if that is what you want, to transfer just them to an external in order to then load on a different PC computer i.e. my laptop?
iPhoto does that - all originals are in a folder in the iPhoto library named "originals" - you can copy it for use somewhere else (I do not recommend it but you can and if you make no mistakes it is safe - i make lots of mistakes so sty out of my iPhoto library) or select the Photos you want elsewhere and export with kind = original
I have a 2TB WD external drive I am using with Time Machine, so my iPhoto library is backed up there. Would you also suggest, to be perfectly safe, backing up the iPhoto library to a 2nd external.
I personally do that - it is certainly a personal choice and and be overkill - but I do it
As I add new pictures to iPhoto and backup to this 2nd external would the library file just overwrite the previous backup?
again your choice - I keep about 4 versions plus the current one on my internal drive which get daily cloned to my EHD - essentially overwriting the old so my EHD is never more thatn a day behind my main system (except when I do an major upgrade and turn the EHD off for two to three weeks to be sure the upgrade went ok)
I don't want to sound paranoid, but I just cringe when reading posts of people losing all of there pictures.
Its hard not to be paranoid when everyone is out to get you - and hard to be too paranoid when it comes to backups - bad stuff will happen
But as to reading about people losing all of their photos - that does not happen - in all of the posts I've read here I have not seen a single case of iPhoto or the Mac losing a single photo - iPhoto has lost track of them (mostly due to user mistakes - sometimes computer glitches) and people have had to start over with their originals losing their keywords, edits, etc but no photos actually lost
So the short answer - I like having both a clone and a TM backup plus the other ones I make - it may be too much for you or you may do more - TD adds a web based backup to his scheme for example
LN

How to view original video files from my Canon Vixia

Hi -
I have a Canon Vixia camcorder and I cannot find a way to view the original mts files on my iMac. I hate to say this, but my old windows laptop to does this without any issue, so that's what I'll continue to do until something changes.
When I mount the camera on my Mac, it only shows one giant AVCHD file. I have read the posts about using iMovie to import the AVCHD file and then export the individual clips, but frankly that ***** for a few different reasons that I don't really feel the need to explain.
Why does Mac not allow me to simply view the files as they are on the camera? I don't edit with iMovie, I edit with Premiere and the original mts files are just fine with me. I love my iMac and all my other Apple products, but let me view my files! ...please?
Thanks
Joey

AVCHD utilizes a proprietary container format. The MTS files are in there, you just have to know where to look.
Navigate to the root directory of the memory card. You should see a rather large (depending on how many clips are on there) file called PRIVATE. You need to right-click that and select "Show Package Contents". Inside, find the file AVCHD, right-click it and select "Show Package Contents". Inside, find the file BDMV, right-click it and select "Show Package Contents". Inside, find the folder STREAM and open it. You should find the MTS files there.
HTH.

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.

Exposing original WSDL files from EJB3/JAX-WS

Similar Messages

Maybe you are looking for