|
|
|
| The following comment has been added to this issue: |
[ Permlink ] |
|
Author: Jean-Marc Orliaguet
Date: 05/03/07 12:10
Comment:
I would vote for moving nxthemes editor into nuxeo.ear/ , i.e. each deployed application will have its own theme, and its own theme-related resources
and for shared themes use the new features of nxruntime instead (that would be a new feature called "shared themes" or "common themes") actually one of the reasons why it's outside now is to be able to share resources between instances, but that could be implemented via nxruntime as I understand?.
|
|
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
