hello,
> I had already planned on making the attributes persist.
>
> But not in a way that would be acceptable for generic JBoss uses (I
> suppose).
>
> I was going to add a MBeanConfigEJB (CMP bean), that basically had 3
> fields.
...
> For clustering, I would post a JMS message for each change, to avoid the
> other instances from hitting the database when something changes.
>
> This would all be done using select-for-update turned on. So other
> instances in the cluster would have serialized access to the row, to
> avoid them stepping on each others changes.
For clustering, do not hesitate to take a look at the clustering framework,
you may find some primitives that fit your needs. You can share state in the
cluster automatically, make multicast RPC calls, ...
That will not directly solve long-living persistence issues, but will most
probably help you much regarding cluster-wide state coherency and
modifications, state transfer when a new node starts, ...
Bill and I stay tuned!
Cheers,
Sacha
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
