RE: cvs commit: jakarta-tomcat-4.0/jasper/src/share/org/apache/ja sper/compiler JspCompiler.java JspReader.java ParserController.java TagLi braryInfoImpl.java

[Steve Downey <st...@netfolio.com>]

Javac does need to get at the class files in WEB-INF/classes, for any jsp
that, say, uses a bean or tag defined in the WAR.

It isn't a requirement that the .java files for those classes be accessible.


> -----Original Message-----
> From: Mel Martinez [mailto:melaquias@yahoo.com]
> Sent: Wednesday, March 21, 2001 9:57 AM
> To: tomcat-dev@jakarta.apache.org
> Subject: Re: cvs commit:
> jakarta-tomcat-4.0/jasper/src/share/org/apache/jasper/compiler
> JspCompiler.java JspReader.java ParserController.java
> TagLibraryInfoImpl.java
> 
> 
> 
> --- remm@apache.org wrote:
> > remm        01/03/20 16:08:53
> > 
> >   Modified:   
> > jasper/src/share/org/apache/jasper/compiler
> > JspCompiler.java
> >                         JspReader.java
> > ParserController.java
> >                         TagLibraryInfoImpl.java
> >   Log:
> >   - Jasper should run from WARs (or any other
> > repository which provides a directory
> >     context to access it).
> >   - All Watchdog 4 tests pass (servlets, JSP,
> > JSP-XML).
> >   - Of course, the classes and JARs are still
> > extracted from the WAR until the
> >     compilation technology is updated (javac wants
> > files :(( ).
> >   
> 
> :-)  But javac doesn't have any reason to deal with
> the contents of the WAR directly.  JSP 'files' read
> out of the .war are being converted to .java files
> stored in the working directory (i.e. /tmp or
> wherever).  Javac just has to deal with the latter
> files.
> 
> It should be possible to modify Jasper to work with an
> unexpanded .war archive.  Not necessarily trivial, but
> definitely possible, in principle, with no need for
> new javac compilation tech.
> 
> Cheers,
> 
> Mel
> 
> __________________________________________________
> Do You Yahoo!?
> Get email at your own domain with Yahoo! Mail. 
> http://personal.mail.yahoo.com/
> 
<><><><><><><><><><><><><><><><><><><><><>This electronic mail transmission
may contain confidential information and is intended only for the person(s)
named.  Any use, copying or disclosure by any other person is strictly
prohibited.  If you have received this transmission in error, please notify
the sender via e-mail. <><><><><><><><><><><><><><><><><><><><><>

RE: cvs commit: jakarta-tomcat-4.0/jasper/src/share/org/apache/ja sper/compiler JspCompiler.java JspReader.java ParserController.java TagLi braryInfoImpl.java

["Craig R. McClanahan" <cr...@apache.org>]

On Wed, 21 Mar 2001, Steve Downey wrote:

> Javac does need to get at the class files in WEB-INF/classes, for any jsp
> that, say, uses a bean or tag defined in the WAR.
> 
> It isn't a requirement that the .java files for those classes be accessible.
> 

The Java sources do not have to be available, but the .class files
do.  Otherwise, when you compile a JSP page that uses a scriptlet
reference to a bean class in WEB-INF/classes, the compile will fail with a
class not found.

If you are running out of a WAR, there is no way to tell the compiler "use
this subdirectory of files out of this WAR file here".  That's why the
(previously working) code pulls out the appropriate stuff and *adds* the
appropriate work directories and JARs to the classpath provided by
Catalina.

Craig