Hi,
I wonder if they are some specific recommendations, in addition to
what's described in [1] and [2] ?
My particular use-case, is to know if there is such a rule as to
create one maven module for one xwiki component, or if several
components can be grouped in the same maven module.
Detailed description: for the xwiki-contrib-mailarchive-api, I started
from a monolithic class (@Component), then I started splitting it up
in several classes. While each of these sub-groups could be considered
components (highly related to the mail archive use-case, ie not
particularly re-usable), for now their life-cycle is managed by the
main Component (ie if one of them needs a query manager, it is not
injected by xwiki framework, but provided to it by the main
Component).
Would it be recommended to move to a whole component architecture, and
make all these sub-components Components managed by xwiki framework ?
Are there any limitations (perfs...) to do it that way ?
I'm pretty sure it's obvious to xwiki devs, but I prefer to ask.
Br,
Jeremie
[1]
http://platform.xwiki.org/xwiki/bin/view/DevGuide/WritingComponents
[2]
http://extensions.xwiki.org/xwiki/bin/view/Extension/Component+Module