[seam-issues] [JBoss JIRA] Issue Comment Edited: (SEAMWICKET-41) EJB and Seam Wicket result in NotSerializableException

[ https://issues.jboss.org/browse/SEAMWICKET-41?page=com.atlassian.jira.plu... ] Thierry Peng edited comment on SEAMWICKET-41 at 8/10/11 3:49 AM: ----------------------------------------------------------------- So far we have in my opinion three possibilities 1: [Edited] it is the glassfish weld proxy that causes the problem. So we that's possibly a bug filing worthy. On the other hand, I doubt that this will be fixed, for various reason, among that I didn't found anything in the spec that this must be serializable. A bug filing is possible but that would take some time to be fixed and it isn't guaranteed that this will happen. 2: We propose (as described in the seam-wicket guide) the workaround that all injected ejb fields must be transient, and that in the onattach hook the members are injected again. The downside is, that this code must be inserted on every component/page. 3: We use Wicket-ioc and wire a serializable proxy between the injected ejb and the field. I implemented this solution in: https://github.com/caliban/seam-wicket was (Author: pengt): So far we have in my opinion three possibilities 1: We file an issue in weld itself and propose that this ejbRef can be serialized, but then it may be that the glassfish proxy that followes is not serializable and we're back on field one. 2: We propose (as described in the seam-wicket guide) the workaround that all injected ejb fields must be transient, and that in the onattach hook the members are injected again. The downside is, that this code must be inserted on every component/page. 3: We use Wicket-ioc an wire a serializable proxy between the injected ejb and the field. I implemented this solution in: https://github.com/caliban/seam-wicket -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira