Title: RE: extending XMLForms for different kinds of models...opinions?
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?

Jonathan,
 
please elaborate on the multiple models requirement.
 
I think that Josema's idea is a significant step forward.
It does not prohibit future extensions, so I definitely support it, but in the meanwhile I am interested to hear what else can we do in the future.
 
 
 
-=Ivelin=-
----- Original Message -----
Sent: Saturday, February 15, 2003 1:00 PM
Subject: RE: extending XMLForms for different kinds of models...opinions?

As a user of cocoon, I see this as a very advantageous feature.  I am currently using cocoon/xmlform and have been developing with it for about five months now.

Your suggestion matches some of the thoughts I was having at the start of my project while I was becoming accustomed to using the framework.  I have taken advantage of the javabean architecture in the sense that I can dynamically grab data from different data sources, but I agree in the simple cases an xml model would be well-suited.

Another suggestion I would have is to allow for multiple models.  The W3C spec for xforms has been designed around multiple models; if a second revision of xmlforms is in the works, I would suggest investigating this feature.

Jon

-----Original Message-----
From: Josema Alonso
To: Cocoon-Users
Sent: 2/15/03 11:39 AM
Subject: Re: extending XMLForms for different kinds of models...opinions?

Jeremy,

I posted here cause I wanted to know if the users would like that
feature to
be added. I thought the dev list would be more suitable in case of
discussing the way of implementing it.

Since I'm not currently subscribed to the dev list, feel free to cc the
message there if you want to.

Btw, glad you like it.

Thanks.


----- Original Message -----
From: "Jeremy Quinn" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, February 15, 2003 11:24 AM
Subject: Re: extending XMLForms for different kinds of
models...opinions?


>
> On Friday, February 14, 2003, at 01:07 PM, Josema Alonso wrote:
>
> > Dear all,
> >
> > I need your suggestions and opinions in extending the current
XMLForm
> > model
> > approach. If you use XMLForm or are thinking about using it soon,
I'd
> > suggest youy to read this message and send some feedback to the
list.
> >
>
> <snip/>
>
> Would it not be best to discuss this on Cocoon-Dev?
>
> Very nice idea, BTW!
>
> regards Jeremy
>
>
> ---------------------------------------------------------------------
> Please check that your question  has not already been answered in the
> FAQ before posting.     <http://xml.apache.org/cocoon/faq/index.html>
>
> To unsubscribe, e-mail:     <[EMAIL PROTECTED]>
> For additional commands, e-mail:   <[EMAIL PROTECTED]>
>
>






---------------------------------------------------------------------
Please check that your question  has not already been answered in the
FAQ before posting.     <http://xml.apache.org/cocoon/faq/index.html>

To unsubscribe, e-mail:     <[EMAIL PROTECTED]>
For additional commands, e-mail:   <[EMAIL PROTECTED]>

Reply via email to