"bdaw" wrote : Forgot to mention this. We aim to be AS agnostic, so for authorization we should investigate and drop any dependency on services that is are portable. How JBoss Security fit in this?
I know about Portal's AS agnostic intentions. JBoss Security is just an SPI and an implementation. There is nothing that is AS dependent. It should be geared to run in a MC. It does not even require JMX.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4079681#4079681
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4079681
I thought about just adding more annotation support to the service mbean metadata, but that is more error prone for a deployer writer who is programatically creating the mbean metadata. It would not be a big deal for those still using the legacy service.xml.
In terms of the InstanceClassFactory being part of the spi, maybe this should be pushed to the AbstractManagedObjectFactory as an implementation detail for this release.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4079675#4079675
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4079675
"bela(a)jboss.com" wrote : (3) Another solution rather than shutting down is to cease caching values and pass all requests directly on to the underlying DB. Of course, this makes only sense if we *have* a DB, otherwise shutting down is probably our own option
This would need to happen on all partitions, though, otherwise you have the problem of the minor partitions updating the database, and the primary partition then reading stale data from it's cache.
Ceasing caching on all partitions is a problem though, as it's not clear how the primary partition distinguishes the cluster split from normal operation.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4079621#4079621
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4079621