RE: Eclipse WTP and Tomcat 6.0.x ?

[Larry Isaacs]

Feel free to start a new thread on the Eclipse Web Tools
newsgroup (http://www.eclipse.org/newsgroups/) to ask
Eclipse related questions.  Currently in WTP, Tomcat
servers default to separate catalina.base and catalina.home.
The problem is that you don't get to choose the location for
catalina.base as it is assigned by the plug-in.  In
WTP 2.0, you will be able to specify the catalina.base
location.

Cheers,
Larry

> -Original Message-
> From: William L. Thomson Jr. [mailto:[EMAIL PROTECTED] 
> Sent: Tuesday, November 14, 2006 11:35 AM
> To: Tomcat Developers List
> Subject: RE: Eclipse WTP and Tomcat 6.0.x ?
> 
> Sorry to interrupt, and excuse my ignorance on the matter, I 
> am Netbeaner. However many are trying to use Eclipse with our 
> system installed Tomcat on Gentoo. Tomcat installed via 
> Gentoo ebuild, not a bundled one in Eclipse.
> 
> The biggest problem people run into is that the Eclipse 
> plugin does not respect CATALINA_BASE and CATALINA_HOME. It 
> expects them to be the same, when it's been a long time 
> design feature that they can be different.
> 
> Now by default Netbeans assumes they are the same, but does 
> allow one to specify both if they are different. The Tomcat 
> Eclipse plugin or etc seems to lack that ability. 
> 
> So if you are going to be improving the support or working on 
> it for future Tomcat releases. Would it be possible to 
> address the _BASE/_HOME issue at the same time.
> 
> Thanks and I know this is the wrong list for this. However, 
> since the discussion was taking place, felt it was some what 
> relevant. Thanks
> 
> --
> William L. Thomson Jr.
> Gentoo/Java
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Eclipse WTP and Tomcat 6.0.x ?

[Larry Isaacs]

Hi Henri,

Probably before the M4 release of WTP 2.0 in early January.
The Tomcat support in WTP is where my day job has my spare
time going these days, what there is of it. :)

Cheers,
Larry 

> -Original Message-
> From: Henri Gomez [mailto:[EMAIL PROTECTED] 
> Sent: Tuesday, November 14, 2006 5:53 AM
> To: Tomcat Developers List
> Subject: Eclipse WTP and Tomcat 6.0.x ?
> 
> Did there is Eclipse WTP developpers around  ?
> 
> Just in case of, when could we expect WTP to support Tomcat 
> 6.0 (still not the case in WTP 1.5.2).
> 
> The Definition for a new server runtime environment still 
> miss TC 6.0 ;(
> 
> 
> Regards
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED] For 
> additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Eclipse WTP and Tomcat 6.0.x ?

[Larry Isaacs]

Regrettably, my day job didn't allow for much change in WTP
from 1.0.x to 1.5.x, beyond sporadic bug fixing.  I should be
able to get much more done in WTP 2.0, also in the M4 release
time frame.

Cheers,
Larry

P.S. As deprecated as Contexts in server.xml is, it's still
the only approach supported across Tomcat versions since 3.x.
I'm not sure when this might change for newer Tomcats, since
too much customization unique to individual versions of Tomcat
may eat more cycles than I have available.  It's something I'm
keeping my eye on though. 

> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On 
> Behalf Of Yoav Shapira
> Sent: Tuesday, November 14, 2006 9:32 AM
> To: Tomcat Developers List
> Cc: Larry Isaacs
> Subject: Re: Eclipse WTP and Tomcat 6.0.x ?
> 
> Hi,
> Larry, thanks for these efforts.  I've been wondering for a 
> while who was maintaining this support, and never got around 
> to checking.  It's much appreciated, at least by me, but I'm 
> sure by many others as well
> ;)
> 
> Yoav
> 
> On 11/14/06, Larry Isaacs <[EMAIL PROTECTED]> wrote:
> > Hi Henri,
> >
> > Probably before the M4 release of WTP 2.0 in early January.
> > The Tomcat support in WTP is where my day job has my spare 
> time going 
> > these days, what there is of it. :)
> >
> > Cheers,
> > Larry
> >
> > > -Original Message-
> > > From: Henri Gomez [mailto:[EMAIL PROTECTED]
> > > Sent: Tuesday, November 14, 2006 5:53 AM
> > > To: Tomcat Developers List
> > > Subject: Eclipse WTP and Tomcat 6.0.x ?
> > >
> > > Did there is Eclipse WTP developpers around  ?
> > >
> > > Just in case of, when could we expect WTP to support Tomcat 6.0 
> > > (still not the case in WTP 1.5.2).
> > >
> > > The Definition for a new server runtime environment still miss TC 
> > > 6.0 ;(
> > >
> > >
> > > Regards
> > >
> > > 
> 
> > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For 
> > > additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> >
> > 
> -
> > To unsubscribe, e-mail: [EMAIL PROTECTED] For 
> > additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Eclipse WTP and Tomcat 6.0.x ?

[Larry Isaacs]

I haven't had time to look much at Tomcat 6.0.x yet.  The first
step to patch the org.eclipse.jst.server.tomcat.core plug-in
to accept Tomcat 6 as if it were Tomcat 5.5 would be to modify
the verfiyInstall.properties file and remove "common/i18n" from
the list of what it checks for in 5.5.  At that point, the
plug-in will probably accept an Tomcat version 4.0.x or later
as if it was Tomcat 5.5.  You could then try to see if the
rest of the plug-in will work as is using Tomcat 6.0.x as a 5.5
server.  If I get a chance, I'll give this a quick try in the
near future and see what happens.

Cheers,
Larry

P.S. If you are using the SDK version of WTP or use Update to
get the source, it is fairly easy to patch a plug-in.


> -Original Message-
> From: Henri Gomez [mailto:[EMAIL PROTECTED] 
> Sent: Tuesday, November 14, 2006 9:58 AM
> To: Tomcat Developers List
> Subject: Re: Eclipse WTP and Tomcat 6.0.x ?
> 
> Larry, how could we lure the current WTP 1.5.2 to use a Tomcat 6.x ?
> 
> 2006/11/14, Larry Isaacs <[EMAIL PROTECTED]>:
> > Regrettably, my day job didn't allow for much change in WTP 
> from 1.0.x 
> > to 1.5.x, beyond sporadic bug fixing.  I should be able to get much 
> > more done in WTP 2.0, also in the M4 release time frame.
> >
> > Cheers,
> > Larry
> >
> > P.S. As deprecated as Contexts in server.xml is, it's still 
> the only 
> > approach supported across Tomcat versions since 3.x.
> > I'm not sure when this might change for newer Tomcats, 
> since too much 
> > customization unique to individual versions of Tomcat may eat more 
> > cycles than I have available.  It's something I'm keeping my eye on 
> > though.
> >
> > > -Original Message-
> > > From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf 
> > > Of Yoav Shapira
> > > Sent: Tuesday, November 14, 2006 9:32 AM
> > > To: Tomcat Developers List
> > > Cc: Larry Isaacs
> > > Subject: Re: Eclipse WTP and Tomcat 6.0.x ?
> > >
> > > Hi,
> > > Larry, thanks for these efforts.  I've been wondering for a while 
> > > who was maintaining this support, and never got around to 
> checking.  
> > > It's much appreciated, at least by me, but I'm sure by 
> many others 
> > > as well
> > > ;)
> > >
> > > Yoav
> > >
> > > On 11/14/06, Larry Isaacs <[EMAIL PROTECTED]> wrote:
> > > > Hi Henri,
> > > >
> > > > Probably before the M4 release of WTP 2.0 in early January.
> > > > The Tomcat support in WTP is where my day job has my spare
> > > time going
> > > > these days, what there is of it. :)
> > > >
> > > > Cheers,
> > > > Larry
> > > >
> > > > > -Original Message-
> > > > > From: Henri Gomez [mailto:[EMAIL PROTECTED]
> > > > > Sent: Tuesday, November 14, 2006 5:53 AM
> > > > > To: Tomcat Developers List
> > > > > Subject: Eclipse WTP and Tomcat 6.0.x ?
> > > > >
> > > > > Did there is Eclipse WTP developpers around  ?
> > > > >
> > > > > Just in case of, when could we expect WTP to support 
> Tomcat 6.0 
> > > > > (still not the case in WTP 1.5.2).
> > > > >
> > > > > The Definition for a new server runtime environment 
> still miss 
> > > > > TC 6.0 ;(
> > > > >
> > > > >
> > > > > Regards
> > > > >
> > > > >
> > > 
> 
> > > > > - To unsubscribe, e-mail: 
> [EMAIL PROTECTED] For 
> > > > > additional commands, e-mail: [EMAIL PROTECTED]
> > > > >
> > > > >
> > > >
> > > >
> > > 
> 
> > > -
> > > > To unsubscribe, e-mail: [EMAIL PROTECTED] For 
> > > > additional commands, e-mail: [EMAIL PROTECTED]
> > > >
> > > >
> > >
> >
> > 
> -
> > To unsubscribe, e-mail: [EMAIL PROTECTED] For 
> > additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED] For 
> additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Eclipse WTP and Tomcat 6.0.x ?

[Larry Isaacs]

The current WTP 2.0 Integration build now contains support for
Tomcat 6.0.  Sorry this missed the M4 release, but the M4 schedule
shifted in a way that prevented this support from getting in.
Support for Servlet 2.5 is being worked on but isn't yet available.

It you want to follow along, the Eclipse bug for Tomcat 6.0 support
is:  https://bugs.eclipse.org/bugs/show_bug.cgi?id=167723

The download for this release is found at:
http://download.eclipse.org/webtools/downloads/drops/R2.0/I-I200701121953-200701121953/

FYI: Unlike most WTP releases, there is no JEM dependency listed with
this release of WTP.  Changes to the emf-sdo-xsd dependency requires
a new build of JEM.  This isn't available from the JEM project yet, so
this release of WTP includes WTP built versions of the JEM plug-ins.

Cheers,
Larry

> -Original Message-
> From: Odilon Oliveira [mailto:[EMAIL PROTECTED] 
> Sent: Tuesday, November 14, 2006 3:43 PM
> To: Tomcat Developers List
> Subject: Re: Eclipse WTP and Tomcat 6.0.x ?
> 
> +1 ! For sure =)
> 
> On 11/14/06, Ian Darwin <[EMAIL PROTECTED]> wrote:
> >
> > Yoav Shapira wrote:
> > > Hi,
> > > Larry, thanks for these efforts.  I've been wondering for a while 
> > > who was maintaining this support, and never got around to 
> checking.  
> > > It's much appreciated, at least by me, but I'm sure by 
> many others 
> > > as well
> >
> > +1 here too!
> >
> > 
> -
> > To unsubscribe, e-mail: [EMAIL PROTECTED] For 
> > additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> 
> 
> --
> ---
> dilas.com.br
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Access WEB-INF through the JK NSAPI connector

[Larry Isaacs]

I believe your PathCheck is the expected approach.  It is
mentioned in the documentation:

http://tomcat.apache.org/connectors-doc-archive/jk2/jk/neshowto.html

I can't say how up to date this document is, however.  Note that
in Tomcat 3.3.x, its auto-generated object.conf file included:

###
# Protecting the WEB-INF and META-INF directories.
###
PathCheck fn="deny-existence" path="*/WEB-INF"
PathCheck fn="deny-existence" path="*/WEB-INF/*"
PathCheck fn="deny-existence" path="*/META-INF"
PathCheck fn="deny-existence" path="*/META-INF/*"

For more details about what was generated in Tomcat 3.3.x, see:

http://svn.apache.org/repos/asf/tomcat/container/branches/tc3.3.x/src/share/org/apache/tomcat/modules/config/NSConfig.java

HTH,
Larry

> -Original Message-
> From: Greg Wetmore [mailto:[EMAIL PROTECTED] 
> Sent: Tuesday, July 11, 2006 10:52 AM
> To: dev@tomcat.apache.org
> Subject: Access WEB-INF through the JK NSAPI connector
> 
> I am looking at:
> http://svn.apache.org/repos/asf/tomcat/connectors/tags/jk1.2.x
> /JK_1_2_16/jk/native/netscape/jk_nsapi_plugin.c
> 
> I do not see any code blocks specifically checking for and 
> rejecting requests to WEB-INF/* or META-INF/*.
> 
> This seems different in design from the Apache or IIS filters 
> - for example:
>Apache 2.0 - mod_jk.c:2575
>IIS - jk_isapi_plugin.c:869
> 
> Does this represent a security flaw or a bug?
> 
> In the mean time I have configured iplanet to reject requests 
> to WEB-INF:
>   PathCheck fn="deny-existence" path="*/WEB-INF/*"
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED] For 
> additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: svn commit: r810132 - /tomcat/tc6.0.x/trunk/STATUS.txt

[Larry Isaacs]

Hi Filip,

I have a vague recollection about tripping over this issue while working on the 
Tomcat support in the Eclipse Web Tools Platform.  WTP has its own version(s) 
of VirtualWebappLoader, called WtpWebappLoader, to address it.  If I'm 
recalling the issue correctly, pre-pending "file:/" worked on Windows, but not 
on Linux since an absolute path ended up as "file://somedir/...".  I believe 
with the change below, pre-pending "file://" will work for Linux, but not for 
Windows, i.e. "file://C:/somedir/..." is going to have problems.  If it helps, 
I went with the URL form "file:/somedir/..." and used the following code 
snippet to get it working for Windows and Linux in WtpWebappLoader:


String path = file.getAbsolutePath();
if (path.startsWith("/")) {
path = "file:" + path;
} else {
path = "file:/" + path;
}
if (file.isDirectory()) {
addRepository(path + "/");
} else {
addRepository(path);
}

Cheers,
Larry


> -Original Message-
> From: fha...@apache.org [mailto:fha...@apache.org]
> Sent: Tuesday, September 01, 2009 1:22 PM
> To: dev@tomcat.apache.org
> Subject: svn commit: r810132 - /tomcat/tc6.0.x/trunk/STATUS.txt
>
> Author: fhanik
> Date: Tue Sep  1 17:21:59 2009
> New Revision: 810132
>
> URL: http://svn.apache.org/viewvc?rev=810132&view=rev
> Log:
> proposal
>
> Modified:
> tomcat/tc6.0.x/trunk/STATUS.txt
>
> Modified: tomcat/tc6.0.x/trunk/STATUS.txt
> URL:
> http://svn.apache.org/viewvc/tomcat/tc6.0.x/trunk/STATUS.txt?rev=810132
> &r1=810131&r2=810132&view=diff
> ===
> ===
> --- tomcat/tc6.0.x/trunk/STATUS.txt (original)
> +++ tomcat/tc6.0.x/trunk/STATUS.txt Tue Sep  1 17:21:59 2009
> @@ -321,3 +321,25 @@
>+1: funkman
>-1:
>
> +
> +* Fix VirtualWebappClassLoader file directives
> +  Index: java/org/apache/catalina/loader/VirtualWebappLoader.java
> +===
> +--- java/org/apache/catalina/loader/VirtualWebappLoader.java
>   (revision 810099)
>  java/org/apache/catalina/loader/VirtualWebappLoader.java
>   (working copy)
> +@@ -92,9 +92,9 @@
> + continue;
> + }
> + if (file.isDirectory()) {
> +-addRepository("file:/" + file.getAbsolutePath() +
> "/");
> ++addRepository("file://" + file.getAbsolutePath() +
> "/");
> + } else {
> +-addRepository("file:/" + file.getAbsolutePath());
> ++addRepository("file://" + file.getAbsolutePath());
> + }
> + }
> +
> +  +1: fhanik
> +  -1:
> +
> +
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: dev-h...@tomcat.apache.org
>

RE: svn commit: r810132 - /tomcat/tc6.0.x/trunk/STATUS.txt

[Larry Isaacs]

> -Original Message-
> From: Rainer Jung [mailto:rainer.j...@kippdata.de]
> Sent: Tuesday, September 01, 2009 3:34 PM
> To: Tomcat Developers List
> Subject: Re: svn commit: r810132 - /tomcat/tc6.0.x/trunk/STATUS.txt
>
> On 01.09.2009 20:48, Larry Isaacs wrote:
> > Hi Filip,
> >
> > I have a vague recollection about tripping over this issue while
> working on the Tomcat support in the Eclipse Web Tools Platform.  WTP
> has its own version(s) of VirtualWebappLoader, called WtpWebappLoader,
> to address it.  If I'm recalling the issue correctly, pre-pending
> "file:/" worked on Windows, but not on Linux since an absolute path
> ended up as "file://somedir/...".  I believe with the change below,
> pre-pending "file://" will work for Linux, but not for Windows, i.e.
> "file://C:/somedir/..." is going to have problems.  If it helps, I went
> with the URL form "file:/somedir/..." and used the following code
> snippet to get it working for Windows and Linux in WtpWebappLoader:
>
> Good point.
>
> >
> > String path = file.getAbsolutePath();
> > if (path.startsWith("/")) {
> > path = "file:" + path;
> > } else {
> > path = "file:/" + path;
> > }
> > if (file.isDirectory()) {
> > addRepository(path + "/");
> > } else {
> > addRepository(path);
>
> Why not: file.toURI().toString()

Won't toURI() convert spaces to '%'.  I was too lazy to determine exactly what 
the downstream code expects or tolerates with respect to this string.  Thus, I 
was attempting to improve the code in a way that involved the least amount of 
assumptions.  This is an approach that has gained popularity with me as I've 
aged. :)  I'm not sure of the impact of converting spaces to '%'.

Cheers,
Larry

>
> It seems this is not cheap, but should handle as much annoyances as
> possible (drive letters, directory trailing slashes, UNC notation).
>
> Regards,
>
> Rainer
>
> >> -Original Message-
> >> From: fha...@apache.org [mailto:fha...@apache.org]
> >> Sent: Tuesday, September 01, 2009 1:22 PM
> >> To: dev@tomcat.apache.org
> >> Subject: svn commit: r810132 - /tomcat/tc6.0.x/trunk/STATUS.txt
> >>
> >> Author: fhanik
> >> Date: Tue Sep  1 17:21:59 2009
> >> New Revision: 810132
> >>
> >> URL: http://svn.apache.org/viewvc?rev=810132&view=rev
> >> Log:
> >> proposal
> >>
> >> Modified:
> >> tomcat/tc6.0.x/trunk/STATUS.txt
> >>
> >> Modified: tomcat/tc6.0.x/trunk/STATUS.txt
> >> URL:
> >>
> http://svn.apache.org/viewvc/tomcat/tc6.0.x/trunk/STATUS.txt?rev=810132
> >> &r1=810131&r2=810132&view=diff
> >>
> ===
> >> ===
> >> --- tomcat/tc6.0.x/trunk/STATUS.txt (original)
> >> +++ tomcat/tc6.0.x/trunk/STATUS.txt Tue Sep  1 17:21:59 2009
> >> @@ -321,3 +321,25 @@
> >>+1: funkman
> >>-1:
> >>
> >> +
> >> +* Fix VirtualWebappClassLoader file directives
> >> +  Index: java/org/apache/catalina/loader/VirtualWebappLoader.java
> >> +===
> >> +--- java/org/apache/catalina/loader/VirtualWebappLoader.java
> >>   (revision 810099)
> >>  java/org/apache/catalina/loader/VirtualWebappLoader.java
> >>   (working copy)
> >> +@@ -92,9 +92,9 @@
> >> + continue;
> >> + }
> >> + if (file.isDirectory()) {
> >> +-addRepository("file:/" + file.getAbsolutePath() +
> >> "/");
> >> ++addRepository("file://" + file.getAbsolutePath() +
> >> "/");
> >> + } else {
> >> +-addRepository("file:/" + file.getAbsolutePath());
> >> ++addRepository("file://" + file.getAbsolutePath());
> >> + }
> >> + }
> >> +
> >> +  +1: fhanik
> >> +  -1:
> >> +
> >> +
> >>
> >>
> >>
> >> 
> -
> >> To unsubscribe, e-mail: dev-

RE: svn commit: r810132 - /tomcat/tc6.0.x/trunk/STATUS.txt

[Larry Isaacs]

> -Original Message-
> From: Larry Isaacs
> Sent: Wednesday, September 02, 2009 9:41 AM
> To: 'Tomcat Developers List'
> Subject: RE: svn commit: r810132 - /tomcat/tc6.0.x/trunk/STATUS.txt
>
>
>
> > -Original Message-
> > From: Rainer Jung [mailto:rainer.j...@kippdata.de]
> > Sent: Tuesday, September 01, 2009 3:34 PM
> > To: Tomcat Developers List
> > Subject: Re: svn commit: r810132 - /tomcat/tc6.0.x/trunk/STATUS.txt
> >
> > On 01.09.2009 20:48, Larry Isaacs wrote:
> > > Hi Filip,
> > >
> > > I have a vague recollection about tripping over this issue while
> > working on the Tomcat support in the Eclipse Web Tools Platform.  WTP
> > has its own version(s) of VirtualWebappLoader, called
> WtpWebappLoader,
> > to address it.  If I'm recalling the issue correctly, pre-pending
> > "file:/" worked on Windows, but not on Linux since an absolute path
> > ended up as "file://somedir/...".  I believe with the change below,
> > pre-pending "file://" will work for Linux, but not for Windows, i.e.
> > "file://C:/somedir/..." is going to have problems.  If it helps, I
> went
> > with the URL form "file:/somedir/..." and used the following code
> > snippet to get it working for Windows and Linux in WtpWebappLoader:
> >
> > Good point.
> >
> > >
> > > String path = file.getAbsolutePath();
> > > if (path.startsWith("/")) {
> > > path = "file:" + path;
> > > } else {
> > > path = "file:/" + path;
> > > }
> > > if (file.isDirectory()) {
> > > addRepository(path + "/");
> > > } else {
> > > addRepository(path);
> >
> > Why not: file.toURI().toString()
>

Oops.  I meant to say to '%' encoded form, i.e. "%20".

Larry

> Won't toURI() convert spaces to '%'.  I was too lazy to determine
> exactly what the downstream code expects or tolerates with respect to
> this string.  Thus, I was attempting to improve the code in a way that
> involved the least amount of assumptions.  This is an approach that has
> gained popularity with me as I've aged. :)  I'm not sure of the impact
> of converting spaces to '%'.
>
> Cheers,
> Larry
>
> >
> > It seems this is not cheap, but should handle as much annoyances as
> > possible (drive letters, directory trailing slashes, UNC notation).
> >
> > Regards,
> >
> > Rainer
> >
> > >> -Original Message-
> > >> From: fha...@apache.org [mailto:fha...@apache.org]
> > >> Sent: Tuesday, September 01, 2009 1:22 PM
> > >> To: dev@tomcat.apache.org
> > >> Subject: svn commit: r810132 - /tomcat/tc6.0.x/trunk/STATUS.txt
> > >>
> > >> Author: fhanik
> > >> Date: Tue Sep  1 17:21:59 2009
> > >> New Revision: 810132
> > >>
> > >> URL: http://svn.apache.org/viewvc?rev=810132&view=rev
> > >> Log:
> > >> proposal
> > >>
> > >> Modified:
> > >> tomcat/tc6.0.x/trunk/STATUS.txt
> > >>
> > >> Modified: tomcat/tc6.0.x/trunk/STATUS.txt
> > >> URL:
> > >>
> >
> http://svn.apache.org/viewvc/tomcat/tc6.0.x/trunk/STATUS.txt?rev=810132
> > >> &r1=810131&r2=810132&view=diff
> > >>
> >
> ===
> > >> ===
> > >> --- tomcat/tc6.0.x/trunk/STATUS.txt (original)
> > >> +++ tomcat/tc6.0.x/trunk/STATUS.txt Tue Sep  1 17:21:59 2009
> > >> @@ -321,3 +321,25 @@
> > >>+1: funkman
> > >>-1:
> > >>
> > >> +
> > >> +* Fix VirtualWebappClassLoader file directives
> > >> +  Index: java/org/apache/catalina/loader/VirtualWebappLoader.java
> > >>
> +===
> > >> +--- java/org/apache/catalina/loader/VirtualWebappLoader.java
> > >>   (revision 810099)
> > >>  java/org/apache/catalina/loader/VirtualWebappLoader.java
> > >>   (working copy)
> > >> +@@ -92,9 +92,9 @@
> > >> + continue;
> > >> + }
> > >> + if (file.isDirectory()) {
> > >> +-  

RE: svn commit: r810132 - /tomcat/tc6.0.x/trunk/STATUS.txt

[Larry Isaacs]

On Windows prepending "file://" to "C:\somedir\somefile" results in 
"file://C:/somedir/somefile".  I'm pretty sure URL will think "C" is the host 
name and fail if you try to use a URL object to read the file.  I think it was 
the same issue on Linux when prepending "file:/" to "/somedir/somefile", i.e. 
"somedir" was seen as a host name.  I think you need to ensure there is one 
slash or three to avoid inadvertently specifying a host name.

Larry

> -Original Message-
> From: Filip Hanik - Dev Lists [mailto:devli...@hanik.com]
> Sent: Thursday, September 03, 2009 5:52 PM
> To: Tomcat Developers List
> Subject: Re: svn commit: r810132 - /tomcat/tc6.0.x/trunk/STATUS.txt
>
> The URL has to start with "file://"
>
> So the VirtualWebappLoader, can take a regular file path, and should
> simply prepend file://, not file: or file:/
>
> Filip
>
> On 09/01/2009 12:48 PM, Larry Isaacs wrote:
> > Hi Filip,
> >
> > I have a vague recollection about tripping over this issue while
> working on the Tomcat support in the Eclipse Web Tools Platform.  WTP
> has its own version(s) of VirtualWebappLoader, called WtpWebappLoader,
> to address it.  If I'm recalling the issue correctly, pre-pending
> "file:/" worked on Windows, but not on Linux since an absolute path
> ended up as "file://somedir/...".  I believe with the change below,
> pre-pending "file://" will work for Linux, but not for Windows, i.e.
> "file://C:/somedir/..." is going to have problems.  If it helps, I went
> with the URL form "file:/somedir/..." and used the following code
> snippet to get it working for Windows and Linux in WtpWebappLoader:
> >
> >
> >  String path = file.getAbsolutePath();
> >  if (path.startsWith("/")) {
> >  path = "file:" + path;
> >  } else {
> >  path = "file:/" + path;
> >  }
> >  if (file.isDirectory()) {
> >  addRepository(path + "/");
> >  } else {
> >  addRepository(path);
> >  }
> >
> > Cheers,
> > Larry
> >
> >
> >
> >> -Original Message-
> >> From: fha...@apache.org [mailto:fha...@apache.org]
> >> Sent: Tuesday, September 01, 2009 1:22 PM
> >> To: dev@tomcat.apache.org
> >> Subject: svn commit: r810132 - /tomcat/tc6.0.x/trunk/STATUS.txt
> >>
> >> Author: fhanik
> >> Date: Tue Sep  1 17:21:59 2009
> >> New Revision: 810132
> >>
> >> URL: http://svn.apache.org/viewvc?rev=810132&view=rev
> >> Log:
> >> proposal
> >>
> >> Modified:
> >>  tomcat/tc6.0.x/trunk/STATUS.txt
> >>
> >> Modified: tomcat/tc6.0.x/trunk/STATUS.txt
> >> URL:
> >>
> http://svn.apache.org/viewvc/tomcat/tc6.0.x/trunk/STATUS.txt?rev=810132
> >> &r1=810131&r2=810132&view=diff
> >>
> ===
> >> ===
> >> --- tomcat/tc6.0.x/trunk/STATUS.txt (original)
> >> +++ tomcat/tc6.0.x/trunk/STATUS.txt Tue Sep  1 17:21:59 2009
> >> @@ -321,3 +321,25 @@
> >> +1: funkman
> >> -1:
> >>
> >> +
> >> +* Fix VirtualWebappClassLoader file directives
> >> +  Index: java/org/apache/catalina/loader/VirtualWebappLoader.java
> >> +===
> >> +--- java/org/apache/catalina/loader/VirtualWebappLoader.java
> >>(revision 810099)
> >>  java/org/apache/catalina/loader/VirtualWebappLoader.java
> >>(working copy)
> >> +@@ -92,9 +92,9 @@
> >> + continue;
> >> + }
> >> + if (file.isDirectory()) {
> >> +-addRepository("file:/" + file.getAbsolutePath() +
> >> "/");
> >> ++addRepository("file://" + file.getAbsolutePath() +
> >> "/");
> >> + } else {
> >> +-addRepository("file:/" + file.getAbsolutePath());
> >> ++addRepository("file://" + file.getAbsolutePath());
> >> + }
> >> + }
> >> +
> >> +  +1: fhanik
> >> +  -1:
> >> +
> >> +
> >>
> >>
> >>
> >> 
> -
> >> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> >> For additional commands, e-mail: dev-h...@tomcat.apache.org
> >>
> >>
> >
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: dev-h...@tomcat.apache.org
>

RE: svn commit: r810132 - /tomcat/tc6.0.x/trunk/STATUS.txt

[Larry Isaacs]

I haven't run into any cases in Java where "file:/C:/somedir/somefile" didn't 
also work for Windows, though it may not be fully spec compliant.  This form 
has been working for a while for WtpWebappLoader.

Larry

> -Original Message-
> From: Filip Hanik - Dev Lists [mailto:devli...@hanik.com]
> Sent: Friday, September 04, 2009 11:27 AM
> To: Tomcat Developers List
> Subject: Re: svn commit: r810132 - /tomcat/tc6.0.x/trunk/STATUS.txt
>
> the URL for Unix would be file:///somedir/somefile
>
> Windows is always a pain in the butt, but I think you need
> file:///c:/somedir/somepath
>
> Filip
>
>
> On 09/04/2009 07:22 AM, Larry Isaacs wrote:
> > On Windows prepending "file://" to "C:\somedir\somefile" results in
> "file://C:/somedir/somefile".  I'm pretty sure URL will think "C" is
> the host name and fail if you try to use a URL object to read the file.
> I think it was the same issue on Linux when prepending "file:/" to
> "/somedir/somefile", i.e. "somedir" was seen as a host name.  I think
> you need to ensure there is one slash or three to avoid inadvertently
> specifying a host name.
> >
> > Larry
> >
> >
> >> -Original Message-
> >> From: Filip Hanik - Dev Lists [mailto:devli...@hanik.com]
> >> Sent: Thursday, September 03, 2009 5:52 PM
> >> To: Tomcat Developers List
> >> Subject: Re: svn commit: r810132 - /tomcat/tc6.0.x/trunk/STATUS.txt
> >>
> >> The URL has to start with "file://"
> >>
> >> So the VirtualWebappLoader, can take a regular file path, and should
> >> simply prepend file://, not file: or file:/
> >>
> >> Filip
> >>
> >> On 09/01/2009 12:48 PM, Larry Isaacs wrote:
> >>
> >>> Hi Filip,
> >>>
> >>> I have a vague recollection about tripping over this issue while
> >>>
> >> working on the Tomcat support in the Eclipse Web Tools Platform.
> WTP
> >> has its own version(s) of VirtualWebappLoader, called
> WtpWebappLoader,
> >> to address it.  If I'm recalling the issue correctly, pre-pending
> >> "file:/" worked on Windows, but not on Linux since an absolute path
> >> ended up as "file://somedir/...".  I believe with the change below,
> >> pre-pending "file://" will work for Linux, but not for Windows, i.e.
> >> "file://C:/somedir/..." is going to have problems.  If it helps, I
> went
> >> with the URL form "file:/somedir/..." and used the following code
> >> snippet to get it working for Windows and Linux in WtpWebappLoader:
> >>
> >>>
> >>>   String path = file.getAbsolutePath();
> >>>   if (path.startsWith("/")) {
> >>>   path = "file:" + path;
> >>>   } else {
> >>>   path = "file:/" + path;
> >>>   }
> >>>   if (file.isDirectory()) {
> >>>   addRepository(path + "/");
> >>>   } else {
> >>>   addRepository(path);
> >>>   }
> >>>
> >>> Cheers,
> >>> Larry
> >>>
> >>>
> >>>
> >>>
> >>>> -Original Message-
> >>>> From: fha...@apache.org [mailto:fha...@apache.org]
> >>>> Sent: Tuesday, September 01, 2009 1:22 PM
> >>>> To: dev@tomcat.apache.org
> >>>> Subject: svn commit: r810132 - /tomcat/tc6.0.x/trunk/STATUS.txt
> >>>>
> >>>> Author: fhanik
> >>>> Date: Tue Sep  1 17:21:59 2009
> >>>> New Revision: 810132
> >>>>
> >>>> URL: http://svn.apache.org/viewvc?rev=810132&view=rev
> >>>> Log:
> >>>> proposal
> >>>>
> >>>> Modified:
> >>>>   tomcat/tc6.0.x/trunk/STATUS.txt
> >>>>
> >>>> Modified: tomcat/tc6.0.x/trunk/STATUS.txt
> >>>> URL:
> >>>>
> >>>>
> >>
> http://svn.apache.org/viewvc/tomcat/tc6.0.x/trunk/STATUS.txt?rev=810132
> >>
> >>>> &r1=810131&r2=810132&view=diff
> >>>>
> >>>>
> >>
> ===
>

RE: svn commit: r609294 - in /tomcat/tc6.0.x/trunk: STATUS.txt conf/catalina.policy webapps/docs/changelog.xml

[Larry Isaacs]

> -Original Message-
> From: Remy Maucherat [mailto:[EMAIL PROTECTED]
> Sent: Thursday, January 10, 2008 5:39 PM
> To: Tomcat Developers List
> Subject: Re: svn commit: r609294 - in /tomcat/tc6.0.x/trunk: STATUS.txt
> conf/catalina.policy webapps/docs/changelog.xml
>
> On Thu, 2008-01-10 at 20:07 +, Mark Thomas wrote:
> > Remy Maucherat wrote:
> > >
> > > On my platform [Linux + IcedTea], with the new policy in place, I
> get an
> > > error initializing a timestamp used by the FileHandler (why such a
> class
> > > ends up using a file like this is a mystery):
> >
> > Can you turn on the debugging so we can figure out which file it is.
> I'd
> > rather add a specific permission, or at least a limited one, rather
> than a
> > default read permission for java_home and every file below it
> (assuming
> > that is where the file it is trying to read is located).
>
> I used java.security.debug=failure. The NPE isn't visible without it
> (and nothing gets logged). I also did try adding various file
> permissions, without much success.
>
> Rémy
>

If I recall correctly, the "failure" option unfortunately doesn't do
anything by itself.  I believe you have to have "access" enabled before
it will include any failures, i.e "java.security.debug=access,failure".
There's no avoiding the huge log file. :(

Cheers,
Larry

>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [PROPOSAL] Announce 3.x is no longer supported

[Larry Isaacs]

I'm fine with either approach as well.

Larry

> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
> Yoav Shapira
> Sent: Friday, February 15, 2008 8:10 AM
> To: Tomcat Developers List
> Subject: Re: [PROPOSAL] Announce 3.x is no longer supported
>
> On Thu, Feb 14, 2008 at 10:23 PM, Bill Barker <[EMAIL PROTECTED]>
> wrote:
> >  Well, the way Apache is structured, it is impossible to say that 3.x
> is no
> >  longer supported.  If three PMC members were to show an interest in
> >  expanding it in the future (say myself, Costin, Henri), then the
> rest would
> >  have a hard time blocking commits to that branch ;).  I would go for
> >  something like "The 3.x.x line is unlikely to have another release",
> instead
> >  of "not supported" as a result.  Especially since I plan to answer
> the
> >  occational 3.3 question on [EMAIL PROTECTED]
>
> I would have no problem with this approach either.  +1 to that as well
> ;)  Slightly gentler warning.
>
> Yoav
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Re: Tomcat 3.2.x problem with MS-DOS device names

[Larry Isaacs]

> -Original Message-
> From: Mamatha Rao (mamtarao) [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, February 20, 2008 7:15 AM
> To: Tomcat Developers List
> Subject: RE: Re: Tomcat 3.2.x problem with MS-DOS device names
>
> Thanks Bill. I found the details of the bug fix:
>
> Bug Fix - http://marc.info/?l=tomcat-dev&m=101055775717102&w=2
> Related email - http://marc.info/?l=tomcat-dev&m=101055563114160&w=2
> http://marc.info/?l=tomcat-dev&m=117236875932374&w=2 states Affected
> versions to be  3.0, 3.1-3.1.1, 3.2-3.2.4, 3.3
>
> But I find JavaGeneratorTool.java file(where I believe the fix was
> made)
> does not exist before 3.3.X.
>
> Not sure if there is a Windows / JRE version implication in reproducing
> the bug. I even tried with JRE 1.3.0_01. We still get a 404 and Tomcat
> doesn't seem to hang.
>
> Please let me know if anyone knows the conditions under which the bug
> is
> reproducible.

You might try using Windows 95. :)  It's been too long for me to remember
exactly what was in use at the time.  It's certainly conceivable that
the OS and Java runtime have gotten smarter about recognizing that trying
to read "aux.jsp" is not an attempt to access the "aux" device.  Your
stacktrace seems to suggest this improvement has been implemented.  Like
Bill said, if the request doesn't hang the thread (waiting for the device
to provide data), you don't have this vulnerability.

Cheers,
Larry

>
> Our product uses Tomcat 3.2 and since all external documentation
> indicate the bug is present in Tomcat versions prior to 3.3.1a, we
> don't
> have any official documentation to state the bug is not really there.
>
> Regards,
> Mamatha
>
> -Original Message-
> From: news [mailto:[EMAIL PROTECTED] On Behalf Of Bill Barker
> Sent: Wednesday, February 20, 2008 1:52 PM
> To: dev@tomcat.apache.org
> Subject: Re: Tomcat 3.2.x problem with MS-DOS device names
>
> I seem to recall that this was fixed in 3.2.4, but I can't be sure
> since
> I mostly passed over those commit messages at the time.  It was the
> reason to produce 3.3.1a, so is also fixed in 3.3.2 (easier upgrade
> path).  However, it hangs connections pretty consistantly on affected
> systems, so if you get a 404 (what I would expect from TC5+), then the
> bug isn't really there.
>
> "Mamatha Rao (mamtarao)" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]
> 417.apac.cisco.com
> ...
> Hi,
>
> Our application used Tomcat 3.2 and Nessus scan reported the following
> CVE against it
> http://nvd.nist.gov/nvd.cfm?cvename=CVE-2003-0045
> http://nvd.nist.gov/nvd.cfm?cvename=CVE-2003-0045>
>
> Tomcat release notes suggest fixing defect in 3.3.1a and later. We
> moved
> to Tomcat 5.5 and still saw Nessus reporting the same vulnerability.
> The
> Nessus scan may not be accurate since we ensured that Tomcat did not
> actually freeze after the attack.
>
> However, we are now stuck in verifying the vulnerability existed in
> Tomcat 3.2. Have tried testing with a sample servlet - it returns a 404
> Not Found error on requests like http://[ip http://[ip/>
> addr]:8080/test/aux.jsp. Traces show something like
> java.io.IOException: Bad pathname
> at java.io.WinNTFileSystem.canonicalize0(Native Method)
> at
> java.io.Win32FileSystem.canonicalize(Win32FileSystem.java:354)
> at java.io.File.getCanonicalPath(File.java:513)
> at org.apache.tomcat.util.FileUtil.safePath(FileUtil.java:184)
> at org.apache.tomcat.core.Context.getRealPath(Context.java:797)
> at
> org.apache.tomcat.facade.ServletContextFacade.getRealPath(ServletCont
> extFacade.java:136)
> at
> org.apache.jasper.JspEngineContext.getRealPath(JspEngineContext.java:
> 359)
> 
> 2008-02-19 10:18:05 - Ctx( /test ): 404 R( /test + /aux.jsp + null) JSP
> file not  found
> 2008-02-19 10:18:05 - Ctx( /test ): Handler
> tomcat.notFoundHandler(null/null) to
> mcat.notFoundHandler
>
> on such requests. And even with limiting the number of threads, Tomcat
> does not freeze. And thread dumps dont indicate anything wrong.
>
> Have tried it both on Windows 2000 server and Windows XP. Is there any
> dependency on Windows versions?
> http://nvd.nist.gov/nvd.cfm?cvename=CVE-2003-0045
> http://nvd.nist.gov/nvd.cfm?cvename=CVE-2003-0045>  seems to
> suggest it occurs in certain Windows systems while
> http://xforce.iss.net/xforce/xfdb/12102
> http://xforce.iss.net/xforce/xfdb/12102>  says it occurs in
> all versions of Windows.
>
> http://marc.info/?l=tomcat-dev&m=101055029706766&w=2
>   - This mail
> thread is refering to some similar/same(?) bug and suggests even
> Windows
> NT, 2000 have a problem but may be Tomcat 3.2.4 doesnt show the
> problem.
>
> Does anyone remember if this vulnerability can be triggered in Tomcat
> 3.2 and how? Any pointers to the bug fix in subversion would also help.
>
> Regards
> Mamatha
>
>
>
>
> -
> To u

RE: DO NOT REPLY [Bug 46293] New: Bean property getter not found when using EL expression

[Larry Isaacs]

It has been a long time, but I believe the bean property naming convention is 
that if the second letter is capitalized, the first letter should be 
capitalized too, avoiding property names like "uRL".  If you really want 
"xKey", you can provide a MyBeanBeanInfo class to go with MyBean to specify 
what you want.  For more details, see the JavaBeans API.

Cheers,
Larry

-Original Message-
From: Karl R. San Gabriel [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 26, 2008 10:13 AM
To: Tomcat Developers List
Subject: Re: DO NOT REPLY [Bug 46293] New: Bean property getter not found when 
using EL expression

[EMAIL PROTECTED] wrote:
> https://issues.apache.org/bugzilla/show_bug.cgi?id=46293
>
>Summary: Bean property getter not found when using EL expression
>Product: Tomcat 6
>Version: 6.0.18
>   Platform: PC
> OS/Version: Windows Vista
> Status: NEW
>   Severity: regression
>   Priority: P2
>  Component: Jasper
> AssignedTo: dev@tomcat.apache.org
> ReportedBy: [EMAIL PROTECTED]
>
>
> The EL expression ${myBean.xKey} does not yield a call to myBean.getXKey().
> However, ${myBean.XKey} does.
>
>
>
Dear All,

I was investigating this bug last night (Philippine time) and found out
something interesting which left me bewildered.
I was trying to come up with a proposed fix. :-)

I have the ff files:

a) testpckg.MyBean.java

package testpckg;
public class MyBean {
private String xKey = "xKey in the house";
private String name = "name in the house";

public String getXKey() { return xKey;}
public String getName() { return name; }
public void setXKey(String xKey) { this.xKey = xKey;}
public void setName(String name) { this.name = name;}
}

b) index.jsp

   
   ${test.xKey}


In javax.el.BeanELResolver.java, BeanInfo.getPropertyDescriptors() is
giving the ff:

pds[0].getName(): XKey
pds[1].getName(): class
pds[2].getName(): name


That BeanInfo.getPropertyDescriptors() call is in :

protected final static class BeanProperties {
private final Map properties;

private final Class type;

public BeanProperties(Class type) throws ELException {
this.type = type;
this.properties = new HashMap();
try {
BeanInfo info = Introspector.getBeanInfo(this.type);
PropertyDescriptor[] pds = info.getPropertyDescriptors();
for (int i = 0; i < pds.length; i++) {
this.properties.put(pds[i].getName(), new BeanProperty(
type, pds[i]));
}
} catch (IntrospectionException ie) {
throw new ELException(ie);
}
}


It looks like Java is taking XKey from getXKey().
I could make the code convert the first character of the property to
lowercase but I not sure about that.

My settings:
TC6.0.18
Java 1.5

Regards,
Karl



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Tomcat 8.next

[Larry Isaacs]

FYI: Support for Tomcat 9.0 was added to WTP 3.8 for Eclipse Neon last weekend.

I can add 8.5 support, but it would be best if it could be added in March or 
April.  If it's delayed beyond that, it might have to move to the first 
maintenance release that comes out in late September.  I'll try to keep an eye 
on this.

Cheers,
Larry

-Original Message-
From: Rémy Maucherat [mailto:r...@apache.org] 
Sent: Wed, March 02, 2016 8:43 AM
To: Tomcat Developers List 
Subject: Re: Tomcat 8.next

2016-03-02 13:15 GMT+01:00 Konstantin Kolinko :

> 2016-03-02 1:12 GMT+03:00 Mark Thomas :
> > To summarise where I think this discussion is going:
> >
> > - Create 8.5.x from 9.0.x with the following changes
> >   - revert all changes to spec APIs
> >   - make any necessary changes to work with Java 7
> >
> > - Release 8.0.x and 8.5.x in parallel for ~6 months then stop 8.0.x
> >   releases
> >
> > - If users report problems caused by removal of a deprecated API in
> >   8.5.x, restore it.
> >
> > Did I miss anything? Any additional concerns to address?
>
> The plan looks good.
>
> Concerns:
> 1. Eclipse IDE has 1 year cycle of major releases. If we go in March, 
> I think we have chances to have 8.5 support in next major release this 
> summer. (Provided that somebody does an effort to actually implement 
> it, as with any volunteer work).
>
> I think that 6 months are counted from first stable release, not from 
> 8.5.alpha.
>
> This time interval of 6 months sounds right for major adoption, but as 
> we have always provided a 1 year advance notice of EOL I think we 
> should be ready to provide security fixes and such for 1 year. These 
> releases should not be monthly (as with current 8.0), but occasional 
> ones. E.g. once in 3-6 months.
>

The "base" 6 months after a stable release seems ok to me. Hoepfully the road 
to stable isn't too long though.

>
>
> 2. The feature of auto-switching sslImplementationName with 
> availability of TCNative library needs better documentation. I suspect 
> that it may come as a surprise.
>
> There is documentation of sslImplementationName attribute on 
> config/http.html, but the attribute of AprLifecycleListener
> (useAprConnector) is not documented at all.
>

It is supposed to be documented as of r1729644. OTOH, I'm not that good with 
that kind of thing, and maybe it is still confusing.

Rémy

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org