There are two different problems here: * lightweight components dependencies (quartz, rss, etc ...) * standard jbi components (eip, http, ...)
For jbi components, the problem is related to the deployment model used. If you use a standard JBI packaging, you need to install the component, then deploy the SU. Everything will work fine, as components are available in /components If you use a static deployment, where you configure the components inside the main servicemix.xml configuration file, these dependencies are not installed automatically. And I think they should not, as the whole classloader hierachy would be messed. So currently, you need to unzip the component installer and put the jars inside it in the /lib or /lib/optional folder. If you take a look at the ws-notification example, this step is done by the ant file. For lightweight components, the servicemix-components.jar is available in /components/lib. We do not ship all the libraries, for two reasons: * it would mess the classloader hierachy * there is such a big number of dependencies ... (20 Mo ?) Philip suggested a while back to ship two different versions of servicemix-lwcontainer, one without components / dependencies (like the current one) and another one with the full dependencies set. However, the same problem would happen for static xml configuration. I'd be glag to find solutions for these problems ... Thoughts ? On 10/5/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Hej! I just discovered that installing the binary distribution like described in the http://goopen.org/confluence/display/SM30UG/3.+Installation#3.Installation-WindowsBinaryInstallation User's Guide / installation presents errors even for the simplest configurations (at least with the default machine settings in our depatment => maybe something additional (classpath,...) has to be set up?). It's just missing packages, so nothing really bad, but not a nice out-of-the-box-experience -- first having to search for information (that was't available till some minutes ago) and to try around. Two files to demonstrate what I mean: http://www.nabble.com/file/292/Timer2Screen.xml Timer2Screen.xml is generated by CIMERO and connects a timer with a screen output. Does not run, a user has to install servicemix-components-3.0-incubating.jar and quartz-1.5.2.jar manually. http://www.nabble.com/file/293/Timer2WireTap2File_and_Screen.xml Timer2WireTap2File_and_Screen.xml adds a wire tap & a file writer to the above config. Requires to install servicemix-eip-3.0-incubating.jar manually. Though quartz is not any more in the examples, it is for sure piece of a lot of "try out configs", and EIP is certainly very common to use and it's use encouraged by us. Is there any way to include at least ServiceMix' sub-projects into the libs-dir / classpath, so it at least our own components simply work out of the box? Georg -- View this message in context: http://www.nabble.com/out-of-the-box-experience-very-limited-tf2389329.html#a6661175 Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
-- Cheers, Guillaume Nodet
