Activity report on *[JIRA] New Feature SKER5013 - Using Taglib TLDs across skins*
Scarab Link: http://sesat.no/scarab/issues/id/SKER5013 Module: Sesat> Kernel Activity generated by Karl Øie ([EMAIL PROTECTED]) at 11/04/2008 17:19 *Reasons for the changes* *Comments* - By Karl Øie - 11/04/2008 17:19 --- "I’ve patched an ran with a new jsp decorator like; <%@ page import="no.sesat.search.view.velocity.AccountingDirective"%> <%= AccountingDirective.writeExcelSpreadheet(response.getOutputStream()) %> but the ROOT webapp is unable to resolve no.sesat.search.view.velocity.AccountingDirective because it resides in another webapp/skin. From velocity this class is accessible because of Thread.currentThread().setContextClassLoader(SiteClassLoaderFactory.instanceOf(classContext).getClassLoader()); in the VelocityEngineFactory.java? So to enable jasper to resolve classes in skins we need to set the SiteClassLoader on the webapp itself, because jasper is run by the container? Since Sesat overrides the ROOT context of the container, would it be safe to set our SiteClassLoader globally? Also I think we need to fetch the original webapp classpath and add it’s entries into SiteClassLoader so it’s able to resolve all calls done by Jasper/JSP to the webapp (I suspect it already does add the current classpath)." - By Karl Øie - 11/04/2008 17:22 --- "yes, i know "<%= " would give a getOutputStream() alread called exception, but thats besides the point"
_______________________________________________ Kernel-issues mailing list [email protected] http://sesat.no/mailman/listinfo/kernel-issues
