You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by bu...@apache.org on 2003/02/13 02:24:18 UTC
DO NOT REPLY [Bug 16580] -
Java compiler requires JARs in the FS; can not use classloader
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=16580>.
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=16580
Java compiler requires JARs in the FS; can not use classloader
vgritsenko@apache.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|XSP ClassLoader not |Java compiler requires JARs
|integrated with Cocoon's |in the FS; can not use
|classloader. |classloader
------- Additional Comments From vgritsenko@apache.org 2003-02-13 01:24 -------
> cocoon requires that all jars be deployed in the WAR file
No, this is not necessary, additional JAR files can be added via extra-classpath.
> compiler should use the classloader of the application server
As of today, compiler does not uses *any* classloader, and can *not* use any
classloader. The only thing compiler understands is list of JAR files / classes
directories physically present on the filesystem. That's how all current Java
compilers work.
You are free to join any Java compiler project and write a compiler which can
work without files. Search mail lists - there were couple of messages about such
efforts.
[I'm changing summary line to reflect this]
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org