Problem with WSDL generated with wscompile JAX-RPC

Ok well I have successfully built a Web Service (From an existing wsdl) and Static Stub Client they work perfectly. I then I tried to connect to it using a Delphi Web Service Client. The client cant change, the problem I am getting is it is requesting using the variable name I am using and the WSDL has String_1.
Ie. it gives me:
unexpected element name: expected=String_1, actual= {targetNameSpace} [Variable Name]
I suspect this is a problem with how the WSDL is generated any suggestions?

THanks for the response, I originally used axis WSDL2Java. And only used the interface class. I think this is where my whole thing fell down. Although this worked with a static stub client that I used.
I have now generated the server side java files using wscompile and am l looking how to implement the server. It doesn't look like it has a implementation class there. And there isn't much information on how to do it.

Similar Messages

Problems installing PDF Generator with Workflow

Hello,
I was trying to combine PDF Generator with LiveCycle Workflow 7.2. I followed the instructions in the document 'Integrating Adobe LiveCycle Products'. Now I'm getting a Java error message when I try to access the Administrator login:
HTTP Status 500 -
type Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
javax.servlet.ServletException: com.adobe.admin.bean.FeaturesBean.validateUserSession(Ljavax/servlet/http/HttpServletRequ est;)V
org.apache.jasper.runtime.PageContextImpl.doHandlePageException(PageContextImpl.java:825)
org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:758)
org.apache.jsp.access_jsp._jspService(access_jsp.java:162)
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94)
javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:324)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
com.adobe.idp.um.auth.filter.PortalSSOFilter.doFilter(PortalSSOFilter.java:105)
com.adobe.framework.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:1 61)
root cause
java.lang.NoSuchMethodError: com.adobe.admin.bean.FeaturesBean.validateUserSession(Ljavax/servlet/http/HttpServletRequ est;)V
org.apache.jsp.access_jsp._jspService(access_jsp.java:97)
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94)
javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:324)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
com.adobe.idp.um.auth.filter.PortalSSOFilter.doFilter(PortalSSOFilter.java:105)
com.adobe.framework.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:1 61)
Has anyone also experience these kind of problem? Or has anyone an idea where this 'validateUserSession' function is located, which *.jar, *.war or *.ear?
BTW: I checked that Workflow in running properly before I installed PDFG.
Regards, Karin

Hello,
I think I found something: the webapp.jar in adminui.war in LiveCycle.ear contains the FeatureBean class and is different once I have PDF Generator included. I tried to exchange this jar file. Now I have access again to the administrator webapp.
However, I get an error message when I try to convert images with Acrobat:
"The service to convert the document could not be looked up."
Can this have something to do with the exchange? It's a strange error message because Acrobat is installed together with PDF Generator.
Or could it be because I have also Adobe Reader 7.0.8 installed?
Any ideas would be really appreciated.
Regards, Karin

How to display value from java class with output generated with toplink

i hava a requirement of displaying (distance ie calculated in java class) with output generated by query.
ie if output is like
school name (distance)
physical address
here the school name and physical address are retrived from database.

Hi,
ValueHolders are used by the JSF internal framework. To work with an object (attributes) in a managed bean you don't need to make it returning a value holder.
Create a POJO, provide accessor methods and register it as a managed bean. Access it from JSF with EL
Frank

Problem with classes generated with .classgen

When I run the sample app from the "Using XML in Oracle Database Applications, Part 2" that generates classes, the syntax is:
java SampleMain -root MYMAIN myfile.dtd
All the elements in myfile.dtd get a class built for them, but they also reference MYMAIN as a class. That is, things like:
public MYMAIN getDocument()
return (MYMAIN)super.getCGDocument();
I would have expected that classgen would have made a class called MYMAIN, but it did not. I'm very confused. Please help.
Thanks,
-Peter
null

Check if you have MYMAIN in your
DTD file:
<!ELEMENT MYMAIN ......

A tree-view in HTML page with nodes generated with java script in run time is not visible in the UI Automation Tree. Need Help

I have a HTML page with an IFrame. Inside the Iframe there is a table with a tree view
<iframe>
<table>
<tr>
<td>
<treeview id="tv1"></treeview>
</td>
</tr>
</table>
</iframe>
In UIA, i am able to traverse till the tree view but not able to see it.
I have used the TreeWalker.RawViewWalker Field to traverse the node from the desktop Automation.RootElement.
I tried to use AutomationElement.FromPoint method to check whether i am able to get that element. Fortunately i was able to get the automation element.
i tried to get the path to root element from the node element using the TreeWalker.RawViewWalker. I was able to get the parent path to the root element.
But trying the reverse way like navigating from root element to tree node, was not getting the element for me.
Please help me with suggestions or inputs to resolve this issue.

Thanks Bernard,
It works fine with JInitiator but not working with
the JPI. For JPI what settings I need to do ??hi TKARIM and Bernard, i am having similar problem even with the Bernard's recommended setup. could you post the webutiljini.htm (i presume you are using config=test) ?
i am actually using jinitiator 1.3.1.28 with Oracle HTTP Server of OAS 10gR2) calling Forms Server 6i (f60cgi). After setting up according to Bernard's recommended setup steps, the java console showed that it loaded the icon jar file when it could not read the form, but it skipped the loading of the icon jar file once it read and started the form. How do we specify in the form to pick up the icon from the jar file instead from a directory ? Or do we need to specify ? Any ideas ?
Thx and Regards
dkklau

Batch operations with JAX-RPC

I have read a number of different tutorials about Web services and JAX-RPC, and have to come the conclusion that JAX-RPC is the correct approach to use for my project. Most of the examples I have seen involve invoking services which perform a 'one-shot' action e.g. get a Stock Quote.
My first question is that I am not sure for such 'one-shot' services, how much support there is in the API for sending/receiving arrays of data items. e.g. sending a user's data to a web service which includes an associated list of phone numbers.
Further if I wanted to send user's data which included an array of nested objects, would I have to implement a serializer/deserialiser plugin?
My main concern really is how best to handle a batch of requests to the service. My current thought is to use JAX-RPC with an xml document attachment - listing of a number of user's data and their parameters. A 'batch service' would return a response immediately then work through the document and invoke the existing 'single shot' service - which will be hosted on the same web server.
Is this approach which brings together a number of different ideas from the various JAX-RPC tutorials viable? Are they any better alternatives?
For example would it be better to implement a JAX-RPC for the single shot service requests and use JAXM for batch service requests? (On the server-side I would still be expecting the batch service to re-use the single-shot service). Can JAXM and JAX-RPC services co-exist on the same web server? I realise that there would be WSDL generated for the JAX-RPC service alone and so for a client developer there will be an inconsistency in terms of how the Web service is accessed.
Thanks in anticipation

Hello, I'll try and go through your questions one at a time:
My first question is that I am not sure for such 'one-shot' services, how much support there is in the API for
sending/receiving arrays of data items. e.g. sending a user's data to a web service which includes an
associated list of phone numbers.JAX-RPC has built in support for List type operations. There is no problem sending Arrays of information over the wire. If you were sending an Object of type User, for instance, there would be no problem with User having a List of PhoneNumber types objects as part of it's structure.
Further if I wanted to send user's data which included an array of nested objects, would I have to implement
a serializer/deserialiser plugin?Condintional No. If the nested objects contained only data structures that JAX-RPC knows how to deal with, your fine (things like java.lang.String or java.lang.Integer). However, if your nested objects contain types that JAX-RPC does not know how to deal with (i.e. java.sql.TimeStamp), you will have to write a custom serializer/deserializer just like you would if you were passing those objects without them being nested.
My main concern really is how best to handle a batch of requests to the service. My current thought is to
use JAX-RPC with an xml document attachment - listing of a number of user's data and their parameters.
A 'batch service' would return a response immediately then work through the document and invoke the
existing 'single shot' service - which will be hosted on the same web server.
Is this approach which brings together a number of different ideas from the various JAX-RPC tutorials
viable? Are they any better alternatives?As per above you shouldn't have to send an xml document attachment, but I guess you could. Also, for batch processing type tasks you probably want to look at the asychronous mode mentioned in the JAX-RPC part of the JWSDP tutorial.
For example would it be better to implement a JAX-RPC for the single shot service requests and use
JAXM for batch service requests? (On the server-side I would still be expecting the batch service to re-use
the single-shot service). Can JAXM and JAX-RPC services co-exist on the same web server? I realise
that there would be WSDL generated for the JAX-RPC service alone and so for a client developer there
will be an inconsistency in terms of how the Web service is accessed.Well, it really is up to you at this point. I assume that you want/need to use web services for access (as opposed to EJBs or any other method). So, I would look at an asychronous web service implementation.

Bug/flaw in JAX-RPC xrpcc generated output (JWSDP EA1)

I believe I have found a bug (or flaw) in how xrpcc (JWSDP EA1) is generating stubs and WSDL code as follows:
If you use simple parameter types (ints, doubles, Strings et al) then xrpcc generates a name that is based on the type (eg. String_1) rather than the
parm name (senderID) in the WSDL and stub code. I have noticed, however, that if you are using a JavaBean as an input/output parameter to/from a remote method, it generates an XMLSchema ComplexType with the proper names of subelements, so that situation seems to be OK.
I think this is a bug/flaw in xrpcc...
For example, if you try to use a remote method that looks somewhat like:
public int SendTrajectory( String senderID )
You get the following fragment generated in the WSDL output from xrpcc:
<message name="sendTrajectory">
<part name="String_1" type="xsd:string"/>
whereas I think it should use the actual parameter name for simple parameters and should look like:
<message name="sendTrajectory">
<part name="senderID" type="xsd:string"/>
I read the JAX-RPC Spec (v 0.7....pdf on the Sun web site) and it seems to allude to the fact that the names SHOULD be based on the parameter name in
section 5.5.5. where it specifically states:
"Each Java parameter (in the Java method signature) is mapped to a message part in the wsdl:message. This wsdl:message corresponds to the wsdl:input element for the mapped wsdl:operation. Each message part has a name attribute that is mapped based on the name of the Java parameter and a type attribute (an XML data type)"
...and the example the shown further down in that section of the JAX-RPC spec re-inforces this opinion.
The generated code works with the current version of JAX-RPC and xrpcc, that is not the problem. There is a bigger issue with this situation, since you
cannot (and should not) assume that a web service (even if generated with JAX-RPC) will be invoked by a client that was generated with JAX-RPC tools.
The problem is really evident when you don't use JAX-RPC to talk to a JAX-RPC generated service, since you have to use these funny names like String_1, Double_3 which have no application context semantics and thus will invariably lead to some really subtle bugs in remote calls.
We have used JAX-RPC to generate our server side web service in the normal manner. However, our client is running on an embedded Java (CLDC/MIDP
level device....on an aJile Java chip in fact) where the JAX-RPC footprint is way too massive for the confines of the MIDP/CLDC platform. So we are using the Enhydra kSoap API and libraries on the client end to invoke the back end JAX-RPC service. This works fine by the way! We have successfully invoked JAX-RPC wrapped services from the embedded Java platform. The
difficulty stems from the fact that the kSOAP api (and others) require you to bind the values of the parameters for the SOAP invocation by using the WSDL <part> name, and so these funny type-based names become visible in your client application code. Ouch!
For example, my kSOAP calls to invoke our JAX-RPC service look like this (where request is a SOAP web services request using the kSOAP API's):
request.addProperty ( "String_1", "SaJe314159" );
request.addProperty ( "Double_2", pvt.getLatitude() );
request.addProperty ( "Double_3", pvt.getLongitude() );
request.addProperty ( "Double_4", pvt.getBearing().floatValue() ) );
request.addProperty ( "Double_5", pvt.getVelocity() );Whereas it should really look like the following, based on our interface definitions:
request.addProperty ( "senderID", "SaJe314159" );
request.addProperty ( "latitude", pvt.getLatitude() );
request.addProperty ( "longitude, pvt.getLongitude() );
request.addProperty ( "bearing", pvt.getBearing().floatValue() ) );
request.addProperty ( "velocity", pvt.getVelocity() );The problem is that xrpcc generates the names as in the first example (String_1, Double_2) instead of using the parameter names (eg. "senderID, latitude).
We can work around this in two ways for now: 1) use the type-based generated name labels for the moment, or 2) go into the xrpcc generated stub code and WSDL and make manual changes. In the longer term, I'm sure you appreciate why either of these workarounds are not acceptable.
Based on the above, I think that there is a bug/flaw in this version of xrpcc (it's using a parameter type rather than a parameter name to generate the <message>/<part> element in the WSDL (and of course in the generated stubs and such).
Thoughts? Fix in EA2 perhaps?
Thanks!
....Andrzej

I've got the same problem. I edited the WSDL and regenerated both Server and Client classes and it then didn't work. Forget the error but it seemed to have incorrectly capitalised a letter in a class/method name.
I am trying to define a common WSDL doc that our suppliers must conform to when providing us with a web service. My aim is that the common WSDL will be OK for both Java-based web services and .NET based web services. I have succeeded in this task apart from the method parameter name issue. .NET (of course) does it correctly, and its WSDL correctly names the method parameters. However Java Web Services via xrpcc produce this ridiculous String_1, String_2 etc which bear no relation to the method parameters. I cannot very well go to our suppliers who are using .NET and demand that their method/function parameters are named String_1, String_2 - and wouldn't Bill be pleased with my excuse that I'm trying to get equivalence with the deficiencies of Java ?

How to generate JAX-RPC web services instead of JAX-WS webservices withOEPE

How to generate JAX-RPC web services instead of JAX-WS webservices withOEPE? I am asking this because I need to pass xmlbeans generated objects as arguments in the web method. For JAX-WS there has to be a no argument constructor for it to be able to pass in theweb method. The workshop 10.3 was able to pass the xmlbeans generated object as the web service was implemented as a JAX-RPC web service....

Ok just as I expected. So I guess I am left with the following two options
1) either I switched to using JAXB in my apps instaed of xmlbeans....
2) or if I still wanna use the old JAX-RPC web services to deploy on the Weblogic 10gR3 server i will have to create my own ant task jwsc directly......as shown below in your docs
Programming Web Services for WebLogic Server (ant tasks)
http://download.oracle.com/docs/cd/E13222_01/wls/docs92/webserv/anttasks.html
Getting Started With WebLogic Web Services Using JAX-RPC
http://download.oracle.com/docs/cd/E12840_01/wls/docs103/webserv_rpc/index.html
Will OEPE be supporting the old JAX-RPC anytime in the near future release? or have to create own build ant task to call jwsc ant task directly to compile JAX-RPC web services??

Memory leak with swf generated by Xcelsius 4.5?

Hello,
I've experienced some memory problems with swf generated with Xcelsius 4.5. I'm using Windows Vista and Internet Explorer 7.
I noticed that every time I refresh my dashboard using the F5 key, the memory used by the Internet Explorer process increases (or doubles).So, in case I need to refresh my dashboard many times, the memory used by the browser becomes definitely too much and compromises my system stability.
Does anyone have experienced this problem? Is this a memory leak? Is there a way to fix this problem?
Thank you,

That's the trick who does it, thank you!

How to create JAX-RPC WS manually

I have a static WSDL file. Do you have any step by step instructions that show how to generate a JAX-RPC artifacts manually please? I can't do it using JDeveloper because my WSDL file is big so I got out of memory error when I tried to use JDev even though I increased the VM memory for JDev to 1024M already.
That's why I have no choice but to generate the JAX-RPC artifacts manually.
I'm using 10.3.1 WL.
Thanks

Ok just as I expected. So I guess I am left with the following two options
1) either I switched to using JAXB in my apps instaed of xmlbeans....
2) or if I still wanna use the old JAX-RPC web services to deploy on the Weblogic 10gR3 server i will have to create my own ant task jwsc directly......as shown below in your docs
Programming Web Services for WebLogic Server (ant tasks)
http://download.oracle.com/docs/cd/E13222_01/wls/docs92/webserv/anttasks.html
Getting Started With WebLogic Web Services Using JAX-RPC
http://download.oracle.com/docs/cd/E12840_01/wls/docs103/webserv_rpc/index.html
Will OEPE be supporting the old JAX-RPC anytime in the near future release? or have to create own build ant task to call jwsc ant task directly to compile JAX-RPC web services??

JAX RPC extension: Problem with document/literal and MyType[]

Hi,
I have installed the JAX RPC extension and want to generate a stub from my WSDL file. The WSDL describes a document/literal binding.
Problem:
A webservice server method like:
public wineshop.model.common.SimpleProducer[] getSimpleProducerList() throws RemoteException;
is translated into a stub method like:
public UnknownType getSimpleProducerList() throws Exception {..}
Is an array of own types with the binding style "document/literal" not supported in JAX RPC 1.4 or is it just a bug?
The WSDL file is generated by JAX RPC 1.4.
I have installed JWSDP-1.5 and generated a stub with wscompile from the WSDL file. The generated stub has the correct method return type:
public wineshop.ws.client.SimpleProducer[] getSimpleProducerList()
throws java.rmi.RemoteException
It there a workaround like replacing some JDev JARs with JWSDP-1.5 to solve the problem?
Any hints are welcome.
Thanks Markus

repost.....

JAX-RPC documentliteral with -model option problems in JWSDP 2.0

Hello,
I am trying to deploy a service generated with JAX-RPC. Howeverr when I write URL (http://localhost:8080/webservicedeployable/webservice001) in a browser I am getting message: 404 Not Found: Invalid request. Appending ?WSDL shows propers wsdl code, so endpoint URL is allright.. There is my config file delow:
<?xml version="1.0" encoding="utf-8"?>
<configuration xmlns="http://java.sun.com/xml/ns/jax-rpc/ri/config">
<service name="webservice001"
           targetNamespace="http://scdjws/webservices/wsdl"
           typeNamespace="http://scdjws/webservices/types"
           packageName="com.service001">
    <interface name="service.MyServicePort" servantName="service.MyServiceImpl"/>
</service>
</configuration>I am using command:
wscompile -gen:server -f:documentliteral -s "C:\Documents and Settings\Michal\jbproject\mojservice\src\" -classpath WEB-INF/classes -d build -model webservice001.xml.gz config.xml -keepmy jaxrpc-ri.xml is:
<?xml version="1.0" encoding="utf-8"?>
<webServices xmlns="http://java.sun.com/xml/ns/jax-rpc/ri/dd"
             version="1.0"
             targetNamespaceBase="http://java.sun.com/xml/ns/jax-rpc/wsi/wsdl"
             typeNamespaceBase="http://java.sun.com/xml/ns/jax-rpc/wsi/types"
             urlPatternBase="/ws">
<endpoint name="service001"
            displayName="Service 001"
            description="This is service001"
            interface="service.MyServicePort"
            implementation="service.MyServiceImpl"
            model="/webservice001.xml.gz"/>
<endpointMapping endpointName="service001"
                   urlPattern="/webservice001"/>
</webServices>I am using Tomcat 5.5.16 and JWSDP 2.0.
Making a call to the service throws exception:
java.io.IOException: Server returned HTTP response code: 500 for URL: http://localhost:8080/webservicedeployable/webservice001
     at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:791)
Thank you in advance for all suggestion.
Michal

Hi,
I reselved the problem by just copying the FastInfoset to the jaxrpc\lib directory (I am sure this should work in a different way).
Well, the next problem I am getting is that the "XMLStreamWriter" class cannot be found. This class is contained in jsr173_api.jar.
I guess my main question is the following:
Which projects are necessary to get this simple helloWorld example to work?
I did set the JWSDP_HOME varible. Is there another setting I have to make to have all necessary jar-files available and to be able to run the samples?
Could anybody point me to a tutorial that does not only show a few lines of code (as the HelloWorld sample in the JWSDP-Tutorial) but that would instead lead me through a step-by-step sample application that I write by myself and actually runs at the end? The example in the JWSDP-Tutorial uses all kinds of existing config files which are not explained.
Thanks for your help.

Problems with J2ME and JAX-RPC

Hi,
I am trying to write a J2ME web service client. I have generated the stub classes with wscompile from the wsdl document at http://www.webservicex.net/stockquote.asmx?WSDL. However, when I try to run the MIDlet I always get the following error message:
[wtkpreverify] Error preverifying class javax.xml.rpc.encoding.Serializer
[wtkpreverify] java/lang/NoClassDefFoundError: java/io/Serializable
I am using Eclipse 3.1, Antenna 0.9.13, the Web Service Development Kit 2.0 and the WTK 2.3 beta.
The necessary jars (the WTK libs, rt.jar from the JRE, activation, mail, saaj and jax-rpc libraries from the WSDK) have been included in my classpath.
Does anybody know how to fix this problem? Any help is much appreciated.
Regards,
Motivated

Thanks, that was my mistake.
Instead of using wscompile, you must generate the stub classes with the WTK. Then, you set a reference to the j2me-ws.jar (JSR-172). No additional libraries from the Web Service Development Kit are required.

Problems with jax-rpc HelloWorld sample

Hi
Running on Linux Red Hat 9.0
Jwsdp 1.3
I'm following the jwsdp tutorial trying to build the jax-rpc HelloWorld sample. I do what the tutorial says:
"ant build" in the sample directory but it "Fails" with this message:
init:
[echo] -------- HelloWorld Sample --------
prepare:
generate-server:
edit-config:
[wscompile] modeler error: failed to parse document at "/home/medimg/pablo/jwsdp-1.3/jaxrpc/samples/HelloWorld//home/medimg/pablo/jwsdp-1.3/jaxrpc/samples/HelloWorl
d/etc/HelloWorldService.wsdl": java.io.FileNotFoundException: /home/medimg/pablo/jwsdp-1.3/jaxrpc/samples/HelloWorld/home/medimg/pablo/jwsdp-1.3/jaxrpc/samples/Hell
oWorld/etc/HelloWorldService.wsdl (No such file or directory)
[wscompile] at com.sun.xml.rpc.processor.modeler.wsdl.WSDLModelerBase.buildModel(WSDLModelerBase.java:179)
[wscompile] at com.sun.xml.rpc.processor.config.ModelInfo.buildModel(ModelInfo.java:85)
[wscompile] at com.sun.xml.rpc.processor.Processor.runModeler(Processor.java:61)
[wscompile] at com.sun.xml.rpc.tools.wscompile.CompileTool.run(CompileTool.java:564)
[wscompile] at com.sun.xml.rpc.util.ToolBase.run(ToolBase.java:40)
[wscompile] at com.sun.xml.rpc.tools.ant.Wscompile.execute(Wscompile.java:686)
[wscompile] at org.apache.tools.ant.Task.perform(Task.java:341)
[wscompile] at org.apache.tools.ant.Target.execute(Target.java:309)
[wscompile] at org.apache.tools.ant.Target.performTasks(Target.java:336)
[wscompile] at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
[wscompile] at org.apache.tools.ant.Project.executeTargets(Project.java:1255)
[wscompile] at org.apache.tools.ant.Main.runBuild(Main.java:609)
[wscompile] at org.apache.tools.ant.Main.start(Main.java:196)
[wscompile] at org.apache.tools.ant.Main.main(Main.java:235)
[wscompile] CAUSE:
[wscompile] failed to parse document at "/home/medimg/pablo/jwsdp-1.3/jaxrpc/samples/HelloWorld//home/medimg/pablo/jwsdp-1.3/jaxrpc/samples/HelloWorld/etc/HelloWorl
dService.wsdl": java.io.FileNotFoundException: /home/medimg/pablo/jwsdp-1.3/jaxrpc/samples/HelloWorld/home/medimg/pablo/jwsdp-1.3/jaxrpc/samples/HelloWorld/etc/Hell
oWorldService.wsdl (No such file or directory)
[wscompile] at com.sun.xml.rpc.wsdl.parser.WSDLParser.parseDefinitionsNoImport(WSDLParser.java:252)
[wscompile] at com.sun.xml.rpc.wsdl.parser.WSDLParser.parseDefinitions(WSDLParser.java:170)
[wscompile] at com.sun.xml.rpc.wsdl.parser.WSDLParser.parse(WSDLParser.java:162)
[wscompile] at com.sun.xml.rpc.processor.modeler.wsdl.WSDLModelerBase.buildModel(WSDLModelerBase.java:126)
[wscompile] at com.sun.xml.rpc.processor.config.ModelInfo.buildModel(ModelInfo.java:85)
[wscompile] at com.sun.xml.rpc.processor.Processor.runModeler(Processor.java:61)
[wscompile] at com.sun.xml.rpc.tools.wscompile.CompileTool.run(CompileTool.java:564)
[wscompile] at com.sun.xml.rpc.util.ToolBase.run(ToolBase.java:40)
[wscompile] at com.sun.xml.rpc.tools.ant.Wscompile.execute(Wscompile.java:686)
[wscompile] at org.apache.tools.ant.Task.perform(Task.java:341)
[wscompile] at org.apache.tools.ant.Target.execute(Target.java:309)
[wscompile] at org.apache.tools.ant.Target.performTasks(Target.java:336)
[wscompile] at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
[wscompile] at org.apache.tools.ant.Project.executeTargets(Project.java:1255)
[wscompile] at org.apache.tools.ant.Main.runBuild(Main.java:609)
[wscompile] at org.apache.tools.ant.Main.start(Main.java:196)
[wscompile] at org.apache.tools.ant.Main.main(Main.java:235)
[wscompile] CAUSE:
[wscompile] java.io.FileNotFoundException: /home/medimg/pablo/jwsdp-1.3/jaxrpc/samples/HelloWorld/home/medimg/pablo/jwsdp-1.3/jaxrpc/samples/HelloWorld/etc/HelloWor
ldService.wsdl (No such file or directory)
[wscompile] at java.io.FileInputStream.open(Native Method)
[wscompile] at java.io.FileInputStream.<init>(FileInputStream.java:106)
[wscompile] at java.io.FileInputStream.<init>(FileInputStream.java:66)
[wscompile] at sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:69)
[wscompile] at sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:156)
[wscompile] at java.net.URL.openStream(URL.java:913)
[wscompile] at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(XMLEntityManager.java:947)
[wscompile] at org.apache.xerces.impl.XMLEntityManager.startEntity(XMLEntityManager.java:893)
[wscompile] at org.apache.xerces.impl.XMLEntityManager.startDocumentEntity(XMLEntityManager.java:846)
[wscompile] at org.apache.xerces.impl.XMLDocumentScannerImpl.setInputSource(XMLDocumentScannerImpl.java:264)
[wscompile] at org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:513)
[wscompile] at org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:595)
[wscompile] at org.apache.xerces.parsers.XMLParser.parse(XMLParser.java:152)
[wscompile] at org.apache.xerces.parsers.DOMParser.parse(DOMParser.java:253)
[wscompile] at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:206)
[wscompile] at com.sun.xml.rpc.wsdl.parser.WSDLParser.parseDefinitionsNoImport(WSDLParser.java:248)
[wscompile] at com.sun.xml.rpc.wsdl.parser.WSDLParser.parseDefinitions(WSDLParser.java:170)
[wscompile] at com.sun.xml.rpc.wsdl.parser.WSDLParser.parse(WSDLParser.java:162)
[wscompile] at com.sun.xml.rpc.processor.modeler.wsdl.WSDLModelerBase.buildModel(WSDLModelerBase.java:126)
[wscompile] at com.sun.xml.rpc.processor.config.ModelInfo.buildModel(ModelInfo.java:85)
[wscompile] at com.sun.xml.rpc.processor.Processor.runModeler(Processor.java:61)
[wscompile] at com.sun.xml.rpc.tools.wscompile.CompileTool.run(CompileTool.java:564)
[wscompile] at com.sun.xml.rpc.util.ToolBase.run(ToolBase.java:40)
[wscompile] at com.sun.xml.rpc.tools.ant.Wscompile.execute(Wscompile.java:686)
[wscompile] at org.apache.tools.ant.Task.perform(Task.java:341)
[wscompile] at org.apache.tools.ant.Target.execute(Target.java:309)
[wscompile] at org.apache.tools.ant.Target.performTasks(Target.java:336)
[wscompile] at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
[wscompile] at org.apache.tools.ant.Project.executeTargets(Project.java:1255)
[wscompile] at org.apache.tools.ant.Main.runBuild(Main.java:609)
[wscompile] at org.apache.tools.ant.Main.start(Main.java:196)
[wscompile] at org.apache.tools.ant.Main.main(Main.java:235)
[wscompile] error: modeler error: failed to parse document at "/home/medimg/pablo/jwsdp-1.3/jaxrpc/samples/HelloWorld//home/medimg/pablo/jwsdp-1.3/jaxrpc/samples/He
lloWorld/etc/HelloWorldService.wsdl": java.io.FileNotFoundException: /home/medimg/pablo/jwsdp-1.3/jaxrpc/samples/HelloWorld/home/medimg/pablo/jwsdp-1.3/jaxrpc/sampl
es/HelloWorld/etc/HelloWorldService.wsdl (No such file or directory)
[wscompile] Command invoked: wscompile -d /home/medimg/pablo/jwsdp-1.3/jaxrpc/build/samples/HelloWorld/classes/server -import -keep -model /home/medimg/pablo/jwsdp-
1.3/jaxrpc/build/samples/HelloWorld/model-wsdl-rpcenc.xml.gz -Xprintstacktrace /home/medimg/pablo/jwsdp-1.3/jaxrpc/samples/HelloWorld/etc/config.xml -classpath /hom
e/medimg/pablo/jwsdp-1.3/jwsdp-shared/lib/mail.jar:/home/medimg/pablo/jwsdp-1.3/jwsdp-shared/lib/activation.jar:/home/medimg/pablo/jwsdp-1.3/jaxp/lib/jaxp-api.jar:/
home/medimg/pablo/jwsdp-1.3/jaxp/lib/endorsed/dom.jar:/home/medimg/pablo/jwsdp-1.3/jaxp/lib/endorsed/sax.jar:/home/medimg/pablo/jwsdp-1.3/jaxp/lib/endorsed/xalan.ja
r:/home/medimg/pablo/jwsdp-1.3/jaxp/lib/endorsed/xercesImpl.jar:/home/medimg/pablo/jwsdp-1.3/jaxrpc/lib/jaxrpc-api.jar:/home/medimg/pablo/jwsdp-1.3/jaxrpc/lib/jaxrp
c-spi.jar:/home/medimg/pablo/jwsdp-1.3/jaxrpc/lib/jaxrpc-impl.jar:/home/medimg/pablo/jwsdp-1.3/saaj/lib/saaj-api.jar:/home/medimg/pablo/jwsdp-1.3/saaj/lib/saaj-impl
.jar:/home/medimg/pablo/jwsdp-1.3/jwsdp-shared/lib/relaxngDatatype.jar:/home/medimg/pablo/jwsdp-1.3/jwsdp-shared/lib/xsdlib.jar:/home/medimg/pablo/jwsdp-1.3/jwsdp-s
hared/lib/jax-qname.jar:/home/medimg/pablo/jwsdp-1.3/apache-ant/lib/ant.jar:/home/medimg/pablo/jwsdp-1.3/jaxrpc/samples/HelloWorld/${compile.classpath}
BUILD FAILED
file:/home/medimg/pablo/jwsdp-1.3/jaxrpc/samples/HelloWorld/build.xml:98: wscompile failed
I took a look into the etc/config.xml file and the path location of HelloWorldService.wsdl is fine as follows
"/home/medimg/pablo/jwsdp-1.3/jaxrpc/samples/HelloWorld/etc/HelloWorldService.wsdl"
BUT.. after "ant build", the path in th config.xml file automatically change for:
"/home/medimg/pablo/jwsdp-1.3/jaxrpc/samples/HelloWorld//home/medimg/pablo/jwsdp-1.3/jaxrpc/samples/HelloWorld/etc/HelloWorldService.wsdl"
Anybody knows how to solve this problem
HELP !!!
J.Pablo

Hi,
I guess you need some changes in your build script.
One solution would be to specify correct value for location attribute in your config.xml and then
uncomment the call to "edit-config" target as show below in your build.xml file:
<target name="generate-server" depends="prepare">

-Amol

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.

Problem with WSDL generated with wscompile JAX-RPC

Similar Messages

Maybe you are looking for