Re: [VOTE] Kurt Miller as commiter

[jean-frederic clere]

Henri Gomez wrote:
Hi to all,

I would like to propose you a new tomcat commiter, Kurt Miller
which as proposed many usefull patches for JK2
Since we want to deprecated jk and focus jk2, we need
more people involved on jk2.
Vote please.
+1



-
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: [5.0] content-type and charset issues

[Remy Maucherat]

Bill Barker wrote:
Hi,

Tomcat 5.0 always adds a charset=ISO-8859-1 to the content type. While
this is I think relatively legal, it is rather risky (it causes problems
with some clients, as I've read on tomcat-user), and very dubious when
dealing with non text data.
Example:
GET /tomcat.gif HTTP/1.0
User-Agent: ApacheBench/1.3d
Host: 127.0.0.1
Accept: */*
HTTP/1.1 200 OK
ETag: W/"1934-1068549702000"
Last-Modified: Tue, 11 Nov 2003 11:21:42 GMT
Content-Type: image/gif;charset=ISO-8859-1
Content-Length: 1934
Date: Tue, 11 Nov 2003 14:59:56 GMT
Server: Apache-Coyote/1.1
Connection: close
(lol)

Maybe Jan's changes to charset handling caused that.
If charset is not explicitely added, I think it should not be added to
content-type either.
What about adding the charset only when contentType.startsWith("text")?  A
better choice would be when usingWriter is true, but that's not available
here.
Since Writer output is sent out as iso-latin-1 if the Servlet doen't set the
charset, I think that it would be better to add the charset to the header,
rather than trust that the browser's default encoding is compatible.
If the charset is iso-latin-1, then it will be displayed.

The startsWith could possibly be going too far, unless this is written 
in black and white in the HTTP spec (I didn't check).
I think my patch restored the previous behavior (and saved some object 
allocation in the general case). People seemed to be fine with it, 
unlike the new behavior (for which I've seen complaints on tomcat-user).

Remy



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

[5.0.15] New tag soon (probably)

[Remy Maucherat]

Hi,

As was discussed earlier, I'll put in a new tag when the final 
specifications are available.

There may not be a need for a new beta release since:
- 5.0.14 has been rather successful
- an extra beta testing month has been added
- the CVS code has been rather stable for a while
Of course, this will be up to the vote results :)
Rémy



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

Tag files not pooling

[jakarta]

Is tomcat 5 going to suport tag file pooling as well as tag pooling.
When looking at some generated code I notice that it was currently only
pooling tags not tag files?

Thanks,

john


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

Re: Tag files not pooling

[Ryan Lubke]

The JSP 2.0 specification states that these must not be cached.

See section 7.1.5.



On Wed, 2003-11-12 at 10:48, jakarta wrote:
> Is tomcat 5 going to suport tag file pooling as well as tag pooling.
> When looking at some generated code I notice that it was currently only
> pooling tags not tag files?
> 
> Thanks,
> 
> john
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
-- 
Ryan Lubke <[EMAIL PROTECTED]>
Sun Microsystems, Inc.


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

Re: Why is mod_jk distributed both as 2.0.2 and 2.0.4?

[Henri Gomez]

Kurt Miller a écrit :

From: "Glenn Nielsen" <[EMAIL PROTECTED]>

Perhaps the mod_jk connector should not be released with Tomcat 4/5 since
it

has its own release cycle and we are already doing separate releases of
these.
Regards,

Glenn



Would this work...

When a stable version of mod_jk or mod_jk2 is released put the stable jar
files in the
jakarta/tomcat-connectors/jk(2)/binaries/ directories. Then have Tomcat 4/5
use the released stable jars instead of building them.
If this works, then it may also serve as a way for users to upgrade both the
native and the java side when a new jk/jk2 release is made.
I think that we should decouple jk/jk2 release from tomcat3/4/5 release, 
in some case jk 1.2.x add a faster release rate that tomcats :)



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

DO NOT REPLY [Bug 24650] - name class of bean when throwing java.lang.NoSuchMethodException

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24650

name class of bean when throwing java.lang.NoSuchMethodException

[EMAIL PROTECTED] changed:

   What|Removed |Added

 AssignedTo|struts- |tomcat-
   |[EMAIL PROTECTED]  |[EMAIL PROTECTED]

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

Need Consulting

[Jeff Rogers]

Hello,

I hate to post this to the dev list, but we need consulting help.  I 
have no idea where to look for reputable Tomcat consulting.

We are at our wits end and ready to make the jump to commercial 
software due to a "signal 11" crashing problem with our Tomcat servers. 
 We have found about a zillion similar issues on the lists, but no 
solutions.

We are in the Northeastern part of the US.  Please reply offline to 
keep this off the dev list.

Thanks

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

DO NOT REPLY [Bug 24655] New: - Binary distribution shortens filenames

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24655

Binary distribution shortens filenames

   Summary: Binary distribution shortens filenames
   Product: Tomcat 4
   Version: 4.1.29
  Platform: HP
OS/Version: HP-UX
Status: NEW
  Severity: Major
  Priority: Other
 Component: Webapps:Administration
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


The binary distribution jakarta-tomcat-1.29.tar.gz could not installed 
correctly.
After unpacking with gzip and untarring with "tar xf jakarta..." some 
filenames are cut of in the directory structure. (e.g. ValueForm.c instead of 
ValueForm.class)

This prevents a successful start of the admin application.

I'm not sure if this is a problem of the distribution itself, or of the tar on 
my system. (HP-UX 11i)

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

DO NOT REPLY [Bug 24655] - Binary distribution shortens filenames

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24655

Binary distribution shortens filenames





--- Additional Comments From [EMAIL PROTECTED]  2003-11-12 18:31 ---
Be sure you are using a version of tar that supports long file names in
tarballs.  GNU tar is recommended.  Sadly, many OS-vendor versions do no support
this.

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

Re: Why is mod_jk distributed both as 2.0.2 and 2.0.4?

[Kurt Miller]

From: "Henri Gomez" <[EMAIL PROTECTED]>
> Kurt Miller a écrit :
>
> > From: "Glenn Nielsen" <[EMAIL PROTECTED]>
> >
> >>Perhaps the mod_jk connector should not be released with Tomcat 4/5
since
> >
> > it
> >
> >>has its own release cycle and we are already doing separate releases of
> >>these.
> >>
> >>Regards,
> >>
> >>Glenn
> >>
> >
> >
> > Would this work...
> >
> > When a stable version of mod_jk or mod_jk2 is released put the stable
jar
> > files in the
> > jakarta/tomcat-connectors/jk(2)/binaries/ directories. Then have Tomcat
4/5
> > use the released stable jars instead of building them.
> >
> > If this works, then it may also serve as a way for users to upgrade both
the
> > native and the java side when a new jk/jk2 release is made.
>
> I think that we should decouple jk/jk2 release from tomcat3/4/5 release,
> in some case jk 1.2.x add a faster release rate that tomcats :)
>

I guess the simplest solution is to exclude the following directories from
the jakarta-tomcat-connectors-4.X-src archives to avoid confusion:

jk/native
jk/native2
webapp/apache-1.3
webapp/apache-2.0
webapp/lib
webapp/support
webapp/include


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

DO NOT REPLY [Bug 24655] - Binary distribution shortens filenames

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24655

Binary distribution shortens filenames

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||INVALID



--- Additional Comments From [EMAIL PROTECTED]  2003-11-12 18:33 ---
The tar from HP is not GNU tar. YOu need GNU's tar.

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

JK2 workers.properties

[Andy Armstrong]

Does anyone know what the contents of workers.properties should look 
like for JK2? I'm producing a new version of the Domino redirector based 
on the ISAPI one but I can't find a sample workers.properties for the 
ISAPI filter.

From stepping through the filter's initialisation code it's clear that 
the property names that appear in the file need to be the names of jk2 
beans so I know what the vocabulary is but I'd rather not have to do 
enough reverse engineering to work out what kind of values the 
properties should have :)

--
Andy Armstrong, Tagish


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

Re: JK2 workers.properties

[Andy Armstrong]

Andy Armstrong wrote:

Does anyone know what the contents of workers.properties should look 
like for JK2? I'm producing a new version of the Domino redirector based 
on the ISAPI one but I can't find a sample workers.properties for the 
ISAPI filter.

 From stepping through the filter's initialisation code it's clear that 
the property names that appear in the file need to be the names of jk2 
beans so I know what the vocabulary is but I'd rather not have to do 
enough reverse engineering to work out what kind of values the 
properties should have :)
Scratch that - I just found an example. You wouldn't believe that I've 
been trying to figure it out all day. Doh!

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

Re: Why is mod_jk distributed both as 2.0.2 and 2.0.4?

[Glenn Nielsen]

Kurt Miller wrote:
From: "Henri Gomez" <[EMAIL PROTECTED]>

Kurt Miller a écrit :


From: "Glenn Nielsen" <[EMAIL PROTECTED]>

Perhaps the mod_jk connector should not be released with Tomcat 4/5

since

it


has its own release cycle and we are already doing separate releases of
these.
Regards,

Glenn



Would this work...

When a stable version of mod_jk or mod_jk2 is released put the stable

jar

files in the
jakarta/tomcat-connectors/jk(2)/binaries/ directories. Then have Tomcat

4/5

use the released stable jars instead of building them.

If this works, then it may also serve as a way for users to upgrade both

the

native and the java side when a new jk/jk2 release is made.
I think that we should decouple jk/jk2 release from tomcat3/4/5 release,
in some case jk 1.2.x add a faster release rate that tomcats :)


I guess the simplest solution is to exclude the following directories from
the jakarta-tomcat-connectors-4.X-src archives to avoid confusion:
jk/native
jk/native2
webapp/apache-1.3
webapp/apache-2.0
webapp/lib
webapp/support
webapp/include
Another way to look at this is, what things out of j-t-c need to have
a source release along with a Tomct 3/4/5 release?  Remy?
coyote, http11, and util, anything else?

Would we then need to provide jars and source for the AJP connector side
of things in our mod_jk releases?
Regards,

Glenn

--
Glenn Nielsen [EMAIL PROTECTED] | /* Spelin donut madder|
MOREnet System Programming   |  * if iz ina coment.  |
Missouri Research and Education Network  |  */   |
--
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 24660] New: - Corrupted installation binary

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24660

Corrupted installation binary

   Summary: Corrupted installation binary
   Product: Tomcat 4
   Version: 4.1.29
  Platform: PC
OS/Version: Windows NT/2K
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Installable Packages
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


The installation terminates because of an corrupted file in the binary.
File: jakarta-tomcat-4.1.29.exe
MD5:  4584D81100CCEB0CE88F1662E8FBC370

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

DO NOT REPLY [Bug 24660] - Corrupted installation binary

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24660

Corrupted installation binary

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||INVALID



--- Additional Comments From [EMAIL PROTECTED]  2003-11-12 21:25 ---
Irritating installation message, if the drive with the temporary folder for the 
installationfiles hasn't enough space to hold all of the unpacked files.
There's no warning that there's not enough space to unpack, but gives a 
messagebox that the installationfile may be corrupted.
Maybe a problem of the Nullsoft Install System?
Sorry!

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

Re: [5.0] content-type and charset issues

[Kazuhiro Kazama]

Remy,

From: Remy Maucherat <[EMAIL PROTECTED]>
Subject: [5.0] content-type and charset issues
Date: Tue, 11 Nov 2003 16:10:24 +0100
Message-ID: <[EMAIL PROTECTED]>
> Tomcat 5.0 always adds a charset=ISO-8859-1 to the content type. While 
> this is I think relatively legal, it is rather risky (it causes problems 
> with some clients, as I've read on tomcat-user), and very dubious when 
> dealing with non text data.

I received the report that the same(?) charset problem exists in
Tomcat 4.1.29 from Japanese developers. They said that Tomcat 4.1.27
is ok.

Could you check whether the same problem exists or not?

If not, I will analyze Tomcat 4.1.29 and send the patch.

Kazuhiro Kazama ([EMAIL PROTECTED]) NTT Network Innovation Laboratories


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