[
https://issues.apache.org/jira/browse/WICKET-2416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12741001#action_12741001
]
bernard commented on WICKET-2416:
---------------------------------
Igor,
There are many alternatives to JSF, however EJB 3.0 really does not have an
alternative because it is a standard.
I use Wicket because it appears to be more productive than JSF. That is my
compliment to the Wicket team.
I use EJB 3.0 because of its good productivity which appears to be a good match
for Wicket.
However it would not be a good strategy to have Wicket productivity on the
expense of breaking compatibility with the major EJB 3.0 server GlassFish, and
potentially others.
At this stage, I am not in the position to try another application server yet.
If this is indeed a GlassFish issue, then I would prefer that it be raised at
https://glassfish.dev.java.net/issues by a Wicket project team member for
reasons of competency. In any case it would be helpful if you could identify
where the issue belongs.
As I wrote before, I cannot comment on the serialization issue itself, except
that in my opinion, there is no business need to serialize a shared resource
that belongs to a server pool. I accept that on a lower level things might be
different.
The application developer uses the @EJB annotation to avoid writing messy
boiler plate code to get access to an EJB if required. The application
developer does not want to know how it works - it should just be available when
required. The reasonable assumption is that it should be available in a page
retrieved from a page store in the same way as in a new page.
Best Regards
Bernard
> 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.
