On May 4, 2009, at 1:35 PM, Asiri Rathnayake wrote: > Hi > > On Mon, May 4, 2009 at 4:38 PM, Vincent Massol <[email protected]> > wrote: > >> >> On May 4, 2009, at 12:35 PM, Asiri Rathnayake wrote: >> >>> Hi Devs, >>> >>> >>>> The other feature is a frequently requested one (auto-strart) and >>>> admins >>>> are having a hard time without this feature :) >>>> >>>> >>> There is a slight change of approach towards implementing this >>> feature. Due >>> to some technical limitations it seems like we cannot start the >>> openoffice >>> server when XE is started. But there is a better solution, we start >>> the >>> openoffice server when officeimporter component is loaded into the >>> memory >>> first time - this is done only if the autostart configuration option >>> is set. >>> >>> Everything else remains the same. >>> >>> I hope this is ok with you, any comments are welcome. >> >> hmmm as a general comment I don't like it too much since it means the >> user will have to wait more when doing the first import. >> > > Actually it's not the first import that will start the openoffice > server but > the first time the wiki is opened on browser. It seems like plexus > loads all > the components when the user visits the wiki for the first time on > browser.
No this is not the case. Components are loaded on the first lookup. > I consider this a hack and not a better solution. >> >> It should pretty easy to add a clean notion of container >> initialization using components (in xwiki-containers). Right now >> there's already the notion of Request init and Execution context >> init. > > >> Note also that in XWiki.java there's already the notion of >> initialization (the variable "initdone" is put in the XWiki Context). > > > Well, I could directly load openoffice server manager component upon > container initialization (DefaultServletContainerInitializer) and > start the > openoffice server. But we don't want openoffice server manipulation > code > inside DefaultServletContainerInitializer, I didn't say that! Of course we don't want to tie in any dependency. Asiri you should read about Request initialization and Execution Context initialization. It doesn't tie any user of it in the xwiki- containers module. -Vincent > that's why we wanted to go with > ObservationManager. But then came the problem of loading openoffice > server > manager at startup (otherwise it will not receive startup > notifications). I > can't think of a working acceptable solution that will allow me to > load the > openoffice server manager component at startup.. > > Thanks. > > - Asiri _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
