[ https://issues.apache.org/jira/browse/WICKET-2416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12740969#action_12740969 ]
bernard commented on WICKET-2416: --------------------------------- Igor, Thanks for generalizing this test case. My statement "wicket-javaee works fine in regular cases" is no longer true. That means that the @EJB annotation cannot be used in Wicket because of its page deserialization. I think we might have a case for including wicket-javaee in wicket. EJB 3.0 is the standard Java Enterprise technology, and Wicket should not have any issues with it. I am suggesting to raise the priority of this from "Minor" to something else. > Exception with EJB Session Bean > ------------------------------- > > Key: WICKET-2416 > URL: https://issues.apache.org/jira/browse/WICKET-2416 > Project: Wicket > Issue Type: Bug > Components: wicket > Affects Versions: 1.4.0 > Environment: Java 1.6. > Wicket Java EE 1.1 > Reporter: bernard > Priority: Minor > Attachments: testcase.zip > > > The attached testcase gets an exception > java.io.InvalidClassException: test.session.TestSessionLocal; could not > resolve class [test.session.TestSessionLocal] when deserializing proxy > at > org.apache.wicket.proxy.LazyInitProxyFactory$ProxyReplacement.readResolve(LazyInitProxyFactory.java:236) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > when the user clicks through it, starting from index.html. > I can't really make any progress without a fix, or without knowing what I am > doing wrong to get this. > The testcase will work out of the box with NetBeans 6.7.1 and Server: > GlassFish V2 which is bundled with it. > I don't know what really causes this. It is interesting that the tescase runs > ok when > two lines are removed from Page2.java. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.