You could use an Object Store such as Ozone where all mutators are marked as
update transactions and will be stored when the mutator invoked. The
Ozone-Jboss integration does not propage transactions between the JBoss TM
and the Ozone TM right now but that is on the todo list. Or you could create
a similar behavior yourself i.e. make sure the file is persisted as part of
whatever transaction that initated the modification. In this case you might
want to work with a proxy to the persistant object so that you are detaching
the storage mechanism from the actual object usage making sure that the
details of keeping files open etc. is managed so it is not currupting objects
on the event of a crash..
Hope I understood your question right.
Best regards,
Per
On Tuesday 10 December 2002 06.32, Andy wrote:
> Hi Geeks
>
> I try to implement a file persistence for the EJB timer and run into
> problems when the server crashes. It seems that the file sometimes
> become corrupted after a crash. Unfortunately the timer can contain
> an unknown but serializable object. I crashed the server during a
> period when the file is not written but I keep the file open as long
> as the server is alive.
>
> Does someone know how to implement a file based persistence that
> does not become corrupted except maybe when the file is written
> during a crash.
>
> Thanx
>
> Andreas Schaefer
> "Code or be coded"
>
> Check out www.madplanet.com
>
>
>
>
> ---
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> ___
> Jboss-development mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-development
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
