It might help to add some debug print code to
java.util.ArrayList.writeObject() (in java.util.ArrayList.java around line
529).
There are some hoops that you have to jump through to get the updated class
ArrayList class file in to be used.
It should be worthwhile if you get information abo
1. Based on some further research, I did not find any "java.lang.Object"
declaration in the (Beans/VO, Action forms, Decorators) of the application
classes.
2. The Mappings are clean and theres no DB -> field mapping of type Object.
3. Although, In "com.ibatis.db.sqlmap.cache.memory" package,
>From looking at that, it would seem the the type of the object put in the list
>would be controlled by the mapping iBatis is using. If some db field is
>mapped to java.lang.Object, that's what you'll get. Hard to see why a db
>field would be mapped to java.lang.Object, though.
View the origi
Well, I think this has got to do with the way Ibatis is implemented. Here's an
example.
private List runQueryForList(SqlStatement localSql, Connection conn, Object
parameterObject, int skipResults, int maxResults, RowHandler rowHandler)
throws SQLException
{
List list;
The problem isn't that any application class or iBatis class isn't
Serializable. It's that one of the fields of one of those classes is of type
java.lang.Object. That field is not Serializable, because java.lang.Object
isn't. You need to find that field.
View the original post :
http://www.j
We investigated the application code and Ibatis sources.
1. All the application classes (Beans, Actionforms, Decorators) are
serializable. (This takes care of all the objects in chain)
2. We suspected that Ibatis could be problem area and made all the classes
serializable (For sanity sake)
Yet
Somewhere in the object graph is an instance of java.lang.Object, which does
not implement Serializable. Looks like the ref is held by a fairly deep object
graph rooted in an ArrayList; the ArrayList is object stored as a session
attribute.
View the original post :
http://www.jboss.com/index.
