DO NOT REPLY [Bug 24846] - Quantity of org.apache.jasper.runtime.JspRuntimeLibrary.* usage triggers javac bug

2003-11-20 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=24846.
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=24846

Quantity of org.apache.jasper.runtime.JspRuntimeLibrary.* usage triggers javac bug

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||WONTFIX



--- Additional Comments From [EMAIL PROTECTED]  2003-11-20 09:47 ---
This will not be fixed (as you said, it is not a Jasper issue, and I'm almost
certain the spec mandates no imports outside of a small list). Besides, there is
a significant amount of other compilers which can be used by Ant, so this
shouldn't be a real issue.
You should precompile your application, BTW.

About the last sentence, Tomcat is not completely reliable for large JSP files
anyway (no compliant JSP compiler can be, AFAIK), because of Java limitations to
method code size.
There may also be an easy workaround: disable tag pooling.

We'll refer to your big report for further comments if needed, and to mark
others as duplicates.

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



DO NOT REPLY [Bug 24846] - Quantity of org.apache.jasper.runtime.JspRuntimeLibrary.* usage triggers javac bug

2003-11-20 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=24846.
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=24846

Quantity of org.apache.jasper.runtime.JspRuntimeLibrary.* usage triggers javac bug





--- Additional Comments From [EMAIL PROTECTED]  2003-11-20 15:31 ---
Thanks for the ernest reply Remmy.

I can understand your position -- and it makes sense from a spec compliance and
let's not do further hacks to workaround javac perspective.

I guess I'll just be patching my own Tomcat with every upgrade (as I do with
every Apache upgrade anyway).

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



DO NOT REPLY [Bug 24846] - Quantity of org.apache.jasper.runtime.JspRuntimeLibrary.* usage triggers javac bug

2003-11-20 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=24846.
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=24846

Quantity of org.apache.jasper.runtime.JspRuntimeLibrary.* usage triggers javac bug





--- Additional Comments From [EMAIL PROTECTED]  2003-11-20 15:37 ---
There are, IMO, much better solutions: you could for example use Eclipse Java
compiler (called EDT, I think) instead (Ant supports it, so Jasper does too). It
seems way faster than javac, without any disadvantages.

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



DO NOT REPLY [Bug 24846] - Quantity of org.apache.jasper.runtime.JspRuntimeLibrary.* usage triggers javac bug

2003-11-20 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=24846.
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=24846

Quantity of org.apache.jasper.runtime.JspRuntimeLibrary.* usage triggers javac bug





--- Additional Comments From [EMAIL PROTECTED]  2003-11-20 15:44 ---
Are there any non-native (i.e. Java-based) compilers that I can distribute
freely, will work on Windows, Solaris, HPUX, AIX, and Linux and are as
1.4.x-compatible as javac, yet have fewer compiler bugs?  Is the Eclipse
compiler such a beast?

Excuse me for my ignorance.  If javac is so bad in general, is the Tomcat group
distributing an alternative out-of-the-box?

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