I usually give the page with the form it's own action (ie.
xxxUpdateSetupAction which I use for stuff like populating lists, etc.) and
the target action of the form has it's own seperate action (ie.
xxxUpdateAction). In this situation you could set the input attribute of the
/xxxUpdate action
The other way to do it is to use scaffolding which is
part of the struts release.
It is really a best-practices framework that is
available for use.
sandeep
--- Dennis Meelis [EMAIL PROTECTED] wrote:
I usually give the page with the form it's own
action (ie.
xxxUpdateSetupAction which I use
If you are using request scope beans than using the
getters and setters is quite normal. Not too hackish
in my opinion..
sandeep
--- Linus Nikander [EMAIL PROTECTED] wrote:
First off, thank you for the reply.
As you point out both solutions that you suggest
have a certain hackishness
over
I've been struggling with a problem similar to the one described (and
solved) at
http://www.mail-archive.com/[EMAIL PROTECTED]/msg50901.html .
Is this really the recommended way to solve population / repopulation of
properties stored in a List() of
whatever-data-object-i-need-in-the-form-of-a-bean
I've seen two ways of dealing w/ this problem, both of which I see as 'hackish'
in nature.
Solution A:
In your getters/setters you implement the following code
public MyCustomBean getMyCustomBean(int index) {
while(index = myCustomBeanList.size()) {
myCustomBeanList.add(new
*sigh* I meant to include the following code snippet before hitting send,
but Outlook had other ideas
logic-el:iterate name=myList property=foo id=foo
c:out value=${foo.description}/
html-el:select property=myField indexed=true name=foo
First off, thank you for the reply.
As you point out both solutions that you suggest have a certain hackishness
over them it would be nice to avoid. As displaying data from a DB-table,
allowing that data to be edited (en masse, not one record at a time), must
be a pretty common task, doesn't
7 matches
Mail list logo
