Sylvain Wallez wrote:
I could give it a shot but I have no deeper knowledge of cocoon.xconf
syntax in this case. Do we have to make every widget a component? That
doesn't feel right.
Nono, what I'm talking about is the various subcontainers that exist in
CForms, such as <forms-datatypes> <forms-formmanager> and
<forms-bindings> and move one level up the components they define.
A question. Right now it looks like this:
<forms-formmanager>
<widgets>
<widget name="form"
src="org.apache.cocoon.forms.formmodel.FormDefinitionBuilder"/>
<widget name="field"
src="org.apache.cocoon.forms.formmodel.FieldDefinitionBuilder"/>
<widget name="group"
src="org.apache.cocoon.forms.formmodel.GroupDefinitionBuilder"/>
</forms-formmanager>
why was widget definition builder selector implemented as
SimpleServiceSelector and not as DefaultServiceSelector in first place?
So this changes nothing to the architecture and the existing components,
but will lead to small changes in the configuration.
--
Leszek Gawron [EMAIL PROTECTED]
IT Manager MobileBox sp. z o.o.
+48 (61) 855 06 67 http://www.mobilebox.pl
mobile: +48 (501) 720 812 fax: +48 (61) 853 29 65
