[TRINIDAD-2023] CheckSerializationConfigurator should use the Trinidad specific ObjectInputStream (ObjectInputStreamResolveClass) class

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.0-beta-1
• Fix Version/s: 1.2.15-core , 2.0.0-beta-2
• Assignee: Matthias Wessendorf
• Reporter: Matthias Wessendorf
• Created: 28/Jan/11 07:24
• Updated: 31/Jan/11 11:56
• Resolved: 28/Jan/11 13:16

Description

Trinidad's CheckSerializationConfigurator uses the vanilla ObjectInputStream class to read objects - this can cause ClassNotFoundException exceptions.

For instance:

java.lang.IllegalArgumentException: java.lang.ClassNotFoundException: oracle.adf.model.dvt.binding.transform.RowsetDefinitionState
at org.apache.myfaces.trinidadinternal.config.CheckSerializationConfigurator$MutatedBeanChecker._deserializeObject(CheckSerializationConfigurator.java:574)
at org.apache.myfaces.trinidadinternal.config.CheckSerializationConfigurator$MutatedBeanChecker.checkForMutations(CheckSerializationConfigurator.java:525)
at org.apache.myfaces.trinidadinternal.config.CheckSerializationConfigurator$SerializationChecker.checkForMutations(CheckSerializationConfigurator.java:1041)
at org.apache.myfaces.trinidadinternal.config.CheckSerializationConfigurator$SerializationCheckingWrapper.checkForMutations(CheckSerializationConfigurator.java:351)
at org.apache.myfaces.trinidadinternal.config.CheckSerializationConfigurator.endRequest(CheckSerializationConfigurator.java:115)
at org.apache.myfaces.trinidadinternal.config.GlobalConfiguratorImpl._endConfiguratorServiceRequest(GlobalConfiguratorImpl.java:538)
at org.apache.myfaces.trinidadinternal.config.GlobalConfiguratorImpl.endRequest(GlobalConfiguratorImpl.java:295)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:217)
at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)