|
|
|
| The following comment has been added to this issue: |
[ Permlink ] |
|
Author: Jean-Marc Orliaguet
Date: 19/03/07 15:17
Comment:
yes, you can do the changes in platform.ui (trunk) and nxruntime (trunk) and I can test directly in the isolated-cl branch (only ecm.webapp apart from nxthemes is currently forked).
also I think we should move the fragment declarations of seam to a separate package (outside ecm.webapp) to avoid duplications. The same goes with facelets, JSF, etc.
|
|
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
