Hi,
I was wondering if any-one can explain the following behaviour.
I have not altered commit options in any way so my entity beans will be
operating under the default as defined in standardjboss.xml (B). All
methods that my client application calls are transactional and the
documentation states that under commit-option B 'Data is synchronised
from under-lying storage at the start of a transaction'.
The behaviour I am noticing is somewhat quirky:
1. If a row is deleted or inserted from the database manually then this
is picked up instantly.
2. If a particular column is modified then this is not picked up and the
old value is retained. If the container is restarted or I go out for
lunch then the new the bean is eventually refreshed.
This is particularly odd as in trace mode whenever the client calls,
jboss displays EXECUTING SQL: SELECT A,B,C FROM D WHERE ID = ? but then
does not refresh the bean with the new value of B. It appears that the
sql is being executed then ignored.
Have I misunderstood the meaning of 'synchronised' ie: Notices absence
or existing of new entities but not changes to their underlying data, or
is this a bug?
Please Please Help.
Thanks
Lawrence
--
MX Financial Solutions is a trading name of MX Moneyextra Financial
Solutions Ltd, which is regulated by the Financial Services Authority and a
member of the General Insurance Standards Council.
MX Moneyextra Financial Solutions Ltd is registered in England No. 3379907.
Registered Office: One Temple Back East, Temple Quay, Bristol BS1 6DX
A wholly owned subsidiary of Bristol West plc.
---
This SF.net email is sponsored by:Crypto Challenge is now open!
Get cracking and register here for some mind boggling fun and
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
