[
https://issues.apache.org/jira/browse/WICKET-2416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12763039#action_12763039
]
Johan Compagner commented on WICKET-2416:
-----------------------------------------
i am reading this thread also a bit now.
What does this mean:
C:\Sun\AppServer\domains\domain1\lib
is this a shared lib? for all webapps?
Thats horrible even library files should always be application specific. An
application server should by default have as little libs sharing over apps as
possible because those are disasters waiting to happen.
But this really seems to me like a classloader problem.
Because where does wicket jar live and where does the other stuff lives. Can
the classloader of the wicket proxy stuff access your application jars/classes??
That looks to me like the problem here.
If you drop all your libraries to a shared lib
and then those libs uses a classloader that is the shared lib classloader
and they want to deserialize something
You have a problem because that classloader cant access your application stuff.
For this i guess somewhere the IClassResolver for the actual application should
be used.
> 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.
