Starting in the upcoming 2.0.2 version, I believe the samples will now place the jars in the WAR file by default. We had a recent commit to that to the Subversion repository trunk.
Glen Am Dienstag, den 28.08.2007, 13:56 -0400 schrieb Rich.Baldwin: > Excellent! > > Christopher Moesel said the following on 8/28/2007 1:54 PM: > > 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 > >
