How do I even set up a form for updating an object? If I model an event with event parameters going into a FrontEndView, it displays the data [read-only] at the top of the page.
If I model an event with event parameters going from the FrontEndView to a system state, it displays _another_ _empty_ form with exactly the same parameters. [I don't want to re-type _all_ the attributes for an object if I am just changing one attribute.] The problem is that I can't see how to populate the update form with the values from the object _before_ the page is displayed. The delegated controller method only gives me access to one form. -Tim On Wed, 2005-04-13 at 18:55 +0200, Wouter Zoons wrote: > hello Tim, > > Tim Dysinger wrote: > > I remodeling my pages a bit since the tablelink change [in cvs branch > > HEAD], I have been reviewing my activity diagrams. The "table" > > functionality of bpm4struts is working and I can show a collection of > > objects in a table on a page with no problems. I can have one link on > > each row to skip off to the object create/read/update/delete page. That > > works great. > > > > Is there an easy way to map an object to/from a form for my CRUD page? > > I currently have to define the event parameters going into the > > FrontEndView state that mirror[duplicate] the session object's > > attributes and then map them to/from a session object manually. If I > > just give the session object as event parameters to the FrontEndView, > > bpm4struts displays the toString() on the resulting page [which isn't > > helpful to me.] > > > > currently, no .. this is still under development, I hope to have it > available as an experimental feature in the RC-2 release, right before > going final > > for now you will explicitly need to model everything > > > > What I'm looking for is some sort of tag where I can hint to the bean > > properties I want to have on the form that directly map to an event > > parameter object's properties. [Sort of like I can hint with > > @andromda.struts.view.table.columns tag for a collection in a table.] > > > > you will be able to tag an <<Entity>> using the <<Manageable>> > stereotype, this will make the Hibernate, Spring and Bpm4struts > cartridge generate all CRUD operations for you, web pages and > everything, 100% generated > > (I'm even including support for criteria searches and the pageable lists > returned by such a search will be using the 'paging' functionality of > the underlying DB, not like the common displaytag implementation is > handling it (which does not scale too well) > > -- Wouter ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Andromda-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/andromda-user
