DO NOT REPLY [Bug 31233] - jsp compile errors with Chinese Characters

2004-09-15 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=31233>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=31233

jsp compile errors with Chinese Characters

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||INVALID



--- Additional Comments From [EMAIL PROTECTED]  2004-09-15 16:18 ---
The is not productive at all. As I said: the syntax error does not occur for me.
So I will ignore this part of the report until I get a real test case.

As for the rest, since the generated source will very likely be the same (you
didn't compare, though), and the encoding is properly set on the compiler (you
can verify that in the compiler adapter source), the issue must rest with the
compiler itself. You have the option of using Ant as the compiler if JDT is the
issue (remove the JDT jar, and put ant.jar where the JDT jar was).

Supporting JDT is outside of Tomcat's scope, so I will resolve this report as
INVALID.

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

DO NOT REPLY [Bug 31233] - jsp compile errors with Chinese Characters

2004-09-15 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=31233>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=31233

jsp compile errors with Chinese Characters





--- Additional Comments From [EMAIL PROTECTED]  2004-09-15 16:15 ---
I tested the second jsp on three environment settings and got three different 
results(please see the attatched images):

1. on tomcat 5.0 with default jsp compiler setting: ok
2. on tomcat 5.5 with default jsp compiler setting: compile error
3. on tomcat 5.5 with javaEncoding set to ISO-8859-1: display incorrectly

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

DO NOT REPLY [Bug 31233] - jsp compile errors with Chinese Characters

2004-09-15 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=31233>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=31233

jsp compile errors with Chinese Characters





--- Additional Comments From [EMAIL PROTECTED]  2004-09-15 16:09 ---
Created an attachment (id=12744)
test jsp on tomcat 5.5 with javaEncoding set to ISO-8859-1

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

DO NOT REPLY [Bug 31233] - jsp compile errors with Chinese Characters

2004-09-15 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=31233>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=31233

jsp compile errors with Chinese Characters





--- Additional Comments From [EMAIL PROTECTED]  2004-09-15 16:08 ---
Created an attachment (id=12743)
test jsp on tomcat 5.5 with default javaEncoding

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

DO NOT REPLY [Bug 31233] - jsp compile errors with Chinese Characters

2004-09-15 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=31233>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=31233

jsp compile errors with Chinese Characters





--- Additional Comments From [EMAIL PROTECTED]  2004-09-15 16:06 ---
Created an attachment (id=12742)
test jsp on tomcat 5.0

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

DO NOT REPLY [Bug 31233] - jsp compile errors with Chinese Characters

2004-09-15 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=31233>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=31233

jsp compile errors with Chinese Characters





--- Additional Comments From [EMAIL PROTECTED]  2004-09-15 13:59 ---
I can't test the correctness of the characters right now, but I do not get any
compilation error with the second file. So this part of the report is bad.

Although I'm not the biggest expert in i18n, one of the pages seem wrong: it
does not include a page directive with the correct charset.

Last, you might want to try using the init-param of Jasper (in conf/web.xml) to
play with the encoding during the compilation.

javaEncoding
ISO-8859-1


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

DO NOT REPLY [Bug 31233] - jsp compile errors with Chinese Characters

2004-09-15 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=31233>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=31233

jsp compile errors with Chinese Characters





--- Additional Comments From [EMAIL PROTECTED]  2004-09-15 10:15 ---
Created an attachment (id=12739)
another jsp which will cause compile error

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

DO NOT REPLY [Bug 31233] - jsp compile errors with Chinese Characters

2004-09-14 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=31233>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=31233

jsp compile errors with Chinese Characters





--- Additional Comments From [EMAIL PROTECTED]  2004-09-15 06:50 ---
Created an attachment (id=12737)
a simple jsp which contains a few chinese chars with UTF8 encoded

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

DO NOT REPLY [Bug 31233] - jsp compile errors with Chinese Characters

2004-09-14 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=31233>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=31233

jsp compile errors with Chinese Characters





--- Additional Comments From [EMAIL PROTECTED]  2004-09-15 05:13 ---
Can you provide a test case ?

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

DO NOT REPLY [Bug 31233] New: - jsp compile errors with Chinese Characters

2004-09-14 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=31233>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=31233

jsp compile errors with Chinese Characters

   Summary: jsp compile errors with Chinese Characters
   Product: Tomcat 5
   Version: 5.5.1
  Platform: All
OS/Version: All
Status: NEW
  Severity: Major
  Priority: Other
 Component: Jasper
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


My jsp pages (which contains Chinese characters and encoded in UTF8) can be 
executed without any problems in Tomcat 4.1 and Tomcat 5.0. When I try to run 
these jsp pages in Tomcat 5.5, either it will result in compile errors or the 
Chinese characters can not be displayed correctly on the browser. Then I tried 
to replace jasper-compiler.jar and jasper-runtime.jar in Tomcat 5.5 with those 
in Tomcat 5.0 and all back to normal.

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

DO NOT REPLY [Bug 13956] - XSI Namespace Declaration Causing JSP Compile Errors

2004-08-22 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=13956>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=13956

XSI Namespace Declaration Causing JSP Compile Errors

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||FIXED



--- Additional Comments From [EMAIL PROTECTED]  2004-08-22 15:56 ---
This has been fixed in CVS for TC4.

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

Re: JSP Compile Errors

2002-10-27 Thread micael 
Write a simple Java program:

1. Drill down and get files.
2. Check for package statement, check for import statements.
3. If blah, blah, blah, then add import blah, blah.

I wrote a generic one that could be used whenever I needed to so something 
like that to lots of files, e.g. change the package name on all of 
them.  It is proprietary to the company I worked for, so I cannot put it in 
here.  But, they are really not hard to write.

At 05:24 PM 10/25/2002 -0400, you wrote:
> I need to make sure that these Java libraries are included when my JSP's
> are compiled:
>
> java.io.*
> java.util.*
>
> I am migrating from another application server that added these to my JSP's
> and now will have the daunting task of manually importing these on every
> JSP that we have.

1) What kind of app server would import those for you? You need to file a 
big, loud
bug report, cuz that violates the spec! Only java.lang is imported for 
free in Java.

2) Write a Shell or Perl script, or a Java program, or use vi. How many 
JSPs are you talking about anyway?



--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Micael

---

This electronic mail  transmission and any accompanying documents contain 
information belonging to the sender which may be confidential and legally 
privileged.  This information is intended only for the use of the 
individual or entity to whom this electronic mail transmission was sent as 
indicated above. If you are not the intended recipient, any disclosure, 
copying, distribution, or action taken in reliance on the contents of the 
information contained in this transmission is strictly prohibited.  If you 
have received this transmission in error, please delete the message.  Thank you 



--
To unsubscribe, e-mail:   
For additional commands, e-mail:

Re: JSP Compile Errors

2002-10-27 Thread Ian Darwin 
> I need to make sure that these Java libraries are included when my JSP's
> are compiled:
>
> java.io.*
> java.util.*
>
> I am migrating from another application server that added these to my JSP's
> and now will have the daunting task of manually importing these on every
> JSP that we have.

1) What kind of app server would import those for you? You need to file a big, loud
bug report, cuz that violates the spec! Only java.lang is imported for free in Java.

2) Write a Shell or Perl script, or a Java program, or use vi. How many JSPs are you 
talking about anyway?



--
To unsubscribe, e-mail:   
For additional commands, e-mail:

JSP Compile Errors

2002-10-25 Thread Dustin Brown 
Hello All.

I need to make sure that these Java libraries are included when my JSP's are
compiled:

java.io.*
java.util.*

I am migrating from another application server that added these to my JSP's
and now will have the daunting task of manually importing these on every JSP
that we have.

Any thoughts?

DO NOT REPLY [Bug 13956] New: - XSI Namespace Declaration Causing JSP Compile Errors

2002-10-24 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13956>.
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=13956

XSI Namespace Declaration Causing JSP Compile Errors

   Summary: XSI Namespace Declaration Causing JSP Compile Errors
   Product: Tomcat 4
   Version: 4.1.12
  Platform: PC
OS/Version: Windows XP
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Servlet & JSP API
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


I use XML Spy to create my xml-valid JSPs by providing sun's schema...XML Spy
produces a page similar to this:

http://jakarta.apache.org/taglibs/xtags-1.0"; 
xmlns:jsp="http://java.sun.com/JSP/Page";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://java.sun.com/JSP/Page
http://java.sun.com/dtd/jspxml.xsd";>


This, to the best of my knowledge is the correct way to declare a JSP.  I have
been using these pages since Tomcat 3.x (bundled with JBoss).  

When migrating these pages to Tomcat 4.1.12 I started receiving compile errors
for every page that contains:

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://java.sun.com/JSP/Page
http://java.sun.com/dtd/jspxml.xsd";>

The compile error is found at the end of my entry.  If I remove this entry the
page compiles just fine.  Are these invalid namespace declarations that Tomcat
was mistakingly allowing before or does the new compiler introduced in 4.1.x
have a bug?  I have a work-around for this problem (simply remove the
declarations), but I am concerned about other namespace entries that may cause a
problem.

Thanx,

Aaron Roller

org.apache.jasper.JasperException: Unable to compile class for JSP
at 
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:479)
at 
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:184)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:289)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:240)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:260)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at 
org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2396)
at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:469)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache