Rickard �berg wrote:
>
> Justin Forder wrote:
> > I haven't got all the details straight, but this looks to me like a
> > caching problem. The only way I can think of that updates can get
> > "undone" in the way you describe is if more than one instance of the
> > entity is being held in jBoss.
> >
> > Marc - any thoughts? (In another post, Nils says he is using up to date
> > code from CVS)
>
> Could it be a faulty primary key? (Marc would just *love it* if that was
> the case.. ;-)
I don't think so, Rickard, I'm sorry... IHMO it *is* a caching problem;
sad but true, the dummy code, I've posted yesterday *works* <be
ashamed>. The trick is, my test application does some more things (using
session beans, to access the entity beans for example) and until now I'm
not sure, when and where exactly the error occures, but it loks quite
like a caching problem. Anyway: I'm looking for some code, that produces
the error, and then I'll describe that scenario here.
regards: nils
>
> /Rickard
>
> --
> Rickard �berg
>
> Email: [EMAIL PROTECTED]
> http://www.telkel.com
> http://www.jboss.org
> http://www.dreambean.com
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
--
Nils Hartmann
Curry Communication GmbH
Behringstr. 28a, 22765 Hamburg, Germany
Tel: 040 - 398 34 408
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
