JWSDP 2.0 JAX-RPC example problem Fast Infoset

Hi,
I installed JWSDP 2.0 and and Tomcat 5.0 for JWSDP. The server runs fine and the example HelloWorld is accessible (I can see the WSDL file in my browser: http://localhost:8080/jaxrpc-HelloWorld/hello?WSDL).
The Problem is that I can not run the client: I tried "ant run-client". The error occurs while trying to create a stub in the file "HelloClient.java" with the following line of code:
stub = (HelloIF_Stub) (helloWorldService.getHelloIFPort());
This is the error I get:
[java] Exception in thread "main" java.lang.NoClassDefFoundError: org/jvnet/fastinfoset/FastInfosetSource
[java] at hello.HelloWorldService_Impl.getHelloIFPort(HelloWorldService_Impl.java:59)
[java] at hello.HelloClient.setUp(HelloClient.java:68)
[java] at hello.HelloClient.main(HelloClient.java:45)
[java] Java Result: 1
I am not sure about the structure of the application, so I don't know where to look for the "FastInfosetSurce" file.
Thanks for any help.
Best regards.

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.

Similar Messages

Help install jwsdp 1.0 and run JAX-RPC example

I installed jwsdp1.0 today and I tried to run the Hello world example for JAX-RPC (http://java.sun.com/webservices/docs/1.0/tutorial/doc/JAXRPC3.html).
The problem is with any command passed at the console (ant command or startup (tomcat), deploytool, etc) I always get the following message : Exception in thread "main" java.lang.NoClassDefFoundError: Files/Microsoft.
The operating system in win XP and jre is 1.4.0.
The variables I used are JAVA_HOME (D:\Java\j2sdk1.4.0)
and JWSPD_HOME (d:\java\jwsdp-1_0). Both bin folder are setup on the path variable (%JAVA_HOME%\bin;%JWSPD_HOME%\bin).
Help will be very much appreciated

Maybe this is just a typo in your post, but the variable name should be JWSDP_HOME, not JWSPD_HOME.
Mike

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.....

[Beginner] Help! How to change the packet name for an jax-rpc example

Hi
I am new to the JWSDP, I tried to build and deploy the helloservice application (the example in
tutorial), it works fine. But I want to change the packet name from helloservice to books, it
returns error message during the building process.
Here is what I did.
I changed the folder name from helloservice to books.
In helloIF.java and helloImp1.java, changed to "package books"
In build.properties:
example=books
war.path=${tut.root}/examples/jaxrpc/books/${dist}/${deployable.war}
context.path=${hello.context}
portable.war=${context.path}-portable.war
deployable.war=${context.path}.war
In jaxrpc-ri.xml,
<?xml version="1.0" encoding="UTF-8"?>
<webServices
xmlns="http://java.sun.com/xml/ns/jax-rpc/ri/dd"
version="1.0"
targetNamespaceBase="urn:foo"
typeNamespaceBase="urn:foo"
urlPatternBase="/ws">
<endpoint
name="MyHello"
displayName="HelloWorld Service"
description="A simple web service"
interface="books.HelloIF"
model="/WEB-INF/model.gz"
implementation="books.HelloImpl"/>
<endpointMapping
endpointName="MyHello"
urlPattern="/hello"/>
</webServices>
In config-interface.xml,
<?xml version="1.0" encoding="UTF-8"?>
<configuration
xmlns="http://java.sun.com/xml/ns/jax-rpc/ri/config">
<service
name="MyHelloservice"
targetNamespace="urn:foo"
typeNamespace="urn:foo"
packageName="books">
<interface name="books.HelloIF"/>
</service>
</configuration>
When I run "ant build", it returns the following error message:
run-wscompile:
[echo] Running wscompile:
[echo] C:\jwsdp-1.3\apache-ant\../jaxrpc/bin/wscompile.bat -define -d bui
ld -nd build -classpath build config-interface.xml -model build/mo
del.gz
[exec] error parsing configuration file: XML parsing error: com.sun.xml.rpc
.sp.ParseException:1: com.sun.xml.rpc.sp/P-067
[exec] Result: 1
All I want to do is just change the packet name, anyone know how to do it?
Please help me.
Thank you.

For future reference, please post JAXRPC related questions to [email protected]
There is something syntatically wrong with your config.xml. Try reverting back to the original, and try that. Then try modifying it again making sure to only change the packageName.

JWSDP 1.4, JAX-RPC, wscompile, http proxies

I have a JAX-RPC client that works properly. However, I'm trying to modify the client so that RPC calls can go through an http proxy prior to reaching the web service.
Here are some of the problems I'm experiencing:
There are posts on this site, and elsewhere on the net, stating that the wscompile -httpproxy:host:port option can be used to provide this solution. However, wscompile generates the same exact code - whether the httpproxy option is used or not. Is this a problem in JWSDP 1.4?
There are also posts that state to use properties, such as http.proxyHost or proxyHost. I've used several versions of this solution (while using a sniffer to verify network activity), but all that happens is that the code continues to call directly to the web service - not the http proxy. Makes me think these properties are only useful when using http directly. Many of the posts I've seen regarding this are two years old, and I've seen at least three different opinions on how the property strings should be named. Anybody know the real solution?

For me these system properties do work:
proxyHost, proxyPort (maybe also http.proxyHost, http.proxyPort) for Http
https.proxyHost, https.proxyPort for Https
The nice thing is that from a WebStart application or the plug-in these properties are set automatically from the browser configuration if not reconfigured manually.

JAX-RPC client problems and proxy

I have deployed a JAX-RPC service in JBoss, but on the client side, I am getting NullPointerException when I attempt to access the service. I believe I'm not creating the proxy in the client properly. Where I need help is:
1. What should the proper ENDPOINT URI be for the service (my variable "destination" shown below).
2. What should the code in createProxy() look like?
WEB Services Shows:
===================
VehicleInfoService ACTIVE
Address: http://myhost:8080/VehicleInfoService/vehicle
WSDL: http://myhost:8080/VehicleInfoService/vehicle?WSDL
Port QName: {http://myhost:8080/wsdl/VehicleInfoService}VehicleInfoServiceIFPort
Remote interface: testsoap.VehicleInfoServiceIF
Implementation class: testsoap.VehicleInfoServiceImpl
Model: http://myhost:8080/VehicleInfoService/vehicle?model
CLIENT CODE
============
import javax.xml.rpc.*;
import javax.xml.rpc.Stub;
import testsoap.*;
public class TestSOAP
VehicleInfoServiceIF vehicleInfoServiceInf;
private String statusMessage = null;
private static String destination = "http://myhost:8080/VehicleInfoService/v
ehicle";
public TestSOAP()
try
Stub stub = createProxy();
// Address of the service
stub._setProperty(javax.xml.rpc.Stub.ENDPOINT_ADDRESS_PROPERTY,
destination);
vehicleInfoServiceInf = (VehicleInfoServiceIF)stub;
catch (Exception ex)
statusMessage = "Error creating Proxy stub: " + ex.getMessage();
private static Stub createProxy()
return(Stub)(new VehicleInfoService_Impl());

To reply to own posting, I finally discovered that I had a problem with my config.xml file. Once I corrected that, I was able to modify the createProxy entry to:
private static Stub createProxy()
return(Stub)(new testacp.VehicleInfoService_Impl().getVehicleInfoServiceIFPo
rt());
Corrected config.xml:
<?xml version="1.0" encoding="UTF-8"?>
<configuration
xmlns="http://java.sun.com/xml/ns/jax-rpc/ri/config">
<wsdl location="http://mybox:8080/VehicleInfoService/vehicle?WSDL"
packageName="testsoap"/>
</configuration>
These changes fixed my problem. With the correct entries in config.xml, I no longer got compile errors with "getVehicleInfoServiceIFPort Not Found".

JAX-RPC and DataHandler

Sorry, I know there has been lots of discussion about sending files with JAX-RPC in this forum, but I haven't found any answers to my problem.
I got the impression that all I needed to do was to write a service having a DataHandler as a method parameter or a return type and JAX-RPC would automatically send it as attachment, but all I got was this error message:
no serializer is registered for (class javax.activation.DataHandler, {http://java.sun.com/jax-rpc-ri/internal}datahandler)
So what else I need to do to get this working? Is there any documentation explaining this, at least the Java Web Services Tutorial doesn't event mention the possibility of sending files.
Heikki

You can use DataHandler classes to add files to your web service messages. You would need to create a client side DataHandler and a server side DataHandler. The Web Service Tutorial doesn't say DataHandler but it is mentioned. Look at the web service tutorial for web service pack 1.3. Chapter 12 --> Advanced JAX-RPC Examples --> SOAP Message Handlers Example.
The basic jist is you manually manipulate the soap message going back and forth.

Need HELP passing raw SOAP to JAX-RPC Web Service

Ive recently downloaded the web services development kit from the SUN site and have got all the examples to work fine.
What I am now trying to do is pass RAW SOAP to the HelloWorld JAX-RPC example,
Ive managed to get the service to call the sayHello function with no params which returns 'Hello NULL'.
I can't however get any parameters to be passed to the sayHello function,
Below is the existing SOAP ive got calling the function with no params.
<?xml version="1.0"?>
<soap:Envelope soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body><sayHello xmlns="http://hello.org/wsdl">????????????</sayHello></soap:Body></soap:Envelope>
If anybody could tell me what I need to replace ???????????? with then I would be more than gratefull.
P.s If I changed the webservice to accept multiple arguments what would I need to put in my SOAP?
Yours,
Cris.

Thanks for your help on this one. However there is still one thing I don`t understand.
In the example SOAP I posted on the orignal message I have added the namespace ns1 pointing to
http://hello.org/wsdl
The example you posted goes to http://caller.org/wsdl
below is SOAP you posted for me.
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:ns0="http://caller.org/wsdl"
env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<env:Body>
<ns0:sayHello>
<String_1 xsi:type="xsd:string">some text</String_1>
</ns0:sayHello>
</env:Body>
</env:Envelope>
This returns me an error! However If I change ns0 to point to http://hello.org/wsdl it all works perfectly.....
If you open a browser and go to http://hello.org/wsdl OR http://caller.org/wsdl neither URL points to anything!!!!!!! All the other namespaces used point to valid XML Schemas, which makes sense.
So how can this SOAP message work if the namespace ns0 is nothing???????????
Yours,
Cris.

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.

WL 8.1 and JAX-RPC 1.1 (JWSDP 1.3) problems

I have developed several web services using Sun's JWSDP 1.3. It deploys just fine
in WebLogic 8.1 and I can view the WSDL, etc. with no problems. I have written
a simple test client to call the service and this is where I get errors.
The server error is:
Apr 14, 2004 9:43:00 AM com.sun.xml.rpc.server.http.JAXRPCServletDelegate doPost
SEVERE: caught throwable
java.lang.NoSuchMethodError: javax.xml.soap.SOAPElement.normalize()V
at com.sun.xml.rpc.streaming.XmlTreeReader.parse(XmlTreeReader.java:129)
at com.sun.xml.rpc.streaming.XmlTreeReader.next(XmlTreeReader.java:100)
at com.sun.xml.rpc.streaming.XMLReaderBase.nextContent(XMLReaderBase.jav
a:24)
at com.sun.xml.rpc.streaming.XMLReaderBase.nextElementContent(XMLReaderB
ase.java:42)
at com.sun.xml.rpc.server.StreamingHandler.handle(StreamingHandler.java:
108)
at com.sun.xml.rpc.server.http.JAXRPCServletDelegate.doPost(JAXRPCServle
tDelegate.java:316)
at com.sun.xml.rpc.server.http.JAXRPCServlet.doPost(JAXRPCServlet.java:6
9)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run
(ServletStubImpl.java:971)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:402)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:305)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationActio
n.run(WebAppServletContext.java:6350)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
dSubject.java:317)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
118)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
rvletContext.java:3635)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
pl.java:2585)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
The client error is:
java.rmi.ServerException: JAXRPC.JAXRPCSERVLET.28: Missing port information
     at com.sun.xml.rpc.client.StreamingSender._raiseFault(StreamingSender.java:372)
     at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:224)
     at com.sun.xml.rpc.client.dii.CallInvokerImpl.doInvoke(CallInvokerImpl.java:61)
     at com.sun.xml.rpc.client.dii.BasicCall.invoke(BasicCall.java:339)
     at com.sun.xml.rpc.client.dii.CallInvocationHandler.doCall(CallInvocationHandler.java:99)
     at com.sun.xml.rpc.client.dii.CallInvocationHandler.invoke(CallInvocationHandler.java:71)
     at $Proxy0.getWorkList(Unknown Source)
     at com.workpoint.sample.client.webservices.WorkItemServiceClient.testGetWorkList(WorkItemServiceClient.java:124)
     at com.workpoint.sample.client.webservices.WorkItemServiceClient.main(WorkItemServiceClient.java:48)
I have a WAR for the web services that also includes the JAX-RPC, SAAJ, and other
JARs. This WAR is bundled in an EAR with our other applications. Like I said,
everything deploys just fine, it's at runtime the web services don't work. This
configuration (and test client) works with Tomcat, JBoss, OC4J, and WebSphere
with no problems. I've tried a bunch of different things and can't figure out
why it doesn't work with WebLogic.
Thanks for any help on this.
Mike

David,
I tried your prefer-web-inf-classes and the web services deploy, but i get an
error trying to view the wsdl. sounds like trying to get jax-rpc 1.1 web services
running in weblogic is going to be nothing but problems. anyways, here's the error
i get:
Error 500--Internal Server Error
javax.servlet.ServletException: JAXRPC.JAXRPCSERVLET.35: failed to create a template
object
     at com.sun.xml.rpc.server.http.JAXRPCServletDelegate.doGetDefault(JAXRPCServletDelegate.java:258)
     at com.sun.xml.rpc.server.http.JAXRPCServletDelegate.doGet(JAXRPCServletDelegate.java:102)
     at com.sun.xml.rpc.server.http.JAXRPCServlet.doGet(JAXRPCServlet.java:76)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:971)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:402)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6350)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
     at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3635)
     at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
"David Karr" <[email protected]> wrote:
>
This is happening because WLS already contains the JWSDP classes, but
an older
release. The jars in your web applications are not used if other jars
containing
those classes are found first.
Technically, you should be able to set the "prefer-web-inf-classes" parameter
in your weblogic.xml file to make it "prefer" classes found in WEB-INF.
There's
one not very well documented aspect of this that would be a problem for
trying
to override particular classes, but it shouldn't be a problem for your
case. The
issue is that the ClassLoader that ends up being used if you set "prefer-web-inf-classes"
(it might not be a different ClassLoader, but just imbued with modified
behavior)
actually does not allow classes in certain packages to be overridden.
I can't
remember all of the paths, but I do know that anything in "javax.xml.*"
is specifically
ALLOWED to be overridden.
However, when I went down this path a while ago, I ran into other more
obscure
exceptions that i was unable to figure out. I ended up concluding that
using the
JWSDP included with WLS 8.1 was the path of least resistance. I never
did try
altering the global classpath of the appserver to include the jwsdp 1.3
jars to
override the classes in weblogic. This is another alternate approach,
but I have
a feeling that this will cause other unexpected problems.
"Mike" <[email protected]> wrote:
I have developed several web services using Sun's JWSDP 1.3. It deploys
just fine
in WebLogic 8.1 and I can view the WSDL, etc. with no problems. I have
written
a simple test client to call the service and this is where I get errors.
The server error is:
Apr 14, 2004 9:43:00 AM com.sun.xml.rpc.server.http.JAXRPCServletDelegate
doPost
SEVERE: caught throwable
java.lang.NoSuchMethodError: javax.xml.soap.SOAPElement.normalize()V
at com.sun.xml.rpc.streaming.XmlTreeReader.parse(XmlTreeReader.java:129)
at com.sun.xml.rpc.streaming.XmlTreeReader.next(XmlTreeReader.java:100)
at com.sun.xml.rpc.streaming.XMLReaderBase.nextContent(XMLReaderBase.jav
a:24)
at com.sun.xml.rpc.streaming.XMLReaderBase.nextElementContent(XMLReaderB
ase.java:42)
at com.sun.xml.rpc.server.StreamingHandler.handle(StreamingHandler.java:
108)
at com.sun.xml.rpc.server.http.JAXRPCServletDelegate.doPost(JAXRPCServle
tDelegate.java:316)
at com.sun.xml.rpc.server.http.JAXRPCServlet.doPost(JAXRPCServlet.java:6
9)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run
(ServletStubImpl.java:971)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:402)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:305)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationActio
n.run(WebAppServletContext.java:6350)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
dSubject.java:317)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
118)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
rvletContext.java:3635)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
pl.java:2585)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
The client error is:
java.rmi.ServerException: JAXRPC.JAXRPCSERVLET.28: Missing port information
     at com.sun.xml.rpc.client.StreamingSender._raiseFault(StreamingSender.java:372)
     at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:224)
     at com.sun.xml.rpc.client.dii.CallInvokerImpl.doInvoke(CallInvokerImpl.java:61)
     at com.sun.xml.rpc.client.dii.BasicCall.invoke(BasicCall.java:339)
     at com.sun.xml.rpc.client.dii.CallInvocationHandler.doCall(CallInvocationHandler.java:99)
     at com.sun.xml.rpc.client.dii.CallInvocationHandler.invoke(CallInvocationHandler.java:71)
     at $Proxy0.getWorkList(Unknown Source)
     at com.workpoint.sample.client.webservices.WorkItemServiceClient.testGetWorkList(WorkItemServiceClient.java:124)
     at com.workpoint.sample.client.webservices.WorkItemServiceClient.main(WorkItemServiceClient.java:48)
I have a WAR for the web services that also includes the JAX-RPC, SAAJ,
and other
JARs. This WAR is bundled in an EAR with our other applications. Like
I said,
everything deploys just fine, it's at runtime the web services don't
work. This
configuration (and test client) works with Tomcat, JBoss, OC4J, andWebSphere
with no problems. I've tried a bunch of different things and can't figure
out
why it doesn't work with WebLogic.
Thanks for any help on this.
Mike

Cannot Run JAX-RPC Hello Service Example

Hello,
I am trying to run the helloservice example from the Java Web Services Tutorial v 1.3 (Chapter 12). Upon running the ant build task, I get the following error.
BUILD FAILED
file:C:/jwstutorial13/examples/jaxrpc/common/targets.xml:151: Warning: Could not
find file C:\jwstutorial13\examples\jaxrpc\helloservice\build\model.gz to copy.
I tried running the ant generate-sei-service task separately. This appears to complete successfully, yet, there is no model file generated.
Any help/suggestions/insights would be very much appreciated!
Thanks,
Sheila

Thanks!
I did that before posting my original message. I'm obviously missing something (noting jumps out at me, as far as being wrong.)
My files look like this:
File: build.xml (C:\jwstutorial13\examples\jaxrpc\helloservice\build.xml)
<!DOCTYPE project [
<!ENTITY jaxrpctargets SYSTEM "../common/targets.xml">
]>
<project name="jaxrpc-tutorial" default="build" basedir=".">
<property file="../../common/build.properties"/>
<property file="../common/build.properties"/>
<property file="build.properties"/>
&jaxrpctargets;
<target name="build" depends="build-service"
description="Executes the targets needed to build the service.">
</target>
</project>
==================================================================================
File: build.properties (C:\jwstutorial13\examples\jaxrpc\helloservice\build.properties).
example=helloservice
war.path=${tut.root}/examples/jaxrpc/helloservice/${dist}/${deployable.war}
context.path=${hello.context}
portable.war=${context.path}-portable.war
deployable.war=${context.path}.war
==================================================================================
File: build.properties (C:\jwstutorial13\examples\jaxrpc\common\build.properties)
# This file contains properties common to the tutorial examples
# for JAX-RPC.
# tut.root=C:/wspack-docs
tut.root=${tutorial.install}
hello.context=hello-jaxrpc
secure.context=secure-jaxrpc
mutualauth.context=secure-mutualauth
url.pattern=/hello
key.store=${tutorial.home}/jwstutorial13/examples/jaxrpc/mutualauth/keystore.jks
key.store.password=changeit
trust.store=${tutorial.home}/jwstutorial13/examples/jaxrpc/mutualauth/cacerts.jks
trust.store.password=changeit
hello.endpoint=http://${host}:${port}/${hello.context}${url.pattern}
secure.endpoint=http://${host}:${port}/${secure.context}${url.pattern}
mutualauth.endpoint=https://${host}:${secure.port}/${mutualauth.context}${url.pattern}
build=build
src=src
dist=dist
client.jar=client.jar
model.file=model.gz
config.wsdl.file=config-wsdl.xml
config.interface.file=config-interface.xml
jwsdp.shared=${jwsdp.home}/jwsdp-shared
jaxp.home=${jwsdp.home}/jaxp
jaxrpc.home=${jwsdp.home}/jaxrpc
saaj.home=${jwsdp.home}/saaj
wscompile.dir=${jaxrpc.home}/bin
wsdeploy.dir=${jaxrpc.home}/bin
javamail.jar=${jwsdp.shared}/lib/mail.jar
jaf.jar=${jwsdp.shared}/lib/activation.jar
jaxp-api.jar=${jaxp.home}/lib/jaxp-api.jar
dom.jar=${jaxp.home}/lib/endorsed/dom.jar
sax.jar=${jaxp.home}/lib/endorsed/sax.jar
xalan.jar=${jaxp.home}/lib/endorsed/xalan.jar
xercesImpl.jar=${jaxp.home}/lib/endorsed/xercesImpl.jar
jaxrpc-api.jar=${jaxrpc.home}/lib/jaxrpc-api.jar
jaxrpc-impl.jar=${jaxrpc.home}/lib/jaxrpc-impl.jar
jaxrpc-spi.jar=${jaxrpc.home}/lib/jaxrpc-spi.jar
commons-logging.jar=${jwsdp.shared}/lib/commons-logging.jar
saaj-api.jar=${saaj.home}/lib/saaj-api.jar
saaj-impl.jar=${saaj.home}/lib/saaj-impl.jar
relaxngDatatype.jar=${jwsdp.shared}/lib/relaxngDatatype.jar
xsdlib.jar=${jwsdp.shared}/lib/xsdlib.jar
jax-qname.jar=${jwsdp.shared}/lib/jax-qname.jar
ant.jar=${jwsdp.home}/apache-ant/lib/ant.jar
==================================================================================
This is where I thought the problem might be, but I can't determine what's wrong. The pathelements in this file, were set in build.properties ((C:\jwstutorial13\examples\jaxrpc\common\build.properties), referenced above.
File: targets.xml (C:\jwstutorial13\examples\jaxrpc\common\targets.xml)

<path id="compile.classpath">
<pathelement location="${javamail.jar}"/>
<pathelement location="${jaf.jar}"/>
<pathelement location="${jaxp-api.jar}"/>
<pathelement location="${dom.jar}"/>
<pathelement location="${sax.jar}"/>
<pathelement location="${xalan.jar}"/>
<pathelement location="${xercesImpl.jar}"/>
<pathelement location="${jaxrpc-api.jar}"/>
<pathelement location="${jaxrpc-impl.jar}"/>
<pathelement location="${jaxrpc-spi.jar}"/>
<pathelement location="${commons-logging.jar}"/>
<pathelement location="${saaj-api.jar}"/>
<pathelement location="${saaj-impl.jar}"/>
<pathelement location="${relaxngDatatype.jar}"/>
<pathelement location="${xsdlib.jar}"/>
<pathelement location="${jax-qname.jar}"/>
<pathelement location="${ant.jar}"/>
<pathelement location="${build}/shared"/>
</path>
<path id="run.classpath">
<path refid="compile.classpath"/>
<pathelement location="${dist}/${client.jar}"/>
</path>
<taskdef name="deploy" classname="org.apache.catalina.ant.DeployTask" />
<taskdef name="undeploy" classname="org.apache.catalina.ant.UndeployTask" />
<taskdef name="list" classname="org.apache.catalina.ant.ListTask" />
<taskdef name="start" classname="org.apache.catalina.ant.StartTask" />
<taskdef name="stop" classname="org.apache.catalina.ant.StopTask" />
<taskdef name="install" classname="org.apache.catalina.ant.InstallTask"/>
<taskdef name="reload" classname="org.apache.catalina.ant.ReloadTask"/>
<taskdef name="remove" classname="org.apache.catalina.ant.RemoveTask"/>
<target name="install" description="Install web application"
depends="build">
<install url="${url}" username="${username}" password="${password}"
path="/${context.path}" war="file:${example.path}/${build}"/>
</target>
<target name="deploy"
description="Deploys a Web application">
<deploy url="${url}" username="${username}" password="${password}"
path="/${context.path}" war="file:${war.path}"
/>
</target>
<target name="undeploy"
description="Undeploys a Web application">
<undeploy url="${url}" username="${username}" password="${password}"
path="/${context.path}"
/>
</target>
<target name="redeploy"
description="Undeploys and deploys a Web aplication">
<antcall target="undeploy" />
<antcall target="deploy" />
</target>
<target name="list"
description="Lists Web applications">
<echo message="Listing the applications...."/>
<list
url="${url}"
username="${username}"
password="${password}"
/>
</target>
<target name="start"
description="Starts a Web application">
<echo message="Starting the application...."/>
<start
url="${url}"
username="${username}"
password="${password}"
path="/${context.path}"
/>
</target>
<target name="stop"
description="Stops a Web application">
<echo message="Stopping the application...."/>
<stop
url="${url}"
username="${username}"
password="${password}"
path="/${context.path}"
/>
</target>
<target name="prepare"
description="Creates the build directory" >
<echo message="Creating the required directories...." />
<mkdir dir="${build}/${example}" />
</target>
<target name="prepare-dist"
description="Creates the dist directory" >
<echo message="Creating the required directories...." />
<mkdir dir="${dist}" />
</target>
<target name="set-wscompile" >
<condition property="wscompile" value="${wscompile.dir}/wscompile.bat">
<os family="windows"/>
</condition>
<condition property="wscompile" value="${wscompile.dir}/wscompile.sh">
<not>
<os family="windows"/>
</not>
</condition>
</target>
<target name="set-wsdeploy" >
<condition property="wsdeploy" value="${wsdeploy.dir}/wsdeploy.bat">
<os family="windows"/>
</condition>
<condition property="wsdeploy" value="${wsdeploy.dir}/wsdeploy.sh">
<not>
<os family="windows"/>
</not>
</condition>
</target>
<target name="compile-service" depends="prepare"
description="Compiles the server-side source code">
<echo message="Compiling the server-side source code...."/>
<javac srcdir="${src}"
destdir="${build}"
includes="*.java"
excludes="*Client.java">
<classpath refid="compile.classpath"/>
</javac>
</target>
<target name="setup-web-inf"
description="Copies files to build/WEB-INF">
<echo message="Setting up ${build}/WEB-INF...."/>
<delete dir="${build}/WEB-INF" />
<copy todir="${build}/WEB-INF/classes/${example}">
<fileset dir="${build}/${example}" />
<fileset dir="${build}/${example}" />
</copy>
<copy file="${build}/${model.file}" todir="${build}/WEB-INF" />
<copy file="web.xml" todir="${build}/WEB-INF" />
<copy file="jaxrpc-ri.xml" todir="${build}/WEB-INF" />
</target>
<target name="package-service" depends="prepare-dist"
description="Packages the WAR file">
<echo message="Packaging the WAR...."/>
<delete file="${dist}/${portable.war}" />
<jar jarfile="${dist}/${portable.war}" >
<fileset dir="${build}" includes="WEB-INF/**" />
</jar>
</target>
<target name="process-war" depends="set-wsdeploy"
description="Runs wsdeploy to generate the ties and
create a deployable WAR file">
<delete file="dist/${deployable.war}" />
<antcall target="run-wsdeploy">
<param name="param1" value="-o dist/${deployable.war} dist/${portable.war}"/>
</antcall>
</target>
<target name="run-wscompile" depends="prepare,set-wscompile"
description="Runs wscompile">
<echo message="Running wscompile:"/>
<echo message=" ${wscompile} ${param1}"/>
<exec executable="${wscompile}">
<arg line="${param1}"/>
</exec>
</target>
<target name="run-wsdeploy" depends="prepare,set-wsdeploy"
description="Runs wsdeploy">
<echo message="Running wsdeploy:"/>
<echo message=" ${wsdeploy} ${param1}"/>
<exec executable="${wsdeploy}">
<arg line="${param1}"/>
</exec>
</target>
<target name="generate-sei-service"
description="Runs wscompile to generate the model file">
<antcall target="run-wscompile">
<param name="param1" value="-define -d ${build} -nd ${build}
-classpath ${build} ${config.interface.file}
-model ${build}/${model.file}"/>
</antcall>
<delete file="${build}/MyHelloService.wsdl"/>
</target>
<target name="generate-interface"
description="Runs wscompile to generate the service endpoint
interface">
<antcall target="run-wscompile">
<param name="param1" value="-import -d ${build} -nd ${build}
-f:norpcstructures -classpath ${build} ${config.wsdl.file}"/>
</antcall>
</target>
<target name="generate-stubs"
description="Runs wscompile to generate the client stub classes">
<antcall target="run-wscompile">
<param name="param1" value="-gen:client -d ${build}
-classpath ${build} ${config.wsdl.file}"/>
</antcall>
</target>
<target name="compile-client" depends="prepare"
description="Compiles the client-side source code" >
<echo message="Compiling the client source code...."/>
<javac srcdir="${src}"
destdir="${build}"
includes="*.java">
<classpath refid="compile.classpath"/>
<classpath path="${build}" />
</javac>
</target>
<target name="package-client" depends="prepare-dist"
description="Builds the JAR file that contains the client">
<echo message="Building the client JAR file...."/>
<delete file="${dist}/${client.jar}" />
<jar jarfile="${dist}/${client.jar}" >
<fileset dir="${build}" />
</jar>
</target>
<target name="package-dynamic" depends="prepare-dist"
description="Builds the JAR file that contains the dynamic proxy client">
<echo message="Building the client JAR file...."/>
<delete file="${dist}/${client.jar}" />
<jar jarfile="${dist}/${client.jar}" >
<fileset dir="${build}" includes="**/HelloClient.class" />
<fileset dir="${build}" includes="**/HelloIF.class" />
</jar>
</target>
<target name="build-service" depends="clean,compile-service,generate-sei-service,
setup-web-inf,package-service,process-war"
description="Executes the targets needed to build the service.">
</target>
<target name="build-static" depends="clean,generate-stubs,
compile-client,package-client"
description="Executes the targets needed to build a static stub client.">
</target>
<target name="build-dii" depends="clean,prepare,compile-client,package-client"
description="Executes the targets needed to build a DII client.">
</target>
<target name="build-dynamic" depends="clean,prepare,generate-interface,
compile-client,package-dynamic"
description="Executes the targets needed to build a dynamic proxy client.">
</target>
<target name="build-webclient" depends="clean,generate-stubs"
description="Executes the targets needed to build a web client.">
</target>
<target name="run-client"
description="Runs a stand-alone (non-J2EE) client">
<java classname="${client.class}" fork="yes" >
<arg line="${endpoint.address}" />
<classpath refid="run.classpath" />
</java>
</target>
<target name="run-secure-client"
description="Runs a client with basic authentication over SSL">
<java classname="${client.class}" fork="yes" >
<arg line="${username} ${password} ${endpoint.address}" />
<classpath refid="run.classpath" />
</java>
</target>
<target name="run-mutualauth-client"
description="Runs a client with mutual authentication over SSL">
<java classname="${client.class}" fork="yes" >
<arg line="${key.store} ${key.store.password}
${trust.store} ${trust.store.password}
${endpoint.address}" />
<classpath refid="run.classpath" />
</java>
</target>
<target name="clean"
description="Removes the build directory">
<delete dir="${build}" />
</target>
<target name="listprops" depends="set-wscompile"
description="Displays values of some of the properties of this
build file">
<echo message="jaxrpc.home = ${jaxrpc.home}" />
<echo message="wscompile = ${wscompile}" />
<echo message="build = ${build}" />
<echo message="src = ${src}" />
<echo message="dist = ${dist}" />
<echo message=" " />
<echo message="example = ${example}" />
<echo message="client.jar = ${client.jar}" />
<echo message="client.class = ${client.class}" />
<echo message=" " />
<echo message="host = ${host}" />
<echo message="port = ${port}" />
<echo message="secure.port = ${secure.port}" />
<echo message="trust.store = ${trust.store}" />
<echo message="trust.store.password = ${trust.store.password}" />
<echo message=" " />
<echo message="username = ${username}" />
<echo message="password = ${password}" />
<echo message="url = ${url}" />
<echo message=" " />
<echo message="context.path = ${context.path}" />
<echo message="secure.context.path = ${secure.context.path}" />
<echo message="url.pattern = ${url.pattern}" />
<echo message="endpoint.address = ${endpoint.address}" />
<echo message="secure.endpoint = ${secure.endpoint}" />
<echo message=" " />
<echo message="war.path = ${war.path}" />
<echo message="portable.war = ${portable.war}" />
<echo message="deployable.war = ${deployable.war}" />
</target>
==================================================================================
File: targets.xml ( C:\jwstutorial13\examples\common\targets.xml)
<taskdef name="list" classname="org.apache.catalina.ant.ListTask"/>
<taskdef name="install" classname="org.apache.catalina.ant.InstallTask"/>
<taskdef name="reload" classname="org.apache.catalina.ant.ReloadTask"/>
<taskdef name="remove" classname="org.apache.catalina.ant.RemoveTask"/>
<taskdef name="deploy" classname="org.apache.catalina.ant.DeployTask"/>
<taskdef name="undeploy" classname="org.apache.catalina.ant.UndeployTask"/>
<target name="list" description="List web applications" >
<list url="${url}" username="${username}" password="${password}" />
</target>
<target name="install" description="Install web application"
depends="build">
<install url="${url}" username="${username}" password="${password}"
path="/${context.path}" war="file:${build}"/>
</target>
<target name="reload" description="Reload web application"
depends="build">
<reload url="${url}" username="${username}" password="${password}"
path="/${context.path}"/>
</target>
<target name="remove" description="Remove web application">
<remove url="${url}" username="${username}" password="${password}"
path="/${context.path}"/>
</target>
<target name="package"
description="Packages the WAR file">
<echo message="Packaging the WAR...."/>
<delete file="dist/${war.file}" />
<jar jarfile="dist/${war.file}" >
<fileset dir="${build}" />
</jar>
</target>
<target name="deploy" description="Deploy a Web application">
<deploy url="${url}" username="${username}" password="${password}"
path="/${context.path}" war="file:/${example.path}/dist/${war.file}"
/>
</target>

<target name="undeploy" description="Undeploy web application">
<undeploy url="${url}" username="${username}" password="${password}"
path="/${context.path}"/>
</target>
==================================================================================
File: build.properties (C:\jwstutorial13\examples\common\build.properties)
tutorial.home=C:/jwstutorial13
tutorial.install=${tutorial.home}
username=******
password=********
host=localhost
port=8080
secure.port=8443
url=http://${host}:${port}/manager
==================================================================================
Finally, here is how I've got my PATH Environmental Variable Set:
PATH:
%JWSDP_HOME%\apache-ant\bin;%JWSDP_HOME%\jwsdp-shared\bin;%JWSDP_HOME%\bin;%JAVA_HOME%\bin;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\system32\WBEM;C:\Program Files\Microsoft SQL Server\80\Tools\Binn\
I set this up according to the instructions at the beginning of the tutorial.
JWSDP_HOME: C:\jwsdp-1.3
JAVA_HOME: C:\j2sdk1.4.1_05
Thanks again for your help.
Sheila

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 ?

Problem verify web services HelloWorld JAX-RPC

I have executed the tutorial Jax-RPC HelloWorld,
but when I verify the web service my browser display
A Web Service is installed at this URL.
This endpoint is incorrectly configured. Please check the location and contents of the configuration file.
which it is the problem?
you can help me?
thanks

Check if the endpoint property of the build.properties file
(ex. endpoint=...ttp://localhost:8080/SmsWSservice/SMS/SmsWSIF)
matches exactly (is case sensitive) the url pattern element content (ex. <servlet-mapping>
          <servlet-name>JAXRPCEndpoint</servlet-name>
          <url-pattern>/SMS/*</url-pattern>
     </servlet-mapping>) of the web.xml file.
In the examples above the url-pattern "SMS" must match the part of the URL between "...ttp://localhost:8080/SmsWSservice/" and the reference of the interface ("SmsWSIF).
Hope it helps

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

Deploy of jax-rpc sample hello fails on jwsdp-1.2 Why ?

Hi Friends,
I am installed Jwsdp-1.2 on my machine.I am trying to
deploy the hello sample which comes as part of jax-rpc.When i use the
ant tool to deploy the war file i get the following error.
C:\jwsdp-1.2\docs\tutorial\examples\jaxrpc\hello>ant deploy
Buildfile: build.xml
deploy:
BUILD FAILED
file:C:/jwsdp-1.2/docs/tutorial/examples/jaxrpc/common/targets.xml:14: java.io.IOException: Server returned HTTP response code: 401 for URL: http://localhost:8080/manager/deploy?path=%2Fhello-jaxrpc
Why am i getting this error while deploying to tomact engine.Also,even
if i try to access the url,
http://localhost:8080/manager/deploy?path=%2Fhello-jaxrpc
directly from the browser i get this error
FAIL - Unknown command /deploy
What should i do so as to deploy the sample jax-rpc hello program.Anyone
knows about this please reply soon.Any help regarding this will be greatly appreciated.

Error 401 means you're not authorised to view the page. Ant needs to know your username and password for Tomcat before it can access the deployment features.
Go to http://java.sun.com/webservices/docs/1.0/tutorial/doc/GettingStarted2.html and follow the guidelines in the section "Creating the Build Properties File"

JWSDP 2.0 JAX-RPC example problem Fast Infoset

Similar Messages

Maybe you are looking for