DO NOT REPLY [Bug 25065] New: - Java and Jakarta Tomcat on FreeBSD

[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=25065

Java and Jakarta Tomcat on FreeBSD

   Summary: Java and Jakarta Tomcat on FreeBSD
   Product: Tomcat 4
   Version: 4.0 Beta 1
  Platform: Other
   URL: http://www.FreeBSD.org/doc/en/articles/java-tomcat
OS/Version: FreeBSD
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Unknown
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


It would be highly appreciated, if one of the Tomcat WWW maintainers
can add the said article (from the URL) to the Tomcat project site.
I am unsure as to where it fits best, but hopefully, there is a place.

The article will be updated soon, to note the new features about
Tomcat v.5, and also describe the installation details.

Thanking in anticipation.

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

DO NOT REPLY [Bug 24970] - charset appended to content-type even if not text/*

[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=24970

charset appended to content-type even if not text/*





--- Additional Comments From [EMAIL PROTECTED]  2003-11-28 10:49 ---
I've some download problems with the attachment. Can you please provide the 
patch again or mail it to me directly?

Thanks!

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

DO NOT REPLY [Bug 25066] New: - Add flag to disable context at startup

[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=25066

Add flag to disable context at startup

   Summary: Add flag to disable context at startup
   Product: Tomcat 5
   Version: 5.0.15
  Platform: All
OS/Version: All
Status: NEW
  Severity: Enhancement
  Priority: Other
 Component: Catalina
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


How about adding an on/off flag for the context. Provided there's one it would
be possible to prevent starting a context during startup, but would allow
starting this context later. This is especially a case for bundled applications
admin, manager and balancer. 

The corresponding  element might look like this:




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

DO NOT REPLY [Bug 25010] - Symbolic links should be supported through

[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=25010

Symbolic links should be supported through 

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|INVALID |



--- Additional Comments From [EMAIL PROTECTED]  2003-11-28 12:26 ---
I have found something to this respect in
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25010

Appearently, this bug, which I have reported for 5.0.14,
has been fixed in the present development.

So, there is a small bookkeeping error here:
This bug should have been RESOLVED/FIXED, but presently is RESOLVED/INVALID.

I will reopen it to be able to correct this bookkeeping error.

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

DO NOT REPLY [Bug 25010] - Symbolic links should be supported through

[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=25010

Symbolic links should be supported through 

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution||FIXED

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

Jakarta Tomcat on FreeBSD (Doc)

[Hiten Pandya]

Hi,

Just FYI, if one of the Tomcat web maintainers have
got
some time, it would be highly appreciated if the
"Java and Jakarta Tomcat on FreeBSD" article is linked
somewhere on the project site.

The article resides at:
http://www.freebsd.org/doc/en/articles/java-tomcat/

The article will be updated soon, but it the
instructions do apply for most installations.

As the name says, it describes the installation
process
for Java and Tomcat.  I do not know where it fits the
best on the project site, but I am sure the site
maintainers can find a suitable place for it. :-)

PS. Mail me directly, as I am currently not subscribed
to the list.

Regards,

Hiten Pandya
[EMAIL PROTECTED], [EMAIL PROTECTED]


Download Yahoo! Messenger now for a chance to win Live At Knebworth DVDs
http://www.yahoo.co.uk/robbiewilliams

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

Error in composeName() implementations

[Phil Steitz]

I have been working on commons-naming (extracted from catalina's 
org.apache.naming, soon to be moved to incubator-directory) and I have 
discovered a (apparently harmless to tomcat) bug in the composeName() 
implementation that is repeated in o.a.n.NamingContext, 
o.a.n.SelectorContext, o.a.n.resources.BaseDirContext, and 
o.a.n.r.ProxyDirContext.

All of these classes include:

 public Name composeName(Name name, Name prefix)
throws NamingException {
prefix = (Name) name.clone();
return prefix.addAll(name);
}
This ignores the prefix and composes the name with itself.  A grep on 
tomcat-4.0 and tomcat-catalina for 'composeName(' turns up nothing but the 
method declarations, so I assume that these methods are not used (at least 
directly) by tomcat.

Should I submit a patch to fix this?  If yes, should I submit it against 
jakarta-tomcat-catalina?  The fix that I have in mind is to replace the 
body with:

Name result = (Name) prefix.clone();
return result.addAll(name);
As we add more tests, we may find other things like this. Should we try to 
replicate the patches, or hold off until the incubator-directory-naming 
component is ready for a release and possible re-integration into tomcat?

Phil



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

DO NOT REPLY [Bug 25078] New: - Catalina Ant Serverinfo task always fails

[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=25078

Catalina Ant Serverinfo task always fails

   Summary: Catalina Ant Serverinfo task always fails
   Product: Tomcat 5
   Version: 5.0.14
  Platform: Other
OS/Version: Other
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Webapps:Manager
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


Tomcat version: 5.0.14
Ant version   : 1.6beta2

I'm getting output from the Serverinfo task, but it always ends failure.  Here's
what I see...

catalina-serverinfo:
[catalina-serverinfo] Tomcat Version: Apache Tomcat/5.0.14
[catalina-serverinfo] OS Name: Windows XP
[catalina-serverinfo] OS Version: 5.1
[catalina-serverinfo] OS Architecture: x86
[catalina-serverinfo] JVM Version: 1.4.2_01-b06
[catalina-serverinfo] JVM Vendor: Sun Microsystems Inc.


BUILD FAILED
D:\myclasses\Repository\TheHartford\Sandbox\NBS2\catalina-targets.incl:162: Tomc
at Version: Apache Tomcat/5.0.14


The thing is it looks like most, if not all, the information is being printed,
but something is causing it to end in failure.  Maybe something in Ant-1.6 broke
this?  Haven't tested it in 1.5.x as my build uses features only available in
1.6.  Either way, there is no reason it shouldn't work under both Ant versions.

Jake

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