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/07/18 11:59:04 UTC
[jira] [Resolved] (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 resolved ISIS-796.
------------------------------
Resolution: Fixed
> lifecycle callback "updating()" is not firing
> ---------------------------------------------
>
> Key: ISIS-796
> URL: https://issues.apache.org/jira/browse/ISIS-796
> Project: Isis
> Issue Type: Bug
> Components: Core: Objectstore: JDO
> Affects Versions: objectstore-jdo-1.4.0
> Environment: jdo objectstore on in-memory hsqldb
> Reporter: Thomas Koren
> Assignee: Dan Haywood
> Fix For: core-1.6.0
>
>
> 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)
Re: [jira] [Resolved] (ISIS-796) lifecycle callback "updating()" is not firing
Posted by GESCONSULTOR - Óscar Bou <o....@gesconsultor.com>.
Really nice ... and useful :))
El 18/07/2014, a las 11:59, Dan Haywood (JIRA) <ji...@apache.org> escribió:
>
> [ https://issues.apache.org/jira/browse/ISIS-796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Dan Haywood resolved ISIS-796.
> ------------------------------
>
> Resolution: Fixed
>
>> lifecycle callback "updating()" is not firing
>> ---------------------------------------------
>>
>> Key: ISIS-796
>> URL: https://issues.apache.org/jira/browse/ISIS-796
>> Project: Isis
>> Issue Type: Bug
>> Components: Core: Objectstore: JDO
>> Affects Versions: objectstore-jdo-1.4.0
>> Environment: jdo objectstore on in-memory hsqldb
>> Reporter: Thomas Koren
>> Assignee: Dan Haywood
>> Fix For: core-1.6.0
>>
>>
>> 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)
Óscar Bou Bou
Responsable de Producto
Auditor Jefe de Certificación ISO 27001 en BSI
CISA, CRISC, APMG ISO 20000, ITIL-F
902 900 231 / 620 267 520
http://www.twitter.com/oscarbou
http://es.linkedin.com/in/oscarbou
http://www.GesConsultor.com
Este mensaje y los ficheros anexos son confidenciales. Los mismos contienen información reservada que no puede ser difundida. Si usted ha recibido este correo por error, tenga la amabilidad de eliminarlo de su sistema y avisar al remitente mediante reenvío a su dirección electrónica; no deberá copiar el mensaje ni divulgar su contenido a ninguna persona.
Su dirección de correo electrónico junto a sus datos personales constan en un fichero titularidad de Gesdatos Software, S.L. cuya finalidad es la de mantener el contacto con Ud. Si quiere saber de qué información disponemos de Ud., modificarla, y en su caso, cancelarla, puede hacerlo enviando un escrito al efecto, acompañado de una fotocopia de su D.N.I. a la siguiente dirección: Gesdatos Software, S.L. , Paseo de la Castellana, 153 bajo - 28046 (Madrid), y Avda. Cortes Valencianas num. 50, 1ºC - 46015 (Valencia). Asimismo, es su responsabilidad comprobar que este mensaje o sus archivos adjuntos no contengan virus informáticos, y en caso que los tuvieran eliminarlos.