In this case, one has to "export" those packages "explicitly" in order
to be visible.
Shing Wai
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
>