Marc, Am Freitag, 15. August 2003 10.10 schrieb Marc Portier: > Simon, > > some intro on Woody: http://wiki.cocoondev.org/Wiki.jsp?page=Woody Yup, that's where I got my first infos about woody from, very usefull.
> as for some additional comments... > the 'vision' would be to have any arbitrary business logic > connect to your database and then 'bind' that information into > the woody-form > > This binding is easily done programmatically by calling > widget.setValue() on the specific widget in the woody-model. > For end-user convenience a 'binding framework' is currently > foreseen that enables you to 'declare' this binding rather then > to program it. > > The current implementation uses jxpath so it works for backends > producing/expecting either XML documents or simple JavaBeans. It > does not currently offer a declarative solution towards straight > JDBC (ie sql statements and resultsets) I guess an Input/Output module binding could be usefull. I'm not sure wether I understand all the concepts right, but if there were these bindings, we could use the modular DatabaseSelectAction to retrieve data and provide it in an output module. The binding will then use this data in the loadFormFromModel. And after the woody stage, the Database*Actions could be used to write the data back. Does this make some sense? > Having said that one angle of attack would be to use some > OR/mapping or persistency framework that actually offers the > simple JavaBean view on the relation data so you can use the > declarative binding. > > Second approach is just to ignore existing binding and code it up > (not that hard, use the code of the current binding framework as > a guide. Your experience will probably yield enough insight for > the design of:) Well, I had a look at the java code of the bindings. I didn't understand how everything exactly works together. But slowly I get the big picture.. So if I understand, you talk about creating JDBC bindings, right? Well, I'm interested in this, but don't know yet if I'm able to do that. > Final approach (no promises) would be to hookup declarative > binding to JDBC sources in the binding framework. Please elaborate, I'm not sure what you mean. > As for the remaining decission: 'where do I write my (arbitrary) > controlling logic' you could go for actions, but the new flow > will easily lead you to a more comfortable state-management > inside your use case (one will typically not mix both approaches) Ok, I'm slowly getting comfortable with the flow concept.. > I thought examples for calling the binding from both are to be > found in the woody-samples section. Right, but a database sample would be very nice. Well, I'm working on that and if I get something working, I'll post it. > HTH, > don't hesitate to ask more anr/or report progress Thanx. The cocoon community seems to be very responsive and productive. Simon --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
