Hi,
To build WSIF, you unfortnately need j2ee.jar, since right now building WSIF involves building all the providers, including ones you may not need to use (such as the EJB or JCA providers).
To use WSIF you need at runtime the jars that are used by the providers you employ. The SOAP providers (WSIF has two - one uses Apache SOAP, the other apache Axis) require activation and mail jars. The EJB and JCA providers require j2ee.jar. So you don't need the entire j2ee.jar at runtime unless you plan on using the EJB or JCA providers.
There are plans to modularise WSIF so you build it independent of all providers, and handle building providers separately; then you can mix and match compiled pieces to create the installation you need. This might be done early next year, keep monitoring upcoming releases.
Nirmal.
| "Jeff Greif" <[EMAIL PROTECTED]>
12/18/2002 01:22 PM
|
To: <[EMAIL PROTECTED]> cc: Subject: [WSIF] -- doc confusion regarding j2ee.jar |
Two documents [1,2] on the wsif site refer to a dependency on j2ee.jar. #1 claims it is optional, if you have activation.jar and javamail.jar, and do not need EJB and JCA providers. #2 claims it is required and does not mention activation.jar and javamail.jar. Clearly, it would be required if you were expected to obtain these latter two apis from j2ee.jar, but is there more to it than that?
Is there work planned to fiddle with the wsif build targets so it will be possible to build a j2ee-independent version, under the assumptions mentioned in #1, and if so, is there a release target for such a build change?
Thanks much for any info on this topic.
Jeff
References:
1. http://cvs.apache.org/viewcvs.cgi/~checkout~/xml-axis-wsif/java/doc/build.htm ,
2. http://cvs.apache.org/viewcvs.cgi/~checkout~/xml-axis-wsif/java/doc/requirements.html
