[
https://issues.jboss.org/browse/SEAMWICKET-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12631724#comment-12631724
]
K. Bachl commented on SEAMWICKET-41:
------------------------------------
@My comment:
it works as long as you do:
@EJB(name = "ServiceEJB")
transient ServiceBean bean;
However, this is quite not nice in case one has many places the usage of EJBs,
so the simple one without transient should work by default and in all
containers equal, meaning seam-wicket should take care of it. Else the
portability will suffer in the long term.
> 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
_______________________________________________
seam-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/seam-issues
