[JBoss Seam] - Long Running Conversation Problem after Upgrade to Seam 2.0.
by jgaoz
We are using JBoss 4.2.0 with Seam.
Currently we meet a long running conversation problem just after upgrading seam from 2.0.0 Beta1 to 2.0.0 GA. The problem is described as following.
We have a scenario of long running conversation involving three stateful beans, Bean A (@Begin init()), Bean B (@Begin(join=true) init() ), Bean C (@Begin(join=true) init() ). These three beans are backing three pages (Page A, Page B, and Page C) individually.
Page A invokes the Bean AâÂÂs init( ) method to start the long conversation; When user inputs some data and clicks a âÂÂGoâ button on Page A, the user is navigated to Page B and Bean B joins the conversation by its init() method invoked; Then after user inputs some data and clicks a âÂÂGoâ button on Page B, the user is navigated to Page C and Bean C joins the conversation by its init() method invoked.
So far so good. But the problem comes when user clicks âÂÂDoneâ button on Page C and the user is navigated back to Page B. At this time, it is observed that the states of Bean B are not restored (lost). (The Beam B object reference is retrieved correctly)
Previously with Seam 2.0.0 Beta1, it was observed that the states of Bean B were restored correctly.
Is there anyone who met the same problem? Can Seam team give some clue to solve the problem or workaround?
Thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110334#4110334
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4110334
18 years, 4 months
[JBoss Seam] - java.sql.Date, Seam-GWT remoting with EJB3/hibernate/JPA
by hartfordd
Hey all,
After a lot of digging, finally found where I am having an issue with some DTO transports using the SEAM-GWT remoting.
First, the (not useful) error on the client/browser side:
=========================
| com.google.gwt.user.client.rpc.IncompatibleRemoteServiceException: This application is out of date, please click the refresh button on your browser
|
| com.google.gwt.user.client.rpc.IncompatibleRemoteServiceException
|
=========================
Second, where the problem is originating from:
===========
DTO.java:
| @Temporal(TemporalType.DATE)
| private java.util.Date dateField;
|
===========
And third, the actual class that is returned (by hibernate):
============
datefield type:java.sql.Date
============
What is returned by the JPA layer, in this case Hibernate, is causing problems within SEAM when trying to transfer the DTO to the GWT client side.
Manually creating the DTO (without hibernate) with a regular java.util.Date works correctly, but changing it to java.sql.Date causes problems as seen in the error above.
Tested with jboss 4.2.1, seam 2.0.0.GA (GWT 1.4.60).
HTH,
-D
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110330#4110330
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4110330
18 years, 4 months