I am involved in a complex Java EE project of our customer for more than six month now. The project is a 3-tier design, where the application server is a JBoss 7.1.1 over an Oracle 11g database. The GUI designers do not access directly the database, so it is unimportant which database is used at all. On the GUI site, JGoodies makes the bindings. The server side uses annotations and uses CDI to inject properties. The design is rather complex: All the code is subdivided in around 90 eclipse projects.
As usual, access to database tables is done using JPA entities. Currently, I am working to make the connection to the server of a previously designed dialog that used CSV data before, but I run into problems. Unfortunately, all the knowing personal is on vacation, so I wanted to bother you with my problem.
The error message I get seems to be straightforward. It reads:
[30.08.2013 10:53:05.628] INFO [Class:RmTracer Thread:AWT-EventQueue-0] - WriteAbortedException: writing aborted; java.io.NotSerializableException: net.atos.roman.tmtbl.jpa.dao.train.adjunct.JPATrainType
I searched the Internet and found out the answer that in this case, it is advisable to make the object serializable. However, all JPA entities in this project are not serializable. So, my
How can I find out why
the system wants a serialization on this class?
If I follow the advise found above, I get another error message:
[30.08.2013 11:26:12.789] INFO [Class:RmTracer Thread:AWT-EventQueue-0] - ClassNotFoundException: net.atos.roman.tmtbl.jpa.dao.train.adjunct.JPATrainType
Although the location has not been changed and the persistence.xml
files of the project are the same, the server cannot find the serialized class. This results in my
What can be the reason that this class becomes unfindable?
Thank you for your help.