|
|
|
| The following comment has been added to this issue: |
[ Permlink ] |
|
Author: Jean-Marc Orliaguet
Date: 17/03/07 20:08
Comment:
the branch can be tested at:
https://svn.nuxeo.org/nuxeo/nuxeo-ep/branches/isolated-cl
here is a summary:
- nuxeo5 starts and works as usual
- the theme editor starts correctly but crashes (this is not due to the migration), but to recent changes in the trunk concerning REST URLs (the fancyURL servlet I believe). So I can't test Seam yet, although it should be easy to fix remaining issues
javax.faces.el.EvaluationException: Exception while invoking _expression_ #{restHelper.initContextFromRestRequest}
at org.apache.myfaces.el.MethodBindingImpl.invoke(MethodBindingImpl.java:156)
at org.jboss.seam.actionparam.ActionParamBindingHelper.invokeTheExpression(ActionParamBindingHelper.java:59)
there are a couple of related issues that must be solved before a merge into the trunk:
- REST URLs crash the editor (see above), I haven't investigated why yet. This can already be fixed in nuxeo-ep trunk.
- JBoss Seam is used both by nxthemes-jsf-editor and nuxeo webapp, it should be moved to a common location.
- org.nuxeo.runtime.jboss-extensions/resources/ear-template/OSGI-INF/templates contains references to UI modules, which creates a dependency on org.nuxeo.ecm.platform.ui.web, org.nuxeo.ecm.webapp in nxruntime:
faces-config.xml: org.nuxeo.ecm.platform.ui.web.resolver.DocumentModelResolver
web.xml: org.nuxeo.ecm.platform.ui.web.rest.FancyURLFilter
web.xml: org.nuxeo.ecm.webapp.shield.SessionExpirationFilter
web.xml: <servlet-class>org.nuxeo.os.web.ui.Downloader</servlet-class>
these have to be moved too.
|
|
There are mainly 2 options :
- migrate NXTheme inside nuxeo.ear
- leave NXThemes outside
For second case, we will need to use the Runtime remoting features to be able to share the Extension Points declarations and contributions across the isolated class loaders.
Jean Marc, if this is the option you choose, Bogdan will help you on that (this is a good test case for the new features of the runtime).
Totally isolating NXThemes et Nuxeo has one major drawback : it means that nxThemes editor will never be able to interact with nuxeo5 seam components.
|
|
|
|
![]() |
|
_______________________________________________
ECM-tickets mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets
