Strategy for supporting NonSerializable data

[dimitris]

With the switch to JDK5, accessing remotely the MBeanServer over the legacy JMXAdaptor and getting back MBeanInfo is problematic, due to non-serializable objects stored in the MBeanInfo Descriptors.

We could deal with this under jdk1.4 by controling the javax.management.modelmbean.DescriptorSupport, but not when using jdk5.

A possible short-term solution is to create an interceptor that filters out non-serializable stuff:
http://jira.jboss.com/jira/browse/JBAS-1955

Is there any other strategy or plan dealing with this problem, by the Remoting and Serialization projects?

I see org.jboss.invocation.MarshalledInvocation can delegate to Cleberts plugable Serialization - could this be used?

[starksm64]

A custom jsr160 connector that allows for control of serialization of types that are not Serializable is the proper solution. The default implementation could use the jboss serialization capabilities.

The 1955 short term solution seems like the best immeadiate approach.

[tom.elrod]

JBoss Serialization will allow serialization of classes not implementing Serializable interface, but requires jdk 1.5 (no problem) and the class have a void constructor (which can be private). Don't know if this has changed, but might be too limiting?