On 7/11/07, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
Side note: and that's why we need T5 IoC and not Guice or Spring.
Those don't have a concept similar to Tapestry's service configuration
/ contribution system.
Actually i really don't understand why they have not such a feature...
--
Ma
Hi,
So I created a singleton class with static field, created at the first
session since the last server restart, but I didn't understand why I should
use the ASO notation also. I don't need, I think, to store the object in the
session, would be redundant, wouldn't be?
The object is already avail
You can use the @ApplicationState annotation on a field to mark it as
an application-wide state object. It will be stored in the
HttpSession.
Most of the infrastructure for storing such an object in the
ServletContext is available; see the
ApplicationStatePersistenceStrategySource service.
What
Try using a public class with static fields and methods. This is best
for things that can be recreated programmatically, like a hardcoded
list of months. Just remember that changes you make will disappear
when you restart your app container, unless you migrate the data to a
more persistant stora
Hi,
I search into the mailing list and didn't find how to declare an object such
as an ArrayList at the context level.
ASO is for session and @Persist for requests, but what about the
Application/Context level?
My site needs to maintains a list of users with their status without having
to reload
