Mark Lundquist dijo: > > A form can only be bound to one model, but I need a form that has the > effect of being bound to 2 beans (so in MVC terms the one form would > comprise 2 views, one of each model). > > Does anybody have any suggestions for how to achieve this?
You can build 2 diferents pipelines or 2 diferents flows scripts, where the binding.xml is diferent. That way you can share the definition.xml and the template.xml of the CForms. Best Regards, Antonio Gallardo > -- Mark > > > --------- > P.S. In case you remember that I am the guy who wanted to have > multiple forms on a page � well, I abandoned that approach... not just > because it was technically inconvenient with flow/continuations, but > mainly because in context of the application flow, it just sucked. Using OJB I am able to share info of many tables at all. Of course just in one form, but when using a more complex tables as: 1 master -> n details1 1 detail1 -> m details2. Then I choosed to use a 2 pages interfaces. To manage this kind of forms. > The > designer who did the preliminary user interface design liked the > multiple-forms presentation, but they didn't think about "where is this > page 'going' and how does it get there". As it turns out, from a > use-case P.O.V. this really needs to be one form with a single submit > button, so that relieved me of the need to figure out how to get 3 > forms on one page to work. Hmm... In Woody you can have diferents submit buttons. Each button define a single action. For example, 1 button for "update", another for "delete", etc. Then in the flow you decide what to do with the returned form values based on the button pressed by the user. This works fine. BTW, What means P.O.V.? Best Regards, Antonio Gallardo --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
