[
https://issues.apache.org/jira/browse/ISIS-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16220114#comment-16220114
]
Andi Huber commented on ISIS-1754:
----------------------------------
I need to investigate DN's customize-able class-loading mechanism via
{code}JDOClassLoaderResolver [1]{code}
Maybe we can adopt some concepts they have into Isis. Patching DN should not be
required.
[1]
http://www.datanucleus.org/products/accessplatform/extensions/extensions.html#_plugins_in_a_non_managed_environment
> JEE Support - replace Class.forName with TCL.loadClass (+ patching DN)
> ----------------------------------------------------------------------
>
> 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
>
>
> 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.)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
