[
https://issues.apache.org/jira/browse/GERONIMO-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12483606
]
David Jencks commented on GERONIMO-1945:
----------------------------------------
If I understand this patch correctly (after a very cursory review) it makes it
so each module in an ear has a separate unrelated classloader. If so IMO it
requires careful review and testing since this is an enormous change in our
classloading policy and this should probably be postponed until after 2.0 is
out. If I've misunderstood and all the connector and ejb modules still share a
classloader then this patch IMO could be considered for 2.0 although it would
still be good to have a lot of testing.
I think that a classloader per module in an ear is probably a good idea but it
is a big and potentially very destabilizing change.
> Console's web application list does not show WARs that are deployed inside
> EARs
> -------------------------------------------------------------------------------
>
> Key: GERONIMO-1945
> URL: https://issues.apache.org/jira/browse/GERONIMO-1945
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: console
> Affects Versions: 1.0, 2.0-M1
> Reporter: Erin Mulder
> Fix For: 2.0-M1
>
> Attachments: jira1945.patch
>
>
> In the console, click on "Applications -> Web App WARs". The resulting list
> of web applications does not include any web application that is packaged as
> part of an EAR.
> (The list is populated inside ConfigManagerPortlet.doView)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
