Yeah. Unfortuanately the JBI spec does not support any reference to a shared library from a service unit, but this is a really needed feature and will hopefully be implemented in 3.2.
On 2/12/07, Rossmanith, Philipp <[EMAIL PROTECTED]> wrote:
Hi, The JBI Standard provides for shared libraries. Within SM, you can take a look at servicemix-shared-3.0-incubating-installer.zip (in v3.0) or http://incubator.apache.org/servicemix/working-with-shared-libraries.html. Hope that helps. Ciao, Philipp Rossmanith > -----Mensaje original----- > De: Jan Arend Jansen [mailto:[EMAIL PROTECTED] > Enviado el: sábado, 10 de febrero de 2007 16:53 > Para: [email protected] > Asunto: Sharing servicemix SE/BC dependencies > Importancia: Baja > > > Hi, > > I have a project that uses multiple service-engines and binding- > components. > These are build with maven2. The SU's are zipped and deployed to the > SEs/BCs. > > If I look inside the generated JAR files I can see that the lib > directories > have a lot of common libraries that originate from servicemix internal > dependencies. As a result each SU is about 10mb in size which is slow to > build and deploy. > > Is there a way to factor out these common libraries as a shared/common > package that is deployed only once? > > Thanks! > J.A. > -- > View this message in context: http://www.nabble.com/Sharing-servicemix-SE- > BC-dependencies-tf3205678s12049.html#a8901853 > Sent from the ServiceMix - User mailing list archive at Nabble.com. This e-mail may contain confidential or privileged information. Any unauthorised copying, use or distribution of this information is strictly prohibited.
-- Cheers, Guillaume Nodet ------------------------ Architect, LogicBlaze (http://www.logicblaze.com/) Blog: http://gnodet.blogspot.com/
