On Apr 8, 2005 1:12 PM, Anil <[EMAIL PROTECTED]> wrote:
> Matt Raible raibledesigns.com> writes:
>
> >
> > 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
On Apr 8, 2005, at 2:12 PM, Anil wrote:
Matt Raible raibledesigns.com> writes:
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
Craig McClanahan wrote:
That being said, I have seen cases where the potential performance
penalty is quite large (many seconds of database access), which will
show up in one of your users waiting an abnormally long time for their
response -- not something I would find very appealling.
I don't l
Matt Raible raibledesigns.com> writes:
>
> 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
On Apr 8, 2005 12:39 PM, Dave Newton <[EMAIL PROTECTED]> wrote:
> Craig McClanahan wrote:
>
> >On Apr 8, 2005 11:28 AM, Dave Newton <[EMAIL PROTECTED]> wrote:
> >
> >
> >>I haven't done much (anything?) with servlet listeners--what's the
> >>advantage to doing it this way as opposed to a servlet.i
Craig McClanahan wrote:
On Apr 8, 2005 11:28 AM, Dave Newton <[EMAIL PROTECTED]> wrote:
I haven't done much (anything?) with servlet listeners--what's the
advantage to doing it this way as opposed to a servlet.init that loads
on app startup? Generally what we've done is to have a thread that
che
On Apr 8, 2005 12:15 PM, Matt Raible <[EMAIL PROTECTED]> wrote:
>
> On Apr 8, 2005, at 1:00 PM, Christine Huang wrote:
>
> > On Apr 8, 2005 1:40 PM, Craig McClanahan <[EMAIL PROTECTED]> wrote:
> >>
> >> The servlet container is *not* required to leave your load-on-startup
> >> servlet loaded for
On Apr 8, 2005, at 1:00 PM, Christine Huang wrote:
On Apr 8, 2005 1:40 PM, Craig McClanahan <[EMAIL PROTECTED]> wrote:
The servlet container is *not* required to leave your load-on-startup
servlet loaded for the entire duration of the webapp's lifetime
(although, in practice, most containers do).
group.com/
>
>
> -Original Message-
> From: Joe Germuska [mailto:[EMAIL PROTECTED]
> Sent: Friday, April 08, 2005 2:35 PM
> To: Struts Users Mailing List
> Subject: Re: Meta Information in Action Form
>
> Matt's general approach is the one we use also,
On Apr 8, 2005 1:40 PM, Craig McClanahan <[EMAIL PROTECTED]> wrote:
>
> The servlet container is *not* required to leave your load-on-startup
> servlet loaded for the entire duration of the webapp's lifetime
> (although, in practice, most containers do). For example, the
> container could unload
nt: Friday, April 08, 2005 2:35 PM
To: Struts Users Mailing List
Subject: Re: Meta Information in Action Form
Matt's general approach is the one we use also, except instead of
ServletListeners and the database, we use the DigestingPlugIn, which
produces objects based on XML and can
Matt's general approach is the one we use also, except instead of
ServletListeners and the database, we use the DigestingPlugIn, which
produces objects based on XML and can put them in the application
context. There's an example in the mailreader app which you should
be able to just about cut-
On Apr 8, 2005 11:28 AM, Dave Newton <[EMAIL PROTECTED]> wrote:
> Matt Raible wrote:
>
> > 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 bea
Matt Raible wrote:
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
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 t
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 P
Leon Rosenberg anotheria.net> writes:
>
> Sorry, but what exactly do you mean with meta information?
>
> Leon
>
> > -UrsprÃngliche Nachricht-
> > Von: news [mailto:news sea.gmane.org] Im Auftrag von Anil
> > Gesendet: Freitag, 8. April 2005 02:34
> > An: user struts.apache.org
> >
Sorry, but what exactly do you mean with meta information?
Leon
> -Ursprüngliche Nachricht-
> Von: news [mailto:[EMAIL PROTECTED] Im Auftrag von Anil
> Gesendet: Freitag, 8. April 2005 02:34
> An: user@struts.apache.org
> Betreff: Meta Information in Action Form
>
>
> Hi All,
>
> Is i
Sorry, but what exactly do you mean with meta information?
Leon
> -Ursprüngliche Nachricht-
> Von: news [mailto:[EMAIL PROTECTED] Im Auftrag von Anil
> Gesendet: Freitag, 8. April 2005 02:34
> An: user@struts.apache.org
> Betreff: Meta Information in Action Form
>
>
> Hi All,
>
> Is i
19 matches
Mail list logo
