[jira] Commented: (WICKET-2416) Exception with EJB Session Bean

["bernard (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/WICKET-2416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12739788#action_12739788 ] 

bernard commented on WICKET-2416:
---------------------------------

There is a large number of combinations of Wicket with other complementing frameworks and implementations such as Spring, Hibernate, JBoss, Tomcat, GlassFish etc.. Uses of these individual technologies are a spread-out fairly thinly due to the fragmentation of the market and Wicket being novel.

EJB 3.0 is a substantial application development platform, and even more so, it combines and unifies some of these fragments.

I think it is in the interest of the Wicket community for Wicket to shine on this platform.

I can't comment on the classloader issues.

>From my limited application development perspective, wicket-javaee works fine in regular cases. However, the @EJB annotation crashes any page that is retrieved via PageReference#getPage(). PageReference is new in Wicket 1.4 and we application developers have been encouraged to use it as best practice to avoid serialization issues.

An application developer shouldn't need to know anything about the life cycle of an ejb reference in a wicket page. That is why we have the @EJB annotation which simplifies things.

Classloader issues should be circumventable because of the following very simple logic:

The @EJB annotated field does not contain any data that should be serialized.
It should be the same on a page retrieved via PageReference#getPage() as on a new page.

So is it possible that the same process that the @EJB annotation applies to a new page is applied to a page retrieved via PageReference#getPage()?



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