On Mon, Jan 17, 2005 at 05:41:48PM -0600, Jonathan Wilson wrote: : Thanks for responding.
Not a problem. You're quite welcome. : (Note to self: weird behaviour == restart IDE) You've stumbled onto the primary reason I'm not a fan of IDE/container integration. =) Too much weirdness. I suppose that makes me very old-school. : By "store in application scope" you mean: : getServletContext().setAttribute(string, object) right?? Correct! : This is then accessible via : (object)getServletContext().getAttribute(string) Ditto. : had static fields set they would still be set and accessible via : objectclassname.<i>public static string object.getSetting()</i> Once you fetch the object from the ServletContext, it's like any other object. You downcast it to the proper type and go to work. What makes the ServletContext just a little better than a singleton (which is another way of making an object globally accessible) is that there's now loose coupling between the object's class and its access: client code (other objects) use the ServletContext as the single point of contact. If the type of object changes, client code doesn't have to know... -QM -- software -- http://www.brandxdev.net tech news -- http://www.RoarNetworX.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
