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





------- Additional Comments From [EMAIL PROTECTED]  2005-08-18 12:48 -------
Created an attachment (id=16089)
 --> (http://issues.apache.org/bugzilla/attachment.cgi?id=16089&action=view)
Patch to JaninoJavaCompiler.

At the moment all dependencies to be loaded when compiling go to the
this.loader. This is why everything works except other to-be-compiled classes.
With changing new UnitCompiler(unit, loader) to new UnitCompiler(unit, this) it
is exactly the other way around: every class will be first looked up at the
internal IClassLoader of the JaninoJavaCompiler. This works as long as class
names indeed start with "java." or similar as these calls are delegated to the
this.loader. But for an char[] or probably other similar things this does not
work. You get two different IClass instances and the match in the UnitCompiler
fails when searching for matching methods.

With the correct IClassLoader hierarchie the delegation for the Java core stuff
is not done by hand, but the parent IClassLoader is asked in every case - and
returns the correct IClass for char[].

-- 
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