+1 from Porto Anca Paula Luca wrote: > Hi devs, > > for better management of the XWatch data, I'd like to create a XWiki Watch > component (plugin) to handle Watch specific actions on the server side. The > main > reason I wish to do this is to eliminate the duplicate query code in Watch, > caused by the fact that the same actions are needed from the GWT Servlet and > the > wiki documents. Since querying is a matter of accessing Watch data, I see no > reason for maintaining duplicate, independent implementations for it and not > centralizing it in a component. > Besides eliminating duplicate code, the component would also provide support > for: > - universal, easier access to Watch data regardless of the interface/API (GWT > servlet, default implementation of XWatch portal pages, custom wiki pages) > - better implementation of the Watch data model layer on top of xwiki data > model > (object/document dependencies, data consistency, providing universal API for > safer manipulation of data from this pov). > > By adding this component, Watch would be deployed as a plugin + xar, as other > XWiki applications are (but with some custom modifications in web.xml, > required > by the GWT servlet). > > I would like to implement this component in the following iteration of XWiki > Watch (1.1 M2) to have it fully tested and debugged until the 1.1 final > release. > > WDYT? > > Happy coding, > Anca Luca > > > > _______________________________________________ > devs mailing list > [email protected] > http://lists.xwiki.org/mailman/listinfo/devs > >
-- Ludovic Dubost Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
