Re: Question regarding tomcat class path handling

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

Re: c:import doesn't work right with HEAD requests

> "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

Re: c:import doesn't work right with HEAD requests

On Sun, Dec 18, 2005 at 03:20:09PM -0800, Bill Barker wrote: > > <[EMAIL PROTECTED]> wrote in message > news:[EMAIL PROTECTED] > > My guess is that tomcat uses a "HEAD" request to retrieve content with > > c:import if the request for the jsp page containing the c:import was > > requested with a "

Re: c:import doesn't work right with HEAD requests

On Sun, Dec 18, 2005 at 12:26:07PM -0800, Hassan Schroeder wrote: > [EMAIL PROTECTED] wrote: > However, from the Servlet Spec -- > protected void doHead(HttpServletRequest req, > HttpServletResponse resp) > throws ServletException, IOException > Receives an HTTP HEAD request from th

Re: c:import doesn't work right with HEAD requests

On Sun, Dec 18, 2005 at 03:06:19PM +0100, Mikolaj Rydzewski wrote: > On Sat, 17 Dec 2005 [EMAIL PROTECTED] wrote: > > > 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 i

Re: c:import doesn't work right with HEAD requests

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

c:import doesn't work right with HEAD requests

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 mo

Re: Singleton memory leak after redeploying.

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 l

Re: FTP Was: Re: manager for some users

On Tue, Nov 22, 2005 at 03:33:09PM -0500, Steve Ochani wrote: > On 22 Nov 2005 at 14:14, [EMAIL PROTECTED] wrote: > > > On Tue, Nov 22, 2005 at 01:17:56PM +0100, Alex Moreno wrote: > > > The problem is that some partners has said me that this is insecure > > > and should only be used on beta appli

Re: manager for some users

> 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 d

Re: How to set restrictions on the retreival of files from some directories

On Thu, Nov 17, 2005 at 02:19:13PM -0600, Alla Winter wrote: > BY default it is possible to retrieve files located under the 'WEB-INF' > directory. For example: www.someserver.com/WEB-INF./web.xml or > www.someserver.com/WEB-INF./classes/MySer >