Well put, Dan. Thanks for the very detailed response. I can see that this has, indeed, received a lot of thought.
I don't know how good it is, but you may want to check out this ANT plugin for generating Eclipse project files. It's under the Apache v2 license, so if it's any good, it should be distributable with CXF. http://ant-eclipse.sourceforge.net/ -Chris -----Original Message----- From: Daniel Kulp [mailto:[EMAIL PROTECTED] Sent: Monday, August 06, 2007 11:20 AM To: [email protected] Cc: Christopher Moesel Subject: Re: How to deploy to JBoss? On Friday 03 August 2007 09:19, Christopher Moesel wrote: > 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. This is something I've been tossing around for ages, I just haven't had time to figure out completely how to get it to work "well". Every time I need to bring a sample up in eclipse to show someone something, the fact that I cannot just do "mvn eclipse:eclipse" drives me nuts. Getting the samples into eclipse currently sucks. There are a couple of issues: 1) "offline mode" or "using the jars in the kits" issues: Maven will go off the repository and download stuff just fine. However, if you're offline, the samples won't work very well unless you built them online first. The latest version of the assembly plugin does have the ability to create a "repository" directory which the samples could point to. I just haven't had time to look into what would be involved in that. Also, that would increase the download size a bit (the jars in /lib as well as /repository). 2) Launching clients and servers - the servers would be easy via something like "mvn jetty:run" or something. Clients to hit those are a bit more involved. Ant is nice in that you can just do "ant server" and "ant client". With maven, the best we could do is "mvn -Pserver" and "mvn -Pclient". 3) There's also a couple of "release" related issues, which as the defacto release manager, I need to keep in mind. #1 is that currently, we just suck in the samples directory as-is. If we go maven, I'd need to update things to filter in a version number into all the poms. Unfortunately, that is NOT easy. (actually, may not even be possible right now, you cannot filter poms very well.) The alternative is to actually wire all the samples into the -Peverything build so they would get "released" with "mvn release:prepare" and deployed to the repositories and stuff. I'm not sure we want to put all the samples into the maven repository. 4) Depending on the fix for (1), there is the "testing kits for votes" issues. If there isn't a "repository" in the kit itself, testing the samples as part of validating the kits before a release will be "hard". The jars only go to the repository if/when the vote passes. Thus, the samples would not be able to download the jars without updating the poms to find the staging area. Anyway, I do think about this periodically. It's just a bit more complicated than "change to maven". It requires a bit more thought than just that. My personal motivation is to make it easier to get the demos into eclipse. Dan > 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:[EMAIL PROTECTED] > Sent: Friday, August 03, 2007 9:09 AM > To: [EMAIL PROTECTED] > 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 <[EMAIL PROTECTED]> 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:[EMAIL PROTECTED] > > Sent: Friday, August 03, 2007 8:32 AM > > To: [EMAIL PROTECTED] > > 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 > > <[EMAIL PROTECTED]> > > > > wrote: > > > Check for spring-beans-2.0.4.jar, copied or not? > > > > > > > -----Original Message----- > > > > From: Erlend Leganger [mailto:[EMAIL PROTECTED] > > > > Sent: 03 August 2007 13:23 > > > > To: [EMAIL PROTECTED] > > > > 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 > > > > <[EMAIL PROTECTED]> > > > > > > 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:[EMAIL PROTECTED] > > > > > > Sent: 03 August 2007 12:40 > > > > > > To: [EMAIL PROTECTED] > > > > > > 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.w > >ar > > > > > > > > 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\classe > >s > > > > > > > > ____________________________________________________________ > > > > > >__ __________ > > > > > > 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. -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727 C: 508-380-7194 [EMAIL PROTECTED] http://www.dankulp.com/blog
