I remember seeing similar code when I was enabling OSGi in v3 and I had
got it working. Are you saying that JSP support in v3 is broken now?
Secondly, classloader is not always of type URLClassLoader. Can't the
Java compiler be improved to use a ClassLoader to find required
resource? If JDK folks fix this bug [1], would that solve the issue for
JDK 6 at least?
Thanks,
Sahoo
[1]
http://monaco.sfbay.sun.com/detail.jsf?cr=6297388
Kin-man Chung wrote:
> In Jasper, to set the classpath for the Java compiler, we have been
> using the following algorithm (simplified):
>
> loader = currentThread.getContextLoader();
> while (loader != null) {
> for (URLClassLoader cl: loader.getURLs()) {
> classpath.append(cl);
> }
> loader = loader.getParent();
> }
>
> This no longer works in V3. Jasper is now a separate module, and
> the classpath so obtained does not include jasper.jar itself!
>
> I'd appreciate any light that can shed on this issue.
>
> -Kin-man
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>