Hi Markus,
>If we want to store custom-objects for each instance of our application, we
>would store them as attribute with
>
>ApplicationContext.setAttribute(String, Object)
This is correct.
>If two instances use
>ApplicationContext.setAttribute("name", new Object());
>they access different objects and do not overwrite objects of other
>instances having the same name ("name"), right?
Right. ApplicationContext is limited to an application session.
Just make sure that you do not use any statics - especially for storing ULC
widgets.
See also
http://lists.canoo.com/mailman/private/ulc-developer/2005/002032.html
Thanks and regards,
Janak
>-----Original Message-----
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED] Behalf Of
>[EMAIL PROTECTED]
>Sent: Wednesday, January 24, 2007 12:02 PM
>To: [email protected]
>Subject: [ULC-developer] ApplicationContext.setAttribute to store
>session-specific objects?
>
>
>
>Dear ulc-community.
>
>Just to get sure:
>
>We plan to deploy our application on an application server and execute it
>via JNLP-Launcher.
>
>If we want to store custom-objects for each instance of our application, we
>would store them as attribute with
>
>ApplicationContext.setAttribute(String, Object)
>
>In our opinion the ApplicationContext.setAttribute/.getAttribute-methods
>are comparable with setAttribute/getAttribute from HttpSession.java and
>ApplicationContext.terminate() will close the specific session and not stop
>all application-instances of this application.
>
>We want to get totally sure, before we have to refactor too many classes.
>If two instances use
>ApplicationContext.setAttribute("name", new Object());
>they access different objects and do not overwrite objects of other
>instances having the same name ("name"), right?
>
>
>Thank you in advance.
>
>
>Best regards,
>
>MarkusP0zw"(
>x
>K,'=i%j
>Kq)!J[y2[jzr ()+
>w~iuk
>
_______________________________________________
ULC-developer mailing list
[email protected]
http://lists.canoo.com/mailman/listinfo/ulc-developer
