Hello Philippe!
Sadly our problem was not solved by switching to Jonas 2.0,
as finder methods do nothing else but a select statement in the
database. We checked this by inspecting the generated code (-keepgenerated).
This implies that I can not find modified data in a transaction even
if I use finder methods - I can not believe that this behavior is correct...
But with Jonas 2.0 we got a still more drastic problem: The rollback
we do cause we can not find the modified data does not work any more.
Even if the finder Exception is thrown and the transaction should be
rolled back, the modified data is in the Datatbase!!!
We can solve the finder method problem by keeping the data we
modify in our own Hashtable, but we can not solve the rollback
problem, so it seems we have to switch back to Jonas 1.6.1.
As much as I respect the work you do in Jonas for the Open Source
community, I'm a little surpriesed about the problems we have with
this simple transaction requirement we have - and I have a lot of
truble argumenting why I have choosen EJB an Jonas for our project.
So please can you give me any hints about the direction Jonas is
moving, especially concernig our problems.
Thanks, Max
> Weißböck Maximilian wrote:
> >
> > We have a massive show-stopping problem using JOnAS 1.6.1
> >
> > In a Session Bean we have a method 'updateData()'
> > (with attribute TX_REQUIRED) that calls methods from a
> > CMP (with attribute TX_SUPPORTS).
> >
> > In a CMP method 'updateBuchungszeile()' we change a
> > field 'buchungszeile' from eg. '333' to '555'.
> >
> > Still inside the SB method 'updateData()' we call the
> > CMP finder method 'findByBuchungszeile()' with the value 555
> > but we get a ObjectNotFoundException!!! Why???
> >
> > Even more misterious, if we do, imediatly after (or before)
> > the 'findByBuchungszeile()' a 'findByPriamrayKey()' of the
> > record where we changed 'buchungszeile' and print out
> > the data, we see the expected value '555'.
> >
> > Why can't the 'findByBuchungszeile()' not see this value '555'???
> >
> > If whe change the TX attributes to TX_NOT_SUPPORTED the
> > 'findByBuchungszeile()' works ok and finds the modified record,
> > but we can not use this the solution, as we can not do a rollback
> > if the 'updateData()' finds any error.
> >
> > We use Database Oracle 7.3 or SQLAnywhere 6.0, the problem
> > is the same with both databases.
> >
> > PLEASE HELP, AS THIS IS A REAL SHOW-STOPPER FOR US!
> >
> > Thanks for any responce, Max
> > ----
> > 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".
> This problem should be fixed now (in jonas 2.0).
> Is it possible for you to use JOnAS 2.0 instead of JOnAS 1.6.1 ?
> I know that you will have to change your deployment descriptor, now in
> XML format!
----
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".
