cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Ellis Parrott <parr...@fas.harvard.edu>
Subject Re: DO NOT REPLY [Bug 14449] New: - Dynamic models in XMLForms
Date Mon, 11 Nov 2002 16:35:56 GMT

Hi,

I have a hacked version of the Form class that uses a Map as a model
object, and so serves as a basic dynamic model. It just uses XPath strings
as the keys for the values; it can handle simple arrays but nothing fancy.
I'm using it just fine at this point; I'm developing a dynamic multiform
application (ala college application) and store the keys/values in a
simple database table, since the application rarely is completed in one
session.

While this isn't exactly in the spirit of Cocoon (non-XML), it works and
should be useful at least as a development/prototyping tool.

When I get a chance later this week, I'll make a diff versus the latest
CVS source and attach it to this bug/enhancement report.


rob


On 11 Nov 2002 bugzilla@apache.org wrote:

> DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
> RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
> <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14449>.
> ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
> INSERTED IN THE BUG DATABASE.
>
> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14449
>
> Dynamic models in XMLForms
>
>            Summary: Dynamic models in XMLForms
>            Product: Cocoon 2
>            Version: Current CVS
>           Platform: All
>         OS/Version: All
>             Status: NEW
>           Severity: Enhancement
>           Priority: Other
>          Component: general components
>         AssignedTo: cocoon-dev@xml.apache.org
>         ReportedBy: alonso@aafunky.com
>
>
> Currently, a model must be specified before hand. For example, you have to
> create a model bean and all the properties and methods are statically created
> there. Then you must use an action to manipulate them.
>
> It would be pretty nice if you could load some dynamic data and metadata into
> the model. For examples, you can now have DOM nodes in properties and
> manipulate them in actions. What if you could load the whole node and map not
> only values, but also properties from there into the model?
>
> Hope more people could elaborate on this, since I'm not sure I'm explaining it
> clearly. Thanks.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message