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

Thierry Peng (JIRA) jira-events at lists.jboss.org
Mon Aug 8 02:58:16 EDT 2011

    [ https://issues.jboss.org/browse/SEAMWICKET-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12619275#comment-12619275 ] 

Thierry Peng commented on SEAMWICKET-41:

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 a 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

> EJB and Seam Wicket result in NotSerializableException
> ------------------------------------------------------
>                 Key: SEAMWICKET-41
>                 URL: https://issues.jboss.org/browse/SEAMWICKET-41
>             Project: Seam for Apache Wicket
>          Issue Type: Enhancement
>    Affects Versions: 3.0.0.Final
>         Environment: Wicket 1.4.17, Glassfish 3.1 and Glassfish 3.1.1
>            Reporter: Thierry Peng
>             Fix For: Future
>   Original Estimate: 1 day, 2 hours
>  Remaining Estimate: 1 day, 2 hours
> Injection of EJBs with Seam for Apache Wicket does not work properly. Wicket tries to serialize all injected references once the page/component changes its version. The culprit is the org.glassfish.weld.ejb.SessionObjectReferenceImpl.ejbRef which is not serializable, see the forum reference for the stacktrace.
> There are few discussions about this problem, one mentioned, that the spec doesn't require that an ejb must be serializable, which is true. Because this is a Problem which mainly affects wicket and its way to serializable the component tree, I suggest that we solve it in this module.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the seam-issues mailing list