Thanks
for the information.
I'll
be using the SOAP and EJB providers for sure, and maybe the java
one.
I was
more concerned about the size of axis itself. But I finally found
out
(I
mistakenly added wsif to my search in the mailing list :( ) that I'll have
to
do it
manually too (see http://marc.theaimsgroup.com/?l=axis-user&m=103479872822656&w=2 )
Thanks
Jacques-Olivier
-----Original Message-----
From: Nirmal Mukhi [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 09, 2003 1:16 PM
To: [EMAIL PROTECTED]
Subject: Re: [wsif] axis client jar ?
Hello Jacques,
At some point we plan to make WSIF modular so that you can make a WSIF distribution containing only the providers you use; this would make the build environment and the runtime environment much easier.
For now you will need to build the core WSIF classes (everything outside of the org/apache/wsif/providers) and the Axis provider, plus whatever depencies the Axis provider has on other providers (hopefully those will be very few). Unfortunately you will have to do this manually as things stand right now.
Out of curiosity: if you have determined that all you will be doing is accessing SOAP services, why aren't you using Axis and the JAX-RPC API directly instead of WSIF?
Nirmal.
"Jacques-Olivier Goussard" <[EMAIL PROTECTED]> 01/09/2003 01:03 PM
Please respond to axis-user
To: <[EMAIL PROTECTED]>
cc:
Subject: [wsif] axis client jar ?
Hi
Is there a way to build an AXIS client-only jar ?
I'm using WSIF and would be interested in packaging
only the needed client classes of AXIS instead of
the whole stuff.
Anybody tried that before ?
Thanks
Jacques-Olivier
