blem since java web apps are dependent
on the class files generated by your application. Unless I'm missing out on
some functionality of Tomcat that I'm aware of I think your best bet is
obfuscation.
Travis Beech
-Original Message-
From: KrantiT K K Parisa [mailto:kranti.par
urns.
On Jan 20, 2010, at 9:25 PM, Travis Beech wrote:
> I would make sure that your DAO class is closing any statements,
> resultsets, and connections that are no longer being used once your
> method call returns.
>
> Since GC does happen immediately your db resources could s
I would make sure that your DAO class is closing any statements,
resultsets, and connections that are no longer being used once your
method call returns.
Since GC does happen immediately your db resources could still be in
memory.
Travis Beech
On Jan 20, 2010, at 3:50 PM, Ken Bowen wrote
Modify your servlet mapping in your web.xml so that you have more than one
mapping to that servlet.
Take the following xml snippet as an example, each of the three servlet
mappings will map to a single servlet. This would allow someone to use three
different URL's to access the same servlet.
R
Mark,
Thanks for the info.
Travis Beech
On Jan 16, 2010, at 3:34 AM, Mark Thomas wrote:
> On 16/01/2010 06:41, Travis Beech wrote:
>> Are there any workarounds available that will retrieve the entire
>> string
>> (SESSIONID=1234567890)?
>
> The next Tomcat 6.0.x rel
advance,
Travis Beech
