[
https://issues.apache.org/jira/browse/ISIS-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andi Huber updated ISIS-1754:
-----------------------------
Description:
Skinny-war and fat-war deployments work as long as the JEE server is in a
state, where DataNucleus (5.1) was not yet loaded by any class-loader. (e.g.
nothing deployed, and fresh boot of JEE server)
Once DN is loaded by the JEE any subsequent deployment will fail.
was:
as per
https://lists.apache.org/thread.html/a815c6d3e50c02111d0cd3df93b70b529c18193f321e613b116119b4@%3Cdev.isis.apache.org%3E
Class.forName(...), so we need a plug-able class-loading mechanism.
(What worked for me is
Thread.currentThread().getContextClassLoader().loadClass(...)).
Unfortunately this applies also to DataNucleus. So I had to patch their
class loading mechanism. (Sounds dramatic, but was just a single line of
code.)
> JEE Support - ClassLoading Issues
> ---------------------------------
>
> Key: ISIS-1754
> URL: https://issues.apache.org/jira/browse/ISIS-1754
> Project: Isis
> Issue Type: Improvement
> Reporter: Dan Haywood
> Assignee: Andi Huber
> Fix For: 2.0.0
>
>
> Skinny-war and fat-war deployments work as long as the JEE server is in a
> state, where DataNucleus (5.1) was not yet loaded by any class-loader. (e.g.
> nothing deployed, and fresh boot of JEE server)
> Once DN is loaded by the JEE any subsequent deployment will fail.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
