Ivelin
The
W3C's candidate recommendation for xforms defines both:
1. a
element named 'model' enabling one to bind an object to a named model in the
form
2. a
common attribute named 'model' enabling one to choose which model to bind an
xforms control to
Basically, the idea would be to change the existing one-to-one
relationship between a form and its model to a one-to-many. I could see an
advantage in keeping a primary model for each form, but still allow for multiple
models to be referenced.
The
primary value I see in this approach is the ability to easily pull data from
multiple sources. Example:
I am
currently in the development of a project using cocoon/xmlforms as the front-end
and xindice as the back-end. In order to pull data from the xindice
database into my xmlforms, I currently have my javabean model set up with a
field referencing a class that returns a jxpath Container which connects to the
Xindice database.
If
multiple models were supported by xmlform, I could more easily separate the
database data from the form/input data.
Jon
-----Original
Message-----
From: ivelin [mailto:[EMAIL PROTECTED]] Sent: Saturday, February 15, 2003 9:30 PM To: [EMAIL PROTECTED]; 'Josema Alonso ' Subject: Re: extending XMLForms for different kinds of models...opinions?
|
Title: RE: extending XMLForms for different kinds of models...opinions?
- Re: extending XMLForms for different kinds of models...opi... Christian Haul
- Re: extending XMLForms for different kinds of models.... Josema Alonso
- Re: extending XMLForms for different kinds of mod... Christian Haul
- Re: extending XMLForms for different kinds of... Josema Alonso
- Re: extending XMLForms for different kind... Christian Haul
- RE: extending XMLForms for different kinds of models...opi... Sylvain.Thevoz
- Re: extending XMLForms for different kinds of models.... Josema Alonso
- RE: extending XMLForms for different kinds of models...opi... Jonathan Spaeth
- Jonathan Spaeth