[
http://jira.amdatu.org/jira/browse/AMDATU-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12519#comment-12519
]
Bram de Kruijff commented on AMDATU-552:
----------------------------------------
Yes, but they are resources from a bundle (and the classloader is tied to the
service lifecycle) I see no problem with using that. Tricky part is loading
custom libraries into a centralized classloader and, thinking about it, that
would break some modularization as jsp1 can't use taglib (v1) at the same time
that jsp2 uses taglib (v2).
> Support for jsp classloader sharing over multiple (tenant) servlet instances
> ----------------------------------------------------------------------------
>
> Key: AMDATU-552
> URL: http://jira.amdatu.org/jira/browse/AMDATU-552
> Project: Amdatu
> Issue Type: Improvement
> Components: Amdatu Web
> Reporter: Bram de Kruijff
> Fix For: Backlog
>
>
> Currently the JSP support component creates a new instance of
> ResourceProviderJspServlet each containing their private JasperClassLoader.
> Although I have not profiled this yet I have a feeling that this will quickly
> become a (permgen) bottleneck when a significant amount of (multi-tenant) JSP
> servlets gets registered. Can we share (part of) the classlaoders?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
http://jira.amdatu.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Amdatu-developers mailing list
[email protected]
http://lists.amdatu.org/mailman/listinfo/amdatu-developers
