On 30 Mar 2008, at 19:25, Michael Santy wrote:
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)?
Yes eventually we'd like to move to Equinox (probably).
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?
No, but there are several places in this file that could hide these
logs. For instance you may still have:
<category name="org.jboss">
<priority value="WARN"/>
</category>
Florent
--
Florent Guillaume, Director of R&D, Nuxeo
Open Source Enterprise Content Management (ECM)
http://www.nuxeo.com http://www.nuxeo.org +33 1 40 33 79 87
_______________________________________________
ECM mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm
