This may be the problem. I got the binary distribution about 2 weeks ago, do
I need to update from CVS?
-Charles
Justin Forder wrote:
> Charles
>
> There was a bug in tuned updates that gave this effect quite recently,
> but it has been fixed. How up to date is your jBoss?
>
> Justin
>
> In message <[EMAIL PROTECTED]>, Charles Crain
> <[EMAIL PROTECTED]> writes
> >I have been experimenting with container-managed persistence in JBoss.
> >What I cannot figure out is what triggers the server to save the
> >currently loaded entity beans to the database. I've tried running the
> >CD example, as well as a test bean I wrote myself. When you create the
> >bean, JBoss creates a database entry with the primary key populated, and
> >all other fields blank. When you start setting properties of the Bean,
> >they are not updated in the database. If you stop the server (or the
> >machine crashes, etc.) the database stays that way -- primary keys but
> >no data.
> >
> >I figured a graceful shutdown of the server would at least flush the
> >data to the database, but this does not appear to be the case.
> >Furthermore, if the server were to crash, lose power, etc., all new data
> >would be lost.
> >
> >Does anyone know a way to change this?
> >
> >-Charles
> >
> >
> >
> >
> >--
> >--------------------------------------------------------------
> >To subscribe: [EMAIL PROTECTED]
> >To unsubscribe: [EMAIL PROTECTED]
> >Problems?: [EMAIL PROTECTED]
> >
>
> --
> Justin Forder
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
