This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 50736 - I18N - Context log cannot be opened when running in Japanese Environment
Summary: I18N - Context log cannot be opened when running in Japanese Environment
Status: RESOLVED WONTFIX
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Tomcat (show other bugs)
Version: 4.x
Hardware: Other All
: P3 blocker (vote)
Assignee: Sherold Dev
URL: http://issues.apache.org/bugzilla/sho...
Keywords: I18N, RELNOTE
Depends on:
Blocks:
 
Reported: 2004-10-22 12:40 UTC by Sherold Dev
Modified: 2004-10-26 10:07 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sherold Dev 2004-10-22 12:40:33 UTC
Context log cannot be opened when running in 
Japanese Environment due to the bug in Japanese 
localization of Tomcat Manager application (see 
http://issues.apache.org/bugzilla/show_bug.cgi?id=31732). 
 
Workaround: use shared context log instead of 
context log. It can be done by removing the 
"Logger" element from the web application's 
META-INF/context.xml file. If the web 
application does not have its own logger 
defined, every message or exception goes into 
the share context log.
Comment 1 Sherold Dev 2004-10-22 12:43:11 UTC
Setting target milestone to prome-E. 
Comment 2 Ken Frank 2004-10-22 17:33:37 UTC
I will ask for this to be release noted - is there a keyword that
indicates a bug should be release noted.

This is because, due to licensing issues, we should not either
remove the ja props file or do the one line fix.

ken.frank@sun.com
10/22/2004
Comment 3 Sherold Dev 2004-10-26 10:07:14 UTC
Setting to WONTFIX, since the issue in Tomcat Manager web 
application has been fixed. Note that the fix will be included in 
Tomcat 5.0.30 but not in the bundle Tomcat, since it is of version 
5.0.29. 
 
Release notes should suggest upgrading to Tomcat 5.0.30 as a 
recommended workaround for this issue.