On Fri, May 9, 2008 at 5:12 PM, Ryan Moquin <[EMAIL PROTECTED]> wrote: > Ok, no prob. I didn't want to just go start dropping jars in, unless I knew > it was necessary. I'll go ahead and try to do that today, since it would be > hugely beneficial for us to be able to use the WAR and I'll send you a list > of what I needed to do to satisfy the dependencies.
Great > > A quick question on 3.2.2, will it the cxf rest support at all? Or is that > planned for another release? CXF 2.1 will be integrated in ServiceMix 3.3 > > Thanks for all the great work your team does with Servicemix. > > Ryan > > On Fri, May 9, 2008 at 9:27 AM, Guillaume Nodet <[EMAIL PROTECTED]> wrote: > >> I think it's because not all libraries are included in the war >> distribution. >> You should try to drop the jms spec jar from servicemix standalone in the >> lib >> folder of the webapp and restart it. If you can come with a list of >> missing jars, >> we could include them for 3.2.2 (I plan to release it early today or >> early next week). >> >> On Fri, May 9, 2008 at 2:47 PM, Ryan Moquin <[EMAIL PROTECTED]> >> wrote: >> > I'm using 3.2.1, anxiously awaiting 3.2.2 (hint hint) :). Anyhow, I'm >> > hoping I'm not doing something dumb, but my assumption is that if the >> > standalone works out of the box, then I wouldn't think I would need to do >> > anything special for the WAR version, but if I do, I want to make sure I >> > know what. >> > >> > I could try deploying through the UI rather than dropping the files into >> the >> > install directory. Though I figured it would be easier to drop all the >> base >> > SE installers into the install directory, rather than go through and >> select >> > each one. This error happens when I deploy the servicemix SE components >> > that come with the standalone. Maybe I'm just not understanding the >> > differences in how the WAR should work compared to the standalone.When >> you >> > use the WAR file, are you supposed to deploy the installers that you >> want, >> > such as the CXF, HTTP, EIP, and so on? Or are you supposed to just go >> ahead >> > and deploy your JBI components right off the bat? >> > >> > On Thu, May 8, 2008 at 10:58 PM, Freeman Fang <[EMAIL PROTECTED]> >> > wrote: >> > >> >> Hi Ryan, >> >> >> >> What's the servicemix version you are using? >> >> >> >> I just test the servicemix 3.2.2 snapshot web distribution, it's ok for >> me. >> >> I'm using jetty as servlet container, and there is a web-gui for you to >> >> install/start component and deploy SA. >> >> [1] for more details how it works >> >> >> >> [1] >> >> >> http://svn.apache.org/repos/asf/servicemix/smx3/branches/servicemix-3.2/distributions/apache-servicemix-web/README.txt >> >> Freeman >> >> >> >> >> >> >> >> Ryan Moquin wrote: >> >> >> >>> I'm trying to understand how to use the servicemix WAR distribution. >> I've >> >>> been using the standalone for a while and it's been working well. I'm >> >>> hoping to use the WAR version so that I can make it easier to >> consolidate >> >>> different applications for demo purposes. I'm not exactly sure how to >> get >> >>> started with the WAR file. I mean I know that it should be deployed in >> >>> tomcat and all that, but I always run into trouble when trying to >> deploy >> >>> components into it. All I did was take the installer component files >> from >> >>> the standalone distribution and drop them into the "install" directory >> >>> under >> >>> the data directory created by the WAR. When I do this, it attempts to >> >>> deploy the components but I get the following error. Is there a set of >> >>> steps needed to successfully use the WAR distribution? It seems like >> it's >> >>> missing some dependencies, but I'm not sure where they would do. Is the >> >>> WAR >> >>> distribution suitable for use instead of the standalone? Thanks for >> any >> >>> help!! >> >>> >> >>> java.lang.NoClassDefFoundError: javax/jms/MessageListener >> >>> at java.lang.ClassLoader.defineClass1(Native Method) >> >>> at java.lang.ClassLoader.defineClass(ClassLoader.java:620) >> >>> at >> >>> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124) >> >>> at >> >>> >> >>> >> org.apache.xbean.classloader.JarFileClassLoader.access$200(JarFileClassLoader.java: >> >>> 48) >> >>> at >> >>> >> >>> >> org.apache.xbean.classloader.JarFileClassLoader$6.run(JarFileClassLoader.java:272) >> >>> at java.security.AccessController.doPrivileged(Native Method) >> >>> at >> >>> >> >>> >> org.apache.xbean.classloader.JarFileClassLoader.findClass(JarFileClassLoader.java:2 >> >>> 24) >> >>> at >> >>> >> >>> >> org.apache.xbean.classloader.MultiParentClassLoader.loadClass(MultiParentClassLoade >> >>> r.java:200) >> >>> at java.lang.ClassLoader.loadClass(ClassLoader.java:251) >> >>> at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) >> >>> at >> >>> >> >>> >> org.apache.servicemix.wsn.component.WSNLifeCycle.doInit(WSNLifeCycle.java:63) >> >>> at >> >>> >> >>> >> org.apache.servicemix.common.AsyncBaseLifeCycle.init(AsyncBaseLifeCycle.java:187) >> >>> at >> >>> >> >>> >> org.apache.servicemix.jbi.framework.ComponentMBeanImpl.init(ComponentMBeanImpl.java >> >>> :201) >> >>> at >> >>> >> >>> >> org.apache.servicemix.jbi.framework.ComponentMBeanImpl.doStart(ComponentMBeanImpl.j >> >>> ava:287) >> >>> at >> >>> >> >>> >> org.apache.servicemix.jbi.framework.ComponentMBeanImpl.start(ComponentMBeanImpl.jav >> >>> a:216) >> >>> at >> >>> >> >>> >> org.apache.servicemix.jbi.framework.InstallationService.install(InstallationService >> >>> .java:334) >> >>> at >> >>> >> >>> >> org.apache.servicemix.jbi.framework.AutoDeploymentService.updateComponent(AutoDeplo >> >>> ymentService.java:289) >> >>> at >> >>> >> >>> >> org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchive(AutoDeploym >> >>> entService.java:249) >> >>> at >> >>> >> >>> >> org.apache.servicemix.jbi.framework.AutoDeploymentService.monitorDirectory(AutoDepl >> >>> oymentService.java:647) >> >>> at >> >>> >> >>> >> org.apache.servicemix.jbi.framework.AutoDeploymentService.access$800(AutoDeployment >> >>> Service.java:60) >> >>> at >> >>> >> >>> >> org.apache.servicemix.jbi.framework.AutoDeploymentService$1.run(AutoDeploymentServi >> >>> ce.java:611) >> >>> at java.util.TimerThread.mainLoop(Timer.java:512) >> >>> at java.util.TimerThread.run(Timer.java:462) >> >>> Exception in thread "Timer-1" java.lang.NoClassDefFoundError: >> >>> javax/jms/MessageListener >> >>> at java.lang.ClassLoader.defineClass1(Native Method) >> >>> at java.lang.ClassLoader.defineClass(ClassLoader.java:620) >> >>> at >> >>> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124) >> >>> at >> >>> >> >>> >> org.apache.xbean.classloader.JarFileClassLoader.access$200(JarFileClassLoader.java: >> >>> 48) >> >>> at >> >>> >> >>> >> org.apache.xbean.classloader.JarFileClassLoader$6.run(JarFileClassLoader.java:272) >> >>> at java.security.AccessController.doPrivileged(Native Method) >> >>> at >> >>> >> >>> >> org.apache.xbean.classloader.JarFileClassLoader.findClass(JarFileClassLoader.java:2 >> >>> 24) >> >>> at >> >>> >> >>> >> org.apache.xbean.classloader.MultiParentClassLoader.loadClass(MultiParentClassLoade >> >>> r.java:200) >> >>> at java.lang.ClassLoader.loadClass(ClassLoader.java:251) >> >>> at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) >> >>> at >> >>> >> >>> >> org.apache.servicemix.wsn.component.WSNLifeCycle.doInit(WSNLifeCycle.java:63) >> >>> at >> >>> >> >>> >> org.apache.servicemix.common.AsyncBaseLifeCycle.init(AsyncBaseLifeCycle.java:187) >> >>> at >> >>> >> >>> >> org.apache.servicemix.jbi.framework.ComponentMBeanImpl.init(ComponentMBeanImpl.java >> >>> :201) >> >>> at >> >>> >> >>> >> org.apache.servicemix.jbi.framework.ComponentMBeanImpl.doStart(ComponentMBeanImpl.j >> >>> ava:287) >> >>> at >> >>> >> >>> >> org.apache.servicemix.jbi.framework.ComponentMBeanImpl.start(ComponentMBeanImpl.jav >> >>> a:216) >> >>> at >> >>> >> >>> >> org.apache.servicemix.jbi.framework.InstallationService.install(InstallationService >> >>> .java:334) >> >>> at >> >>> >> >>> >> org.apache.servicemix.jbi.framework.AutoDeploymentService.updateComponent(AutoDeplo >> >>> ymentService.java:289) >> >>> at >> >>> >> >>> >> org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchive(AutoDeploym >> >>> entService.java:249) >> >>> at >> >>> >> >>> >> org.apache.servicemix.jbi.framework.AutoDeploymentService.monitorDirectory(AutoDepl >> >>> oymentService.java:647) >> >>> at >> >>> >> >>> >> org.apache.servicemix.jbi.framework.AutoDeploymentService.access$800(AutoDeployment >> >>> Service.java:60) >> >>> at >> >>> >> >>> >> org.apache.servicemix.jbi.framework.AutoDeploymentService$1.run(AutoDeploymentServi >> >>> ce.java:611) >> >>> at java.util.TimerThread.mainLoop(Timer.java:512) >> >>> at java.util.TimerThread.run(Timer.java:462) >> >>> >> >>> >> >>> >> >> >> >> >> > >> >> >> >> -- >> Cheers, >> Guillaume Nodet >> ------------------------ >> Blog: http://gnodet.blogspot.com/ >> > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/
