You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Gianny DAMOUR (JIRA)" <de...@geronimo.apache.org> on 2005/03/01 08:46:49 UTC
[jira] Created: (GERONIMO-598) ejbFind<> or ejbSelect<> following ejbCreate<> within the same TX context
ejbFind<> or ejbSelect<> following ejbCreate<> within the same TX context
-------------------------------------------------------------------------
Key: GERONIMO-598
URL: http://issues.apache.org/jira/browse/GERONIMO-598
Project: Geronimo
Type: Bug
Components: OpenEJB
Versions: 1.0-M3
Reporter: Gianny DAMOUR
Assigned to: Gianny DAMOUR
Fix For: 1.0-M4
Currently database operations are flushed upon TX commit.
This is an issue where:
* an Entity Bean is created; and
* then an ejbFind<> or ejbSelect<>, whose result is modified by the previously created Entity Bean, is executed in the same TX context.
It should be possible to force/configure a database flush prior any finder or select method.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
Re: [jira] Closed: (GERONIMO-598) ejbFind<> or ejbSelect<> following ejbCreate<> within the same TX context
Posted by Dain Sundstrom <ds...@gluecode.com>.
This should be the default mode. The spec requires flushing, but we
can optionally turn it off.
-dain
--
Dain Sundstrom
Chief Architect
Gluecode Software
310.536.8355, ext. 26
On Mar 2, 2005, at 3:53 AM, Gianny DAMOUR (JIRA) wrote:
> [ http://issues.apache.org/jira/browse/GERONIMO-598?page=history ]
>
> Gianny DAMOUR closed GERONIMO-598:
> ----------------------------------
>
> Resolution: Fixed
>
> This has been fixed.
>
> An optional element, namely flush-cache-before-query, indicates if the
> transaction cache is to be flushed before the execution of the
> associated finder or select.
>
>> ejbFind<> or ejbSelect<> following ejbCreate<> within the same TX
>> context
>> ----------------------------------------------------------------------
>> ---
>>
>> Key: GERONIMO-598
>> URL: http://issues.apache.org/jira/browse/GERONIMO-598
>> Project: Geronimo
>> Type: Bug
>> Components: OpenEJB
>> Versions: 1.0-M3
>> Reporter: Gianny DAMOUR
>> Assignee: Gianny DAMOUR
>> Fix For: 1.0-M4
>
>>
>> Currently database operations are flushed upon TX commit.
>> This is an issue where:
>> * an Entity Bean is created; and
>> * then an ejbFind<> or ejbSelect<>, whose result is modified by the
>> previously created Entity Bean, is executed in the same TX context.
>> It should be possible to force/configure a database flush prior any
>> finder or select method.
>
> --
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the administrators:
> http://issues.apache.org/jira/secure/Administrators.jspa
> -
> If you want more information on JIRA, or have a bug to report see:
> http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-598) ejbFind<> or ejbSelect<> following ejbCreate<> within the same TX context
Posted by "Gianny DAMOUR (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-598?page=history ]
Gianny DAMOUR closed GERONIMO-598:
----------------------------------
Resolution: Fixed
This has been fixed.
An optional element, namely flush-cache-before-query, indicates if the transaction cache is to be flushed before the execution of the associated finder or select.
> ejbFind<> or ejbSelect<> following ejbCreate<> within the same TX context
> -------------------------------------------------------------------------
>
> Key: GERONIMO-598
> URL: http://issues.apache.org/jira/browse/GERONIMO-598
> Project: Geronimo
> Type: Bug
> Components: OpenEJB
> Versions: 1.0-M3
> Reporter: Gianny DAMOUR
> Assignee: Gianny DAMOUR
> Fix For: 1.0-M4
>
> Currently database operations are flushed upon TX commit.
> This is an issue where:
> * an Entity Bean is created; and
> * then an ejbFind<> or ejbSelect<>, whose result is modified by the previously created Entity Bean, is executed in the same TX context.
> It should be possible to force/configure a database flush prior any finder or select method.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Reopened: (GERONIMO-598) ejbFind<> or ejbSelect<> following ejbCreate<> within the same TX context
Posted by "Gianny DAMOUR (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-598?page=history ]
Gianny DAMOUR reopened GERONIMO-598:
------------------------------------
Dain: This (transaction cache is to be flushed before the execution of the associated finder or select) should be the default mode. The spec requires flushing, but we can optionally turn it off.
Need to "reverse" the implementation.
> ejbFind<> or ejbSelect<> following ejbCreate<> within the same TX context
> -------------------------------------------------------------------------
>
> Key: GERONIMO-598
> URL: http://issues.apache.org/jira/browse/GERONIMO-598
> Project: Geronimo
> Type: Bug
> Components: OpenEJB
> Versions: 1.0-M3
> Reporter: Gianny DAMOUR
> Assignee: Gianny DAMOUR
> Fix For: 1.0-M4
>
> Currently database operations are flushed upon TX commit.
> This is an issue where:
> * an Entity Bean is created; and
> * then an ejbFind<> or ejbSelect<>, whose result is modified by the previously created Entity Bean, is executed in the same TX context.
> It should be possible to force/configure a database flush prior any finder or select method.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-598) ejbFind<> or ejbSelect<> following ejbCreate<> within the same TX context
Posted by "Gianny DAMOUR (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-598?page=history ]
Gianny DAMOUR closed GERONIMO-598:
----------------------------------
Resolution: Fixed
Replace flush-cache-before-query by no-cache-flush, which indicates if the transactional cache is not to be flushed for the associated select or finder.
> ejbFind<> or ejbSelect<> following ejbCreate<> within the same TX context
> -------------------------------------------------------------------------
>
> Key: GERONIMO-598
> URL: http://issues.apache.org/jira/browse/GERONIMO-598
> Project: Geronimo
> Type: Bug
> Components: OpenEJB
> Versions: 1.0-M3
> Reporter: Gianny DAMOUR
> Assignee: Gianny DAMOUR
> Fix For: 1.0-M4
>
> Currently database operations are flushed upon TX commit.
> This is an issue where:
> * an Entity Bean is created; and
> * then an ejbFind<> or ejbSelect<>, whose result is modified by the previously created Entity Bean, is executed in the same TX context.
> It should be possible to force/configure a database flush prior any finder or select method.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira