[JBoss Seam] - Re: Feature request regarding nested conversations
by matt.drees
By the way, I didn't realize this:
"wschwendt" wrote : And the following approach is not viable either: We cannot simply access a component from the parent conversation and call a property Setter of this component with the ending result of the nested conversation supplied as argument for this Setter. The reason is that when a component from the parent conversation is called while the nested conversation is still in progress, the ManagedEntityIdentityInterceptor saves wrappers for the called component in the scope of the nested conversation (!) and not the scope of the parent conversation. So once the nested conversation scope gets destroyed at the end of the nested conversation, the saved wrappers for the component from the parent conversation get destroyed as well.
|
|
I can't help but think this wasn't intended; I'm guessing ManagedEntityIdentityInterceptor is intended to be transparent. (Side rant: it's not transparent, and has caused me some pain.)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4085815#4085815
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4085815
18 years, 10 months
[JBoss Seam] - Re: Seam 2.0 Beta with Weblogic 10
by apatterson11
There is definitely an issue with EJB vararg methods in Weblogic 10 (see stack trace below). Since Seam has quite a few vararg methods then it means that you can't deploy a full JSF->Seam->EJB3.0 application on Weblogic 10 yet.
An error occurred during activation of changes, please see the log for details.
Exception preparing module: EJBModule(jboss-seam.jar) Unable to deploy EJB: jboss-seam.jar from jboss-seam.jar: There are 1 nested errors: java.io.IOException: Compiler failed executable.exec: /checkpoint/weblogic10/wlserver_10.0/samples/domains/wl_server/servers/examplesServer/cache/EJBCompilerCache/-1fp2y4mbf7ax/org/jboss/seam/core/Dispatcher_u7njda_Intf.java:20: modifier transient not allowed here public transient javax.ejb.Timer scheduleEvent(java.lang.String arg0, java.lang.Long arg1, java.util.Date arg2, java.lang.Long arg3, java.lang.Object[] arg4); ^ /checkpoint/weblogic10/wlserver_10.0/samples/domains/wl_server/servers/examplesServer/cache/EJBCompilerCache/-1fp2y4mbf7ax/org/jboss/seam/core/TransactionListener_r4jqkg_LocalTransactionListenerImpl.java:109: modifier transient not allowed here public transient void scheduleEvent(java.lang.String arg0, java.lang.Object[] arg1) ^ /checkpoint/weblogic10/wlserver_10.0/samples/domains/wl_server/servers/examplesServer/cache/EJBCompilerCache/-1fp2y4mbf7ax/org/jboss/seam/core/TransactionListener_r4jqkg_Intf.java:23: modifier transient not allowed here public transient void scheduleEvent(java.lang.String arg0, java.lang.Object[] arg1);
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4085812#4085812
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4085812
18 years, 10 months
[JBoss Seam] - More about nested conversations
by wschwendt
I looked again at the Seam reference documentation, section "6.2. Nested conversations"
It cites correct behavior in the face of backbuttoning and workspace management as motives for nested conversations.
"Seam Reference 6.2" wrote : A conversation may be thought of as a continuable state. Nested conversations allow the application to capture a consistent continuable state at various points in a user interaction, thus insuring truly correct behavior in the face of backbuttoning and workspace management.
|
| TODO: an example to show how a nested conversation prevents bad stuff happening when you backbutton.
Using nested conversation to alleviate problems caused by the back button is exactly what you described in your post, Jacob (post #2 in this thread).
On the other hand, if I think of breadcrumbs and the conversation stack (-> 6.7.5. Breadcrumbs), the use of nested conversations goes into a direction much similar to the composition of "subflows" my post #1 in this thread is related to.
[More to follow]
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4085803#4085803
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4085803
18 years, 10 months