When you are working with entity beans, you must avoid database write
outside the bean. The data is rewritten because if it was allowed to update
the table outside the entity bean then there might be serious
synchronization problems. So as far as I know, there is no solution for your
problem.
Ozgur
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Ebru NAMOGLU
Sent: Thursday, April 12, 2001 11:20 AM
To: [EMAIL PROTECTED]
Subject: EJB Database persistency
I do some tests on JONAS EJB Server and see a problem.
Here's my test:
1. I created a container managed EntityBean which is dealing with a table
called Rules.
2. I executed a client that only runs findAllRules method. (This method
doesn't require Transaction and the passivation-time-out attribute is set 60
seconds for this test. )
3. After execution of the client I manually updated the Rules table
CustomerId column to new values.
4. Then I executed the client again.
Database: When I check the database manually it shows the new values for
about 60 secs, however after 60 seconds it shows the old values.
>From the Bean: It always shows the old values and never gets the values that
I have updated manually.
Note: Even though I only run a select statement within the bean
(findAllRules), after about 60 seconds I see on database that an update
statement which updates the Rules table CustomerId column to the old values
executed. So I lost the CustomerId new values.
Is there any solution of this?
----
To unsubscribe, send email to [EMAIL PROTECTED] and
include in the body of the message "unsubscribe jonas-users".
For general help, send email to [EMAIL PROTECTED] and
include in the body of the message "help".
