Hey
Charles Crain wrote:
> 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?
Sounds like a bug somewhere, either in your configuration, or in the
server. Since I have gotten this to work 8-) I would start looking in
your bean and deployment descriptors. Let us know if you don't find
anything, and we'll continue from there.
regards,
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]
