Florent,
> OSGi is the spec we use to specify deployment dependencies, but the
> actual deployment, in the current version of Nuxeo, is still done by
> JBoss, and does not follow OSGi classloader rules.
Thanks for the clarification. The error that I was seeing now makes a whole
lot of sense. I can also see how the bundle isolation provided by OSGi
would be very useful to plugin developers. Are there any concrete plans to
move Nuxeo to an OSGi runtime on the server (e.g., JoNAS 5, Server-Side
Equinox)?
>
> If you peek at the server/defaut/log/server.log, you'll see something
> like:
>
> DEBUG [org.jboss.deployment.JARDeployer] looking for nested
> deployments in : file:/opt/jboss/server/default/deploy/nuxeo.ear/
> platform/nuxeo-platform-workflow-jbpm-5.1.4-SNAPSHOT.jar
> [...]
> DEBUG [org.jboss.deployment.JARDeployer] nested deployment: file:/opt/
> jboss/server/default/tmp/deploy/tmp44861nuxeo-platform-workflow-
> jbpm-5.1.4-SNAPSHOT.jar-contents/jbpm-3.1.4.jar
> DEBUG [org.jboss.deployment.JARDeployer] nested deployment: file:/opt/
> jboss/server/default/tmp/deploy/tmp44861nuxeo-platform-workflow-
> jbpm-5.1.4-SNAPSHOT.jar-contents/jbpm-identity-3.1.4.jar
> DEBUG [org.jboss.deployment.JARDeployer] nested deployment: file:/opt/
> jboss/server/default/tmp/deploy/tmp44861nuxeo-platform-workflow-
> jbpm-5.1.4-SNAPSHOT.jar-contents/saxon.jar
I didn't actually see this message, even after adjusting the log level to
DEBUG in ${jboss.home}/server/default/conf/log4j.xml. Is there somewhere
else that I should adjust the log setting?
>
> So JBoss automatically deploys embedded jars.
>
> From a quick look at the code there are two ways to have embedded
> files not be deployed by JBoss:
> 1. put them in META-INF
> 2. don't give them a recognized suffix (.jar, .sar, .ear, etc.)
>
That did the trick. Thanks for the insight and keep up the good work!
Cheers,
Mike
_______________________________________________
ECM mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm
