users@jax-rpc.java.net

RE: RE: Correctly shipping a web service client library

From: Kevin Jones <kevinj_at_develop.com>
Date: Tue, 12 Apr 2005 19:18:45 +0100

> Is that direction that we should all be taking when shipping
> a web-service right now?

That's the direction I would take. And the search in WEB-INF/lib is a spec
requirement so it should work,

Kevin Jones
http://kevinj.develop.com/weblog
 

> -----Original Message-----
> From: Ryan Champlin [mailto:ryan.champlin_at_firstlogic.com]
> Sent: 12 April 2005 19:13
> To: users_at_jax-rpc.dev.java.net
> Subject: RE: RE: Correctly shipping a web service client library
>
> Kevin,
>
> I'm assuming that it's probably safest not to rely on the
> server app our customers will be running to provide the
> correct JAX-RPC libraries and they should really be shipping
> in my applications WEB-INF/lib directory? That way they
> should work on all servers? (ideally anyway). Tomcat at
> least looks there before it looks in the servers common/lib
> or shared/lib directories. I'm not sure about Weblogic or Websphere.
>
>
> Thanks,
> Ryan
>
>
>
> -----Original Message-----
> From: Kevin Jones [mailto:kevinj_at_develop.com]
> Sent: Friday, April 08, 2005 2:45 AM
> To: users_at_jax-rpc.dev.java.net
> Subject: RE: Correctly shipping a web service client library
>
>
> Depends exactly what you're doing. I would guess that you
> need (all relative to %JWSDP_HOME%) the files from jaxrpc/lib
> and saaj/lib, you will probably need some (but not all) of
> the jwsdp-shared/lib, oh, and you may need jaxp/lib/endorsed.
> Sorry if this is a little vague but obviously your mileage
> will vary depending on the app you have,
>
>
> Kevin Jones
> http://public.xdi.org/=kevin.jones
> skype (www.skype.com): kevinrjones
>
>
>
>
> ________________________________
>
> From: Ryan Champlin [mailto:ryan.champlin_at_firstlogic.com]
> Sent: 07 April 2005 21:46
> To: users_at_jax-rpc.dev.java.net
> Subject: Correctly shipping a web service client library
>
>
>
>
> I'm building a web based application that is using a
> web service we developed for our application. Basically, for
> my web based application I am using JAX-RPC to generate my
> client stubs for my web service. If I deploy my web
> application with these stubs what else will need to ship with
> my web application? The web service will not be packaged
> with this particular web application. Can I just package up
> all the stubs in a jar file and then reference that from my
> web application and have everything work fine?
> Obviously all the JAX-RPC jars will need to exist on whatever
> webserver/servlet container the web app is being run on for
> this to work.
> Will J2EE 1.4 based servlet containers contain these JAR
> files already? I assume not as Tomcat doens't ship with them
> as of yet.
>
> If a customer were to try to deploy them on another
> server say a Weblogic would they have these JARs or should I
> always be shipping all of them along with my web app that has
> the JAX-RPC client stubs.
>
> Thanks,
> Ryan
>
>
>
> ---------------------------------------------------------------------
> 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
>
>