I used to use NonSerializableFactory to bind my classes that are truly non-serializable. But now with JBoss 3.0.0 the server complains that the class I'm trying to bind is not serializable. It's simple to put implements java.io.Serializable on my classes but they are not serializable, so looks like I'll have a lot of work to port my app to JBoss 3.
Is this a deliberate semantics change in the way NonSerializableFactory is used?
