6 Jan
2009
6 Jan
'09
1:52 a.m.
Vincent Massol wrote:
On Jan 5, 2009, at 5:46 PM, Fabio Mancinelli wrote:
> Vincent Massol wrote:
>> On Jan 5, 2009, at 5:01 PM, Fabio Mancinelli wrote:
There's no import on any plexus class anywhere in
our components
(except in the plexus module of course).
The idea is that we should be independent of the component engine and
tomorrow move to OSGi without the need to change any existing module.
When plexus instantiate a class we don't see it. All we do is ask
xwiki's component manager to get us an instantiated class
(ComponentManager.lookup()). The plexus module then uses plexus to
implement the lookup but we can have an OSGi module that does the same
with OSGi.
I committed a fully componentized version of the REST infrastructure.
There are no real resources at the moment but only a dummy
SpacesResource, just to show you the thing.
You declare resources and their routes as components.
You declare representers for different media types as components.
You can find the implementation in the sandbox
http://svn.xwiki.org/svnroot/xwiki/sandbox/xwiki-core-rest/src/main/java/co…
and the components.xml is located at
http://svn.xwiki.org/svnroot/xwiki/sandbox/xwiki-core-rest/src/main/resourc…
I would like to hear some comments before completely porting the
remainder of what I wrote to this new architecture.
Thanks.
-Fabio
P.S.: Plexus is a really nice tool :)