Ok, packaging the JAXRPC .jars to the .war is the solution to prefer,
agree.
What makes me a bit thoughtful is nevertheless the thing, that WebSphere
can work with the raw .war (Sun App Server too). These two app servers
create all the necessary stuff (cook the raw .war) obviously under the
hood. How is this behaviour called? Is this what makes an app server
"JAXRPC compliant"???
So, when I want to deliver my .war to a customer, what should I deliver,
general raw one or implementation specific cooked one?
Maybe this is the solution: provide two .war files. One for
JAXRPC-compliant servlet containers (raw .war), one for servlet
containers, which do not support JAXRPC "immediately" but can work with
the cooked .war.
cu
Merten
> -----Original Message-----
> From: Kevin Jones [mailto:kevinj_at_develop.com]
> Sent: Wednesday, August 04, 2004 1:25 PM
> To: users_at_jax-rpc.dev.java.net
> Subject: RE: Is Apache Axis required to deploy JAX-RPC application?.
>
> What I do is build the raw WAR file and make sure it contains
> the jar files
> from the JAXRPC etc libs in the WEB-INF/lib. I don't want to pollute
> Tomcat's common directory with files that may affect other
> apps. I then cook
> the war and deploy it to TC.
>
> My note about Xerces is because JWSDP 1.4 relies on Sun's
> version of Xerces
> and simply including those JARS (xercesimpl etc) in the
> WEB-INF/lib won't
> work, you have to replace the Endorsed JARs in TC,
>
> Kevin Jones
> http://kevinj.develop.com
>
>
> > -----Original Message-----
> > From: Merten Schumann [mailto:Merten.Schumann_at_asg.com]
> > Sent: 04 August 2004 09:12
> > To: users_at_jax-rpc.dev.java.net
> > Subject: Re: Is Apache Axis required to deploy JAX-RPC application?.
> >
> > Hello Bobby,
> >
> > it worked! :-)
> >
> > Just to mention, maybe it's of interest: I had to copy these
> > .jar's (out of Sun J2EE 1.4 RI) following the missing class
> > exceptions from Tomcat
> > jaxrpc-impl.jar, jaxrpc-api.jar
> > jax-qname.jar (javax/xml/namespace/Qname)
> > j2ee.jar (javax/xml/soap/SOAPException)
> > saaj-impl.jar
> > (com/sun/xml/messaging/saaj/soap/SOAPVersionMismatchException)
> >
> > When I deploy my .war for example to WebSphere, I can take
> > the RAW version. WebSphere seems to evaluate the
> > jaxrpc-ri.xml file itself and does create all this tie stuff
> > and all. So, I guess the current Tomcat version is not
> > "JAXRPC ready" per default. You have to assemble an JAXRPC
> > implementation specific .war (for example, with Sun J2EE's
> > libs and wsdeploy tool) and provide the implementation
> > specific .jars to Tomcat. At least, even with the JAXRPC jars
> > in common/libs, when I copy my raw .war to Tomcat webapps,
> > nothing (besides from extracting the
> > .war) happens.
> >
> > Bobby, thank you for the response!
> > Merten
> >
> > > -----Original Message-----
> > > From: Bobby Bissett [mailto:Robert.Bissett_at_Sun.COM]
> > > Sent: Tuesday, August 03, 2004 6:14 PM
> > > To: users_at_jax-rpc.dev.java.net
> > > Subject: Re: Is Apache Axis required to deploy JAX-RPC
> application?.
> > >
> > >
> > > > Hm, I thought the cooked .war is Sun specific, since
> > > wsdeploy generates
> > > > dependencies to Sun classes.
> > >
> > > Like other war files, it should work in any serlvet-compliant web
> > > server as long as the needed classes are in the classpath
> > of the web
> > > server (or are in the war file). I have used a standalone tomcat
> > > server (the servlet container RI) in the past and simply
> copied the
> > > jaxrpc jars into the common/lib dir and it has worked fine.
> > >
> > > > java.lang.ClassNotFoundException:
> > > > com.sun.xml.rpc.server.http.JAXRPCContextListener
> > >
> > > Are the jar files definitely in the classpath? If you
> > installed jwsdp
> > > over the suggested tomcat container, this should happen
> > automatically.
> > > Otherwise, try copying the jwsdp jars into the server's
> common lib
> > > directory. The file you're missing is in the jaxrpc-impl.jar file.
> > >
> > > Cheers,
> > > Bobby
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe_at_jax-rpc.dev.java.net
> > For additional commands, e-mail: users-help_at_jax-rpc.dev.java.net
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jax-rpc.dev.java.net
> For additional commands, e-mail: users-help_at_jax-rpc.dev.java.net
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_jax-rpc.dev.java.net
For additional commands, e-mail: users-help_at_jax-rpc.dev.java.net