Requiring that class loaders are URLClassLoaders (containing file resources) in a three-level arrangement
Common
|
Shared
|
WebApp
Then before executing javac it walks up the classloader chain and calls getURLS() to get the list of jar files and directories for each class loader and places these in a temporary file system where javac can find them.
Although it probably would be easy to do something similar I don't think anyone would agree that that is a good solution.
Regards,
Chris
Robert Simmons wrote:
In my opinion this is the largest fault with cocoon at present. It is rather
strange since the Tomcat servlet engine does not suffer from this limitation.
Since they have already got this working, why cant we borrow their code to
accomplish it?
We will never get enterprise programmers to transfer over from using JSP to
using XSP without such a facility. Having to put all the jars in a classpath is
just NOT a viable solution. Not even a viable workaround.
In fact, I think the goal of cocoon should now be to reel in those enterprise
programmers and bring them into the fold. The days of doing things with direct
SQL and database calls are fast waning into the abyss of impossible large scale
project management. There must be other options. XSP as a competitor to JSP and
ASP technologies is simply not viable without integration with EJBs. Integration
with EJBs means getting our compiler to work with a class loader instead of a
classpath.
I think the milestone for this and related bugs should be firmly 2.1. Once
Cocoon has this, I'm convinced they could hit the big time.
-- Robert
"Michael Homeijer" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
Anyone care to comment on the threads I mentioned?
http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=103769226701593&w=2
http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=103990910724056&w=2
When using xsp pages or actions in an ear (combined with using value objects
returned from ejb's) this is a rather big issue.
Michael
-----Original Message-----
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: 13-2-2003 9:08
Subject: 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
------- Additional Comments From [EMAIL PROTECTED] 2003-02-13 08:08
-------
http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=103769226701593&w=2
http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=103990910724056&w=2
Anyone care to comment on the threads above? Both mention use of either
the
eclipse compiler or the pizza compiler. The first link mentions a
complete
patch for pizza compiler that can directly work in Cocoon.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
