On Mon, Jan 09, 2006 at 08:16:00PM +0200, Oded Arbel wrote:
The problem is like this (the actual system is far more complex):
- suppose two web applications, app1 and app2, both use some API (which
I developed myself).
- I don't want to develop the API twice on both web applications, so I
Hassan Schroeder [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
No. But I wouldn't have *any* expectations of an ambiguous situation.
Out of curiousity, have you tried this with any different containers
(Jetty, Resin, JRun, ...)?
no, I haven't. I think I've got a
On Sun, Dec 18, 2005 at 09:06:22AM -0500, Martin Gainty wrote:
Did you include the core taglib spec before using 'c' reference identifier
%@ taglib prefix=c uri=http://java.sun.com/jsp/jstl/core; %
Of course. It's the very first line in testit.jsp. w/o that it
wouldn't work even for
I'm having some trouble getting the c:import tag to work right.
It seems to be perfectly fine when the request that tomcat receives is
a GET request. However, when it receives a HEAD request instead, c:import
never actually reads the data.
Is this a known bug? Is it fixed in a
On Mon, Nov 28, 2005 at 06:24:52PM +0100, Lionel Farbos wrote:
Hi Juan,
I think your problem can't be solved (only) by Tomcat.
The problem is that objets stay in memory because of pointers on static
references...
but aren't those supposed to go away when the classloader is no
On 11/22/05, Kyle [EMAIL PROTECTED] wrote:
If you set which ever server.xml parameter it is that auto-reloads an
application (I think it's reloadable=true, or something like that) and
just have your users recompile their entire app each time and then ftp
it into the relevant directory,
