Hello Darius,
Nils Kelleter wrote: > > ..., I update the version of the JavaBasicCartridge and wonder why all > classes should implement java.io.Serializable. > Darius Jockel wrote: > > Hm, you are right. I think only classes you want to persist should > implement java.io.Serializable, > e.g. "Entities". > I think you could say in more general that only classes which you want to serialize should implement java.io.Serializable. ;-) Serialization is not only needed with peristence also for transfer/remoting. I think the decision, for which classes you need the interface (e.g. entities, transfer objects), is project specific and should be configured with an AOP-Template. So I think it is reasonable, that the template in the JavaBasicCartridge should be rolled back to the old version. Regards Nils -- View this message in context: http://www.nabble.com/-JavaBasic--Why-any-class-should-implement-java.io.Serializable--tp24698684s17564p24714493.html Sent from the Fornax-Platform mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Fornax-developer mailing list Fornax-developer@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fornax-developer
