Ok, so now things are starting to make sense. Apparently there is a big difference between the servicemix-web that you build from the examples directory from a servicemix distribution and actually downloading the servicemix-web war from the website. The one on the website is missing a ton of jars that are needed for it to run properly (it doesn't include activemq, the pooling classes, or quartz). It also doesn't enable activemq or enable polling a deploy directory. Knowing this difference would have saved me a lot of headaches. I figured getting the one off the website would be the same as the one built from the examples (or at least the same without the examples actually in it). Anyhow, I still have a few problems, but they are classloader/tomcat related and not servicemix related. So I guess all I needed was to just build the examples war and use that to deploy my stuff..
On Fri, Jan 9, 2009 at 9:21 PM, Ryan Moquin <[email protected]> wrote: > I started looking at the WAR version of servicemix again and was curious > about how the classloading for SA/SUs differs from the standalone version. > The reason I'm asking is because I have a CXF SU that uses a quartz timer > internally and therefore includes a quartz jar along with the quartz > configuration for the SU. When I deploy the SU to the servicemix war, it > tells me it can't find the Quartz classes, but if I deploy the SU to the > standalone servicemix, then my SU loads up and operates perfectly fine. > Quartz isn't in a global classpath that I can see for the standalone > Servicemix, so I guess I'm a little confused on how dependencies and class > loading works when using the WAR. Is there something different you have to > do in order to get it find classes? I figured anything that worked when > deployed in the standalone servicemix should work fine when deployed in the > WAR version. Any suggestions would be great, thanks! > > Ryan >
