As far as drop-downs, I typically populate all (or most) of mine from a
database at application startup using a ServletListener. I stuff these
into the application scope as Lists of LabelValue beans. Then I code
up a ReloadAction that can call my Listener to reload them all. I've
found this useful so I don't have to restart the app if data changes.
If I have edit screens for the drop-downs, I'll replace the List in
application scope after saving.
Matt
On Apr 8, 2005, at 12:03 PM, Christine Huang wrote:
If those drop-down values are not dynamic, I would use a application
scope bean.
If it is dynamic, like credit card profiles in a dropdown list for a
particular user, I will declare it as ActionForm property.
I would like to hear about other people's solution.
Christine
On Apr 8, 2005 12:18 PM, Anil <[EMAIL PROTECTED]> wrote:
Leon Rosenberg <struts_user <at> anotheria.net> writes:
Sorry, but what exactly do you mean with meta information?
Leon
-----Ursprüngliche Nachricht-----
Von: news [mailto:news <at> sea.gmane.org] Im Auftrag von Anil
Gesendet: Freitag, 8. April 2005 02:34
An: user <at> struts.apache.org
Betreff: Meta Information in Action Form
Hi All,
Is it good approach to keep the meta information in action form ?
Thanks in advance.
Regards,
Anil.
--------------------------------------------------------------------
-
To unsubscribe, e-mail: user-unsubscribe <at> struts.apache.org
For additional commands, e-mail: user-help <at> struts.apache.org
Hi Leon,
Thanks for the reply. Meta information is like drop-down values that
are being
shown in a JSP page. In my case, this data should be fetched from
database.
Before going to the JSP page, I have to make sure that the drop-down
values
exist somewhere in scope. Here my question is, Is it ok to keep this
kind of
information in Action Form?
Thanks,
Anil.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
