[jira] [Commented] (ISIS-651) Prereqs to possible JRebel support
[ https://issues.apache.org/jira/browse/ISIS-651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13880435#comment-13880435 ] ASF subversion and git services commented on ISIS-651: -- Commit e59219c6c08f313f293e0c6cc2c39e8eb8e8eb39 in branch refs/heads/master from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=e59219c ] ISIS-651: adding a .launch for todo app also. In addition: - delete the rebel.xml files checked in for simple app - update .gitignore to ignore rebel.xml files. - minor tidy up of ToDoItem > Prereqs to possible 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)
[jira] [Commented] (ISIS-651) Prereqs to possible JRebel support
[ https://issues.apache.org/jira/browse/ISIS-651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13880433#comment-13880433 ] ASF subversion and git services commented on ISIS-651: -- Commit 2483ca661ff9536cbaf4b0a94aa6bb9d6922959d in branch refs/heads/master from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=2483ca6 ] ISIS-651: minor improvements to core ... to better support JRebel (in testing Estatio). > Prereqs to possible 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)
[jira] [Commented] (ISIS-651) Prereqs to possible JRebel support
[ https://issues.apache.org/jira/browse/ISIS-651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13879251#comment-13879251 ] ASF subversion and git services commented on ISIS-651: -- Commit 6b497b0ca8f9bf20fcef0ad54db9c0d3a8971346 in branch refs/heads/master from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=6b497b0 ] ISIS-651: further changes for JRebel support provide ability to discard PMF additions to SimpleApp with the JRebel config. > Prereqs to possible 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)
[jira] [Commented] (ISIS-651) Prereqs to possible JRebel support
[ https://issues.apache.org/jira/browse/ISIS-651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13874748#comment-13874748 ] ASF subversion and git services commented on ISIS-651: -- Commit a008bfa4f6b07f8b7c276cfc80d9ba339c7132be in branch refs/heads/master from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=a008bfa ] ISIS-651: make JDO PMF accessible, invalidateCache signature in addition: - sorted out .launch files for ToDo app and Simple app, added to appropriate favourites. > Prereqs to possible 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) -- This message was sent by Atlassian JIRA (v6.1.5#6160)
