[ http://issues.apache.org/jira/browse/COCOON-761?page=all ]
Pier Fumagalli updated COCOON-761:
----------------------------------
Reporter: Marc Portier (was: Marc Portier)
> [woody] initial binding framework
> ---------------------------------
>
> Key: COCOON-761
> URL: http://issues.apache.org/jira/browse/COCOON-761
> Project: Cocoon
> Type: Improvement
> Components: - Components: Avalon
> Versions: 2.1.8-dev (Current SVN)
> Environment: Operating System: other
> Platform: Other
> Reporter: Marc Portier
> Assignee: Cocoon Developers Team
> Priority: Minor
> Attachments: woody-bind.patch, woody-bind.patch
>
> A first functional throw at the implementation of some Binding ideas for
> connecting Woody forms to actual back-ends.
> The enhancement is packaged as a patch for the Woody-block where it introduces
> - code in the o.a.c.woody.binding package
> - some new BindingManager component to be declared
> - supporting logging xpatch files
> - a sample showing the current features.
> - usage of a new xml-namespace: http://apache.org/cocoon/woody/binding/1.0 for
> the declarations in the 'binding'-file
> More explanation/ideas to be found on the mailarchives.
> - http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=105703782520964&w=2
> - http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=105834927217234&w=2
> Please direct your comments to the list.
> Known Limitations:
> - no documentation yet: should get into the wiki with the other woody-docos
> - no namespace-awareness concerning the xml-backend-objectmodel (how to
> express
> in jxpath?)
> - the repeater requires a unique id --> this calls for a hidden widget inside
> Woody (actually leaving it out from the template should do as soon as Woody
> learns how to deal with widgets that are missing on the form)
> - simple way to address this from flowscript is missing
> - BindingManager should maintain a cache of the bindings it build (pattern to
> be
> copied from woody form-manager, or factored out/reused)
> - no dataconversions yet: binding strictly 'String'
> - no binding for booleanfield and multivaluefield
> - list of builders probably nicer in the xconf in long run
> - use of jxpath was to enable binding to javabeans (coming from O/R layer)
> current patch lacks the sample though.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira