[
https://issues.apache.org/jira/browse/WICKET-2416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bernard reopened WICKET-2416:
-----------------------------
Igor, thanks for spending your time on this again, this is very much
appreciated. Your test case was certainly helpful.
It shows that it is one of the cases where wicket-contrib-javaee actually works.
You can get your testcase to crash as follows: Copy all the jars under App\lib\
into the application server directory e.g. C:\Sun\AppServer\domains\domain1\lib
where they actually belong as these are library files not application files.
Don't package them with the application
(uncheck the option "Package" in the Libraries dialog, compile tab). This will
crash.
To take this one step further, to really prove what is going on, leaving the
library files in C:\Sun\AppServer\domains\domain1\lib, you may then copy the
file App-ejb.jar there as well and the application will NOT crash.
This possibly confirms your first assessment that this is a classloader
visibility issue.
> 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.1
> Environment: Java 1.6.
> Wicket Java EE 1.1
> Reporter: bernard
> Assignee: Igor Vaynberg
> Attachments: App.rar, 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.
