Return-Path: Delivered-To: apmail-incubator-cxf-dev-archive@locus.apache.org Received: (qmail 70089 invoked from network); 4 Aug 2007 21:45:54 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 4 Aug 2007 21:45:54 -0000 Received: (qmail 85264 invoked by uid 500); 4 Aug 2007 21:45:53 -0000 Delivered-To: apmail-incubator-cxf-dev-archive@incubator.apache.org Received: (qmail 85145 invoked by uid 500); 4 Aug 2007 21:45:52 -0000 Mailing-List: contact cxf-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cxf-dev@incubator.apache.org Delivered-To: mailing list cxf-dev@incubator.apache.org Received: (qmail 85110 invoked by uid 99); 4 Aug 2007 21:45:52 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 04 Aug 2007 14:45:52 -0700 X-ASF-Spam-Status: No, hits=2.6 required=10.0 tests=FM_FAKE_HELO_VERIZON,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of glen.mazza@verizon.net designates 206.46.252.40 as permitted sender) Received: from [206.46.252.40] (HELO vms040pub.verizon.net) (206.46.252.40) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 04 Aug 2007 21:45:30 +0000 Received: from [192.168.1.43] ([138.88.55.79]) by vms040.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPA id <0JM9009MHR3K9A0C@vms040.mailsrvcs.net> for cxf-dev@incubator.apache.org; Sat, 04 Aug 2007 16:45:21 -0500 (CDT) Date: Sat, 04 Aug 2007 17:45:21 -0400 From: Glen Mazza Subject: RE: How to deploy to JBoss? In-reply-to: To: cxf-dev@incubator.apache.org Message-id: <1186263921.13413.98.camel@gmazza-desktop> MIME-version: 1.0 X-Mailer: Evolution 2.10.1 Content-type: text/plain Content-transfer-encoding: 7bit References: X-Virus-Checked: Checked by ClamAV on apache.org Personally, I'm OK with Ant, at least for the code samples--I think it does a better job of showing both the "what" and the "how" involved in web service creation, helpful for newbies trying to understand the build and deployment process, and it is still better integrated than Maven right now in the various IDEs. What I'd like to see us reevaluate though is our continued use of embedded (Jetty) servlet containers. J2SE 6 has the endpoint interface now[1] that should make embedded containers unnecessary. But also I think that learning how to deploy/redeploy web service WAR files or EJB JAR files to an App Server is such a fundamental part of programming Java web services that we should be encouraging that as early on as possible. Once the user installs Tomcat, he/she could enter the Tomcat Catalina home directory in an Ant parent build.xml file and after that, the build.xml files in the sample directories would be able to provide the user build/WAR/deploy/redeploy targets for each of the samples. (Users may need to also store a Tomcat manager username/password though for redeploying.) Or, if they use something else besides Tomcat, they can still use our build.xml up to the "WAR" part, and then use their own deploy/undeploy tasks for their particular server. When I started out a couple of months back with CXF, I downloaded the samples, and dutifully ran "ant server" in one terminal window and "ant client" in the other, and it indeed worked--but I didn't really learn much from that. To me, it was a loss of time from what a newbie really needs to learn--namely, again, compiling this service into a WAR file, and then moving that WAR file onto Tomcat, and then getting the Ant deploy/redeploy cycle working well. Glen [1] https://jax-ws.dev.java.net/guide/Using_JAX_WS_2_1_with_JavaSE6.html Am Freitag, den 03.08.2007, 09:19 -0400 schrieb Christopher Moesel: > Hey Dev Team, > > Just wondering-- has any thought been given to having the examples use > maven rather than ANT? I suspect that a conscious decision has been > made NOT to use Maven for the examples-- because the examples are the > only part of the project that doesn't use Maven. > > I'm just thinking that using Maven could possibly make this a lot easier > for users to try-- it could build a war, it could use the jetty or cargo > plugin to run an embedded web server, or it could use the exec plugin to > run standalone examples with the classpath automatically set up for you. > But... it also requires the user to know Maven. =/ > > Anyway, just wondering if this topic has already been run to the ground. > > -Chris > > -----Original Message----- > From: Ray Krueger [mailto:raykrueger@gmail.com] > Sent: Friday, August 03, 2007 9:09 AM > To: cxf-user@incubator.apache.org > Subject: Re: How to deploy to JBoss? > > The CXF crew should look at making the samples deploy in a more > standard fashion. > > Currently the deployment requires man-handling all of the cxf jars > into Tomcat's classpath, rather than packaging them into a WAR. > > Building a WAR would give us the ability to try out the samples in our > container of choice; or the companys container of choice as the case > may be. > > > On 8/3/07, Christopher Moesel wrote: > > You should be able to drop all those same jars into the WEB-INF/lib of > > your web application-- then you wouldn't need to copy them into the > > Jboss server lib. > > > > -Chris > > > > -----Original Message----- > > From: Erlend Leganger [mailto:eleganger@gmail.com] > > Sent: Friday, August 03, 2007 8:32 AM > > To: cxf-user@incubator.apache.org > > Subject: Re: How to deploy to JBoss? > > > > You were right, it wasn't copied. I tried to copy it from > > cxf-2.0-incubator/lib > > into jboss-4.0.4.GA/default/server/lib, restarted - then jboss was > > missing > > some other spring stuff. Copied all spring*.jar from cxf into jboss, > > restarted, then some other stuff was missing. Finally copied all files > > from > > cxf/lib into default/server/lib, restarted jboss and then it worked! - > > thanks a lot! > > > > Is this this the proper way to do it? I felt like I was polluting the > > jboss > > installation with all this cxf stuff... > > > > Regards, > > Erlend Leganger > > > > On 03/08/07, Velidanda Srinivas > > wrote: > > > > > > Check for spring-beans-2.0.4.jar, copied or not? > > > > > > > -----Original Message----- > > > > From: Erlend Leganger [mailto:eleganger@gmail.com] > > > > Sent: 03 August 2007 13:23 > > > > To: cxf-user@incubator.apache.org > > > > Subject: Re: How to deploy to JBoss? > > > > > > > > > > > > I tried the following: > > > > - copied all files from cxf's modules directory into jboss' > > > > server/default/deploy/lib > > > > - restarted jboss > > > > - dropped helloworld.war into jboss' server/default/deploy > > > > > > > > This made a difference, but it still doesn't work, here's the > > > > jboss log: > > > > > > > > 09:41:05,987 INFO [TomcatDeployer] deploy, ctxPath=/helloworld, > > > > warUrl=.../tmp/deploy/tmp58299helloworld-exp.war/ > > > > 09:41:06,190 INFO [[/helloworld]] Marking servlet cxf as > > unavailable > > > > 09:41:06,190 ERROR [[/helloworld]] Servlet /helloworld threw > load() > > > > exception java.lang.NoClassDefFoundError: > > > > org/springframework/beans/factory/support/BeanDefinitionRegistry > > > > > > > > When trying ant client-servlet, jboss refuses to respond to > > > > the client, it > > > > logs: > > > > 09:50:05,909 INFO [[cxf]] Servlet cxf is currently unavailable > > > > 09:50:05,924 INFO [[cxf]] Servlet cxf is currently unavailable > > > > 09:50:05,924 INFO [[cxf]] Servlet cxf is currently unavailable > > > > > > > > What is missing now and how do I fix it? > > > > > > > > Regards, > > > > Erlend Leganger > > > > > > > > > > > > On 03/08/07, Velidanda Srinivas > > > > > > wrote: > > > > > > > > > > I think you need to drop the jar file containing > > > > > org.apache.cxf.transport.servlet.CXFServlet class > > > > > into jboss\default\server\lib folder OR add this jar to > > > > web-inf\lib folder > > > > > of the war being deployed. > > > > > > > > > > Srinivas. > > > > > > > > > > > -----Original Message----- > > > > > > From: Erlend Leganger [mailto:eleganger@gmail.com] > > > > > > Sent: 03 August 2007 12:40 > > > > > > To: cxf-user@incubator.apache.org > > > > > > Subject: How to deploy to JBoss? > > > > > > > > > > > > > > > > > > I have been going through the CXF samples; those I have tried > > > > > > work fine, > > > > > > both in standalone mode and with the server part deployed > > > > to Tomcat. > > > > > > > > > > > > What do I need to do if I want to deploy to JBoss instead of > > > > > > Tomcat? I tried > > > > > > to simply drop helloworld.war into the C:\opt\jboss\jboss- > > > > > > 4.0.4.GA\server\default\deploy directory, this gave a > > > > class not found > > > > > > exception: > > > > > > > > > > > > 09:00:31,501 ERROR [MainDeployer] Could not create deployment: > > > > > > > > > > > > file:/C:/opt/jboss/jboss-4.0.4.GA/server/default/deploy/helloworld.war > > > > > > org.jboss.ws.WSException: java.lang.ClassNotFoundException: > > > > > > org.apache.cxf.transport.servlet.CXFServlet > > > > > > at > > > > > > > > org.jboss.ws.server.WebServiceDeployerJSE.isWebserviceDeployment( > > > > > > WebServiceDeployerJSE.java:161) > > > > > > ... > > > > > > > > > > > > Regards, > > > > > > Erlend Leganger > > > > > > > > > > > > My environment: > > > > > > rem set JAVA_HOME=c:\opt\java\jdk1.6.0_02 > > > > > > set JAVA_HOME=c:\opt\java\jdk1.5.0_12 > > > > > > set AXIS2_HOME=c:\opt\axis2\axis2-1.3-RC2 > > > > > > set ANT_HOME=c:\opt\ant\apache-ant-1.7.0 > > > > > > set CATALINA_HOME=c:\opt\tomcat\apache-tomcat-5.5.23 > > > > > > set JBOSS_HOME=c:\opt\jboss\jboss-4.0.4.GA > > > > > > set CFX_HOME=c:\opt\cxf\apache-cxf-2.0-incubator > > > > > > set PATH=C:\WINDOWS > > > > > > set PATH=%PATH%;C:\WINDOWS\system32 > > > > > > set PATH=%PATH%;C:\WINDOWS\System32\Wbem > > > > > > set PATH=%PATH%;%JAVA_HOME%\bin > > > > > > set PATH=%PATH%;%CATALINA_HOME%\bin > > > > > > set PATH=%PATH%;%JBOSS_HOME%\bin > > > > > > set PATH=%PATH%;%ANT_HOME%\bin > > > > > > set > > > > > > > > > > > > CLASSPATH=.;%CFX_HOME%\lib\cxf-manifest-incubator.jar;.\build\classes > > > > > > > > > > > > > > > > > > ______________________________________________________________ > > > > > > __________ > > > > > > This e-mail has been scanned for all viruses by MessageLabs. > > > > > > ______________________________________________________________ > > > > > > __________ > > > > > > > > > > > > > > > > > > > > ______________________________________________________________ > > > > __________ > > > > > This e-mail has been scanned for all viruses by MessageLabs. > > > > > > > > > > To learn more about Singularity's business process > > > > management solutions > > > > > and services please visit: > > > > > www.singularity.co.uk > > > > > www.singularity.us.com > > > > > Singularity operates globally through its offices in New > > > > York, London, > > > > > Singapore, Ireland and India. Singularity Limited is > > > > incorporated in the > > > > > United Kingdom with Registration Number NI 31519 and its > > > > Registered Office > > > > > at 100 Patrick Street, Derry, BT48 7EL, United Kingdom. > > > > > > > > > > > > > > > > > ______________________________________________________________ > > > > __________ > > > > This e-mail has been scanned for all viruses by MessageLabs. > > > > ______________________________________________________________ > > > > __________ > > > > > > > > > > > > > ________________________________________________________________________ > > > This e-mail has been scanned for all viruses by MessageLabs. > > > > > > To learn more about Singularity's business process management > > solutions > > > and services please visit: > > > www.singularity.co.uk > > > www.singularity.us.com > > > Singularity operates globally through its offices in New York, > London, > > > Singapore, Ireland and India. Singularity Limited is incorporated in > > the > > > United Kingdom with Registration Number NI 31519 and its Registered > > Office > > > at 100 Patrick Street, Derry, BT48 7EL, United Kingdom. > > > > >