I think that changing the context path of the nuxeo webapp is not easy. Besides the hardcoded css files (which I believe you can change with a theme), from memory there are hard-coded javascript files, including some for the Seam Remoting functionality.
Sean > Hi, > > with context i mean a new war application for example /mywebapp. > > My basic doubt is: if, for example I want to make two new indipendent > applications (sites) with different user and look & feel the best > approach is add two new .war (context) to the nuxeo ear? > > So in the .ear I have nuxeo.war , mywebapp.war and mywebapptwo.war. > > This is the correct way to implement this or I need to use the domain > concept? If yes, where I can found informations about how use the > domain ? I don't have found the relative documentation or example. > > I have read in this moment the email of Domitru: sorry, what do you mean > with "use separate bundle not separate war"? > > Many thanks for your time. > > Regards, > Marco > > > > Il giorno gio, 14/06/2007 alle 10.22 +0200, Olivier Grisel ha scritto: > > mean by "context" ? If you want to define your own theme, just make > > your custom component register a new contribution to the theme > > service, either > > calling it "default" to override the default theme or with a new name > > that is > > selected by default by a new theme negociator of your own (contributed > > to the > > theme service extension point as well). > > > > _______________________________________________ > ECM mailing list > [email protected] > http://lists.nuxeo.com/mailman/listinfo/ecm > > -- Dr. Sean Radford, MBBS MSc http://www.tacola.com _______________________________________________ ECM mailing list [email protected] http://lists.nuxeo.com/mailman/listinfo/ecm
