You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@isis.apache.org by "Dan Haywood (JIRA)" <ji...@apache.org> on 2014/06/04 08:02:04 UTC

[jira] [Updated] (ISIS-796) lifecycle callback "updating()" is not firing

     [ https://issues.apache.org/jira/browse/ISIS-796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dan Haywood updated ISIS-796:
-----------------------------

    Description: 
when trying to override lifecycle callbacks, only some of them fire as expected.

working:
- created()
- saving()
- persisting()
- saved()
- persisted()
- updated()

missing:
- updating()
- loading()
- loaded()

no yet tested:
- removing()
- removed()

test scenario:
- create new entity of class X
- list all entities of X
- open created instance
- edit property
- click 'ok'

result:
according to the logfile, "updated" is called right after the corresponding datastore UPDATE (as expected), but "updating" is missing.

  was:
when trying to override lifecycle callbacks, only some of them fire as expected.

working:
- created()
- saving()
- persisting()
- saved()
- persisted()
- updating()

missing:
- updating()
- loading()
- loaded()

no yet tested:
- removing()
- removed()

test scenario:
- create new entity of class X
- list all entities of X
- open created instance
- edit property
- click 'ok'

result:
according to the logfile, "updated" is called right after the corresponding datastore UPDATE (as expected), but "updating" is missing.


> lifecycle callback "updating()" is not firing
> ---------------------------------------------
>
>                 Key: ISIS-796
>                 URL: https://issues.apache.org/jira/browse/ISIS-796
>             Project: Isis
>          Issue Type: Bug
>          Components: Objectstore: JDO
>    Affects Versions: objectstore-jdo-1.4.0
>         Environment: jdo objectstore on in-memory hsqldb
>            Reporter: Thomas Koren
>            Assignee: Dan Haywood
>
> when trying to override lifecycle callbacks, only some of them fire as expected.
> working:
> - created()
> - saving()
> - persisting()
> - saved()
> - persisted()
> - updated()
> missing:
> - updating()
> - loading()
> - loaded()
> no yet tested:
> - removing()
> - removed()
> test scenario:
> - create new entity of class X
> - list all entities of X
> - open created instance
> - edit property
> - click 'ok'
> result:
> according to the logfile, "updated" is called right after the corresponding datastore UPDATE (as expected), but "updating" is missing.



--
This message was sent by Atlassian JIRA
(v6.2#6252)