you should be acquiring your config params in the way I show, and then setting them perhaps in the application scope, or maybe a registry, or whatever pattern you wish. but do not make your "normal" classes attempt to access any objects like servletconfig or otherise as that breaks good design.
> -----Original Message----- > From: Andreas Andersson [mailto:[EMAIL PROTECTED] > Sent: 06 December 2004 13:12 > To: Tomcat Users List > Subject: Re: web.xml > > > Allistair Crossley wrote: > > "normal" class? Is that a Servlet? > > Well, no. This class is called from another class wich in > turn is used > in a jsp-page as a session bean. > > Do I have to pass the value down all the way via jsp:setProperty? > > -- > Andreas Andersson > IT Dept. > Travelstart Nordic > [EMAIL PROTECTED] > http://www.travelstart.se > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > <FONT SIZE=1 FACE="VERDANA,ARIAL" COLOR=BLUE> ------------------------------------------------------- QAS Ltd. Developers of QuickAddress Software <a href="http://www.qas.com";>www.qas.com</a> Registered in England: No 2582055 Registered in Australia: No 082 851 474 ------------------------------------------------------- </FONT> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
