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=39089>.
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=39089





------- Additional Comments From [EMAIL PROTECTED]  2006-04-18 23:11 -------
(In reply to comment #4)
I didn't reopen this for the sake of re-opening it nor for the documentation 
fix...

JDT *does not* add the JSR-045 SourceDebugExtension - Jasper seems to. Please
see comment #3 that I added when I reopened this bug - the SourceDebugExtension
code is in Tomcat's SVN repository (see the link in #4). 

The Sun JVM issue is really a spec documentation conflict. The overall JVM specs
quite clearly says there is a 4K limit for attributes, the JSR spec says
something different. I would think the JVM spec is much more important here. 

For large JSPs, Jasper is adding > 4K work of SourceDebugExtension information
to the compiled classes - this violates the JVM spec and causes the bug.

As I said in my comment, I don't know how the SmapUtil and related classes are
being used by Jasper or when they are used. According to the analysis from the
JDT developer looking at this issue on their end:

"In the .class file that I got, there is such an attribute at the end.
  Attribute: SourceDebugExtension Length: 81342."

Since JDT does not add the SourceDebugExtension attribute during compilation, it
would appear that Jasper is adding it to the bytecode after compilation? I'm
open to an alternate explanation...

I'm attaching the .class and .java files to this bug so you can look at them 
too.

In my opinion, this should be re-opened and looked into, but I will defer to 
you.



-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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

Reply via email to