You still can, because for example you will have a servlet that will loaded up more
than once.
Or if you have a pre-check that checks for null and then loads it up in app context,
it will work once per jvm (not sure exactly if it is once per server or jvm).
Internationalization may be an issue
Jacob Weber wrote:
I have a lot of data that needs to be available to all users, at any
time (for example, the contents of drop-down menus, which I loaded from
an XML file). From all the posts I've seen here, the recommended place
to store global data seems to be the servletContext. Most people
At 10:43 AM -0400 5/9/04, Jacob Weber wrote:
Thanks. I'm glad you made sense of my question. :) If I do this, can I
still use Struts tags that refer to a bean? Taking the drop-down menu
example, if I store it directly in the servletContext, I can do:
But if I store it in the servletContext as "m
g with the httpsessions.
BAL
From: Joe Germuska <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
Subject: Re: Storing global data in the servletContext
Date: Sun, 9 May 2004 09:05:13 -0500
At 9:37 AM -0400 5/9/04, Brian Alexander Lee wrote:
That's intere
In article <[EMAIL PROTECTED]>,
Joe Germuska <[EMAIL PROTECTED]> wrote:
> Looking back at the original email, I would guess that the things
> read from XML config files could pretty safely be stored in each
> ServletContext -- assuming they don't change after initialization --
> drop down menu
At 9:37 AM -0400 5/9/04, Brian Alexander Lee wrote:
That's interesting, so you recommend having an EJB (running in the ejb
container) to manage data put into user sessions and servlet contexts
(running in the web container)?
I wouldn't go that far -- but then again, I'm not much of an EJB
develope
[EMAIL PROTECTED]>
Sent: Sunday, May 09, 2004 9:26 AM
Subject: Re: Storing global data in the servletContext
It sounds like you are the use case for EJB! As
for your "other question," I would always advise
using one (or a few beans) to manage everything
you put into a session
It sounds like you are the use case for EJB! As
for your "other question," I would always advise
using one (or a few beans) to manage everything
you put into a session or application context, as
much as you can logically encapsulate that.
It'll make your life easier in the long-run,
believe
8 matches
Mail list logo
