Throwing NotSerializableException instead of serializing means removing
support for clustering SFSBs with an XPC. That IMHO would be a pretty
major feature regression. I believe we have supported that since AS 4.2
if not earlier.
On 10/24/11 9:39 AM, Scott Marlow wrote:
Hi,
I'm looking into handling serialization of the extended persistence
context (for both clustering and EJB3.1 passivation/activation).
The (JPA subsystem) spi is still developing for this but if anyone has
feedback or wants to follow. A sketch for the spi is at
https://github.com/scottmarlow/jboss-as/blob/d7ec51ac14afb47ced7d203f8b36...
One question that comes up is why. Why not just throw
NotSerializableException instead of serializing the extended persistence
context. If anyone feels strongly that we should throw
NotSerializableException instead of serializing the extended persistence
context, I'd like to hear why.
I've made internal changes on
https://github.com/scottmarlow/jboss-as/tree/cluster1 to support
clustering extended persistence contexts. Next is to do the actual
serialization.
Scott
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat