[
https://issues.apache.org/jira/browse/ISIS-651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13890057#comment-13890057
]
ASF subversion and git services commented on ISIS-651:
------------------------------------------------------
Commit 42bf756a07370752def1dd1121b3ed49d5945893 in branch refs/heads/master
from [~danhaywood]
[ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=42bf756 ]
ISIS-651: fixing NPE in ActionMemento and similar
Also: forcing invalidation of Isis ObjectSpec in EntityPage (else the UI is
rendered w.r.t old Isis metadata)
Not exactly sure why either of these are problems. For the latter, certainly,
it seems that the IsisJRebelPlugin invalidates the
cache correctly, but it isn't picked up. It would seem that the Wicket viewer
is holding the ActionMemento, PropertyMemento and CollecitonMemento in-memory?
also:
- adding maxPermSize to launch config for simple app.
> Modifications to enable JRebel support
> --------------------------------------
>
> Key: ISIS-651
> URL: https://issues.apache.org/jira/browse/ISIS-651
> Project: Isis
> Issue Type: Improvement
> Components: Core, Objectstore: JDO
> Affects Versions: objectstore-jdo-1.3.0, core-1.3.0
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Priority: Minor
> Fix For: objectstore-jdo-1.4.0, core-1.4.0
>
>
> Make JDO PersistenceManagerFactory accessible so can be interacted with
> outside of Isis runtime
> Invalidate Isis spec cache by way of class (not just by object).
> ~~~
> need to be able to do similar with the DN metadata:
> http://www.datanucleus.org/servlet/jira/browse/NUCCORE-1104
> Assuming that there's auto-enhancement within the IDE, this means that JRebel
> picks up each class twice: once for the unenhanced class, then almost
> immediately for the enhanced class. Therefore, I think that all that may be
> required is to remove the ClassMetaData whenever an unenhanced class is
> reloaded DN's will lazily recreate metadata as required.
> An enhancement might be to do the enhancement within the JRebel plugin (and
> not in the IDE). This would require the enhancement is done in a separate
> classloader; it (obviously!) isn't allowed to reference the java.lang.Class
> being loaded within the plugin itself. As enhancement does cause this to
> occur, it must be namespaced off to a separate classloader.
> resources:
> -
> http://www.datanucleus.org/servlet/wiki/pages/viewpage.action?pageId=6619188
> (Metadata Generation, programmatic running of Enhancement)
> - http://markmail.org/message/xn6fowrxqeucac26 (useful forum messages
> hinting on the classloader stuff)
> - http://www.datanucleus.org/products/accessplatform/jpa/enhancer.html#api
> (background notes)
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
