So, you agree that this message is misleading in that the class specified was NOT really the source of the problem, rather the source must have been the ejb SecProfile?
WARNING: "IOP00100006: (BAD_PARAM) Class net.sf.jasperreports.engine.JRResultSetDataSource is not Serializable"
And why did this error NOT occur for the first invoke to this same code? Why would the findByID method NOT serialize the 1st time but then serialize every time after that?
Matter of fact, in testing I can run this clean the 1st time and then successfully access this same SecProfile bean for inserts, updates, findByPK, and deletes via another service in the same session. Only when I try to also use JasperReports do I get this condition. While in this condition, EVERY EJB ACCESS FROM THIS POINT FORWARD TRIGGERS SERIALIZATION ERRORS SPECIFICALLY ON THE EJB BEANS.
If I don't hit a JasperReport, then I can run the app all day without any serial errors...I don't get it. Naturally, I have NO control over the Jasper API.
[Message sent by forum member 'jameshr' (jameshr)]
http://forums.java.net/jive/thread.jspa?messageID=280204