geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gianny DAMOUR (JIRA)" <...@geronimo.apache.org>
Subject [jira] Closed: (GERONIMO-598) ejbFind<> or ejbSelect<> following ejbCreate<> within the same TX context
Date Thu, 03 Mar 2005 09:57:48 GMT
     [ 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


Mime
View raw message