[
https://issues.apache.org/jira/browse/ISIS-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253677#comment-16253677
]
Andi Huber commented on ISIS-1754:
----------------------------------
I'll need to cleanup this chaotic jira issue (description and comments).
Currently I'm working on well defined deployment tests, but I'm not able to
reproduce the issue as stated by the description.
Problems only had earlier occurred on my development machine during many
deploy/undeploy cycles during development on a project with lots of shared
dependencies. Hard to say what caused it. Maybe we have no issue at all. Better
testing methodology should tell!
> 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 could fail with
> org.datanucleus.metadata.InvalidClassMetaDataException under special
> circumstances:
> * a persistence-capable class (A) inherits from a super class (S), while A is
> 'skinny-war deployed' and S resides in a container shared library
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
