Yes, in the trunk's code, now we have built the "FULL WAR", which
included all the necessary jars in the $WAR/WEB-INF/lib.
If you want to try it against the 2.0.1 release, you need to change the
"common_build.xml" to do that.
Please refer to JIRA[1] for detail.
Thanks
Jeff
[1]https://issues.apache.org/jira/browse/CXF-901
Daniel Kulp wrote:
Just FYI, I think for 2.0.2, the default for the demos is changing to
building big wars that have all the required deps in the WEB-INF/lib.
That way, the wars should be app-server independent and you should be
able to use any version of tomcat, etc...
Dan
On Tuesday 28 August 2007, Christopher Moesel wrote:
Hi Rich,
I have not tried Tomcat 6, but I have successfully packaged all the
CXF jars in the WEB-INF/lib of my war in Tomcat 5.5. My shared/lib is
empty. I would suspect that you could do this with Tomcat 6.
So-- it's possible. I don't know if it's the recommended approach,
but it's an approach that has worked fine for me thus far.
-Chris
-----Original Message-----
From: Rich.Baldwin [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 28, 2007 1:49 PM
To: [email protected]
Subject: cxf deployment to tomcat
Looking through the cxf samples and the build.xml files, I noticed
that the target tomcat layout is 5.0 or 5.5. At tomcat 6.0, by
default the shared/lib goes away unless defined in properties files.
So my question
concerns classloader issues and servlet engine dependencies. Is the
recommended deployment for TC 6 to dump all cxf.home/lib jars into the
tomcat/lib directory or keep them in the project WEB-INF/lib or to
configure properties such that shared/lib and common/lib are used?
Are there jars in cxf.home/lib which MUST be deployed to tomcat/lib
for the cxf server stack to work? The tomcat folks have been
strongly hinting
for years that users avoid adding to tomcat/lib to avoid portability
issues, classloader issues, package conflict issues, etc.
Tx, Rich
