DO NOT REPLY [Bug 22293] - JSPC class name doesn't match Jasper

[bu...@apache.org]

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

JSPC class name doesn't match Jasper

brettporter@yahoo.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|JasperLoader prepends fixed |JSPC class name doesn't
                   |package name                |match Jasper



------- Additional Comments From brettporter@yahoo.com  2003-08-11 22:36 -------
Remy, reading your comment makes me think we are talking about different things.
What I am aiming to do is avoid compiling JSPs on access, by compiling them via
ant and including them in the webapp.

However, we have had the situation of needing to change a JSP on the fly and
recompile it on access. I don't know how Tomcat 5.0.x is going to work for that
sort of thing.

All I'm trying to do is have JSPC generate the same structure as the work
directory so they can be interchangable.

This will be in production here with my patch in the next 2 weeks. I don't see
why it can't be applied to the TC4 branch if it will only improve the functionality.

I've closed 22294 as a duplicate of this, because I guess they were really the
same problem of JSPC differing from Jasper at runtime. It just differed in 2 ways.