of a (exploded) war file.
Thanks for your reply,
Glen
2007/10/11, Christopher Schultz [EMAIL PROTECTED]:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Glen,
Glen Vermeylen wrote:
Hi all,
Recently I moved to a (ancient) project which uses following layout:
content/
*.jsp
/WEB-INF
there,
instantly seeing changes to jsp's and class files.
With the current structure this seems impossible, forcing me every time I
make a change to rebuild the war and redeploy the application.
Is it possible to run the application from my project folder without
touching the source layout?
Regards,
Glen
-5.5-doc/jndi-datasource-examples-howto.html
and found a few differences.
Please see my replies to your post below:
On 4/20/07, Glen Vermeylen [EMAIL PROTECTED] wrote:
Hello everybody,
I'm trying to move a global jdbc resource out of server.xml so it is
application specific. Following
Thanks for the response,
We use tomcat 5.5.
-Glen
2007/4/20, Rashmi Rubdi [EMAIL PROTECTED]:
Hello Glen,
What is the version of Tomcat? I'm asking for the version because the
JNDI Datasource configuration is different for different version of
Tomcat. The one for 4.x is different from the
Hello everybody,
I'm trying to move a global jdbc resource out of server.xml so it is
application specific. Following is the server.xml (which works fine)
?xml version=1.0 encoding=UTF-8?
Server port=8005 shutdown=SHUTDOWN
Listener className=org.apache.catalina.core.AprLifecycleListener/
We use Tomcat 5.5.20.
I actually have no synchronization in place whatsoever. I will change to
hashtable and see if it solves the problem.
Thank you.
2007/3/7, Caldarale, Charles R [EMAIL PROTECTED]:
From: Glen Vermeylen [mailto:[EMAIL PROTECTED]
Subject: Retrieve list of all sessions
to instantiate my set with something like:
Collections.synchronizedSet( new java.util.HashSet())
Or is it better to use directly the old hashtable ?
Best regards.
Quoting Glen Vermeylen [EMAIL PROTECTED]:
We use Tomcat 5.5.20.
I actually have no synchronization in place whatsoever. I will change
Hello all,
I've created a management screen which lists all currently logged in users.
This list is kept as a hashmap and is kept in sync with reality in the
following way:
At login-time I put the sessions in a list.
A sessionlistener removes any sessions from this map when sessionDestroyed()