[JBoss Seam] - Conversation context flush required before redirect?
by quilleashm
Hi all,
I have some code like this (pseduo)
| MyConversationComponent comp = MyConversationComponent.instance()
| comp.setValue( xxx )
|
| Redirect redirect = Redirect.instance()
| redirect.setViewId( xxx )
| redirect.setConvProp( true )
| redirect.execute()
|
Now after the redirect I try and access the MyConversationComponent in a detail component and it wasn't there. I found that unless I called Contexts.getConversationContext().flush() the component would not get copied into the backing session and so would not be available after the redirect. The conversation was being propogated properly as I could see other components in the conversation context from before the redirect.
Is this intended behaviour? Could redirect.execute() flush the conversation context?
I noticed that DebugPageHandler does the same thing.
Cheers.
Mike.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4038090#4038090
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4038090
19 years, 1 month
[JBoss Seam] - Re: Problems Starting Page Flows
by Delphi's Ghost
Regarding pageflows from the pages.xml file, are you using the generic catch-all "*' view id and assigning outcomes to pageflows? i.e.
| <page view-id="*'>
| <navigation>
| <rule if-outcome="startWizard">
| <begin-conversation pageflow="wizardFlow"/>
| </rule>
| </navigation>
| </page>
|
|
or do you put the begin-conversation tag on the "wizardPage1" page information :
| <page view-id="wizardPage1.xhtml">
| <begin-conversation pageflow="wizardFlow"/>
| </page>
|
|
I'm just wondering since the first method allows global navigation based on the outcome of startWizard from any method. The second requires you to always navigate to the wizardPage1.xhtml page in order to start the wizard page flow. In the event of the name of first page page of the wizard changes, means you have to replace it everywhere.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4038087#4038087
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4038087
19 years, 1 month
[JBoss Seam] - Seam Conversation Should Be Flexible but NOT
by app4you＠yahoo.com
After implemented a full blown application using Seam 1.1, my experience on Seam comes to a mix, really and seriously. Why? Here are my reasons why:
anonymous wrote :
|
| * Maintaining the session timeout, say 30 minutes
|
| * Maintaining the EJB3 timeout
|
| * Maintaining the application component conversation timeout
|
| * Live development in Eclipse using Tomcat plug-in for quick monkey-do-monkey-see will crash Tomcat server. If you modified a Java file then Tomcat will automatically updates the changes ====> crashed most of the time
|
| * Conversation timer should be flexible to turn on/off. Say if your application requires that the application form has to be in the edit mode all time unless user clicked on the Done button. If you want to conversation to end at the same time as the http session timeout, then you have to set the conversation timeout to equal to the HTTP session timeout, 30 minutes, you are asking for bog down - too many sessions. Otherwise, say while the user is looking at the data report for 5 minutes then she tries to fix something on application entry form, boom! Conversation is timed out, redirected to the home.faces. This is bad!!! Imagine that you have the tree and tab interfaces and the application has tons of modules, unless your application is simple like the Hotel demo app.
|
| * Seam's security is not sufficient enough to protect all the resources besides the component classes and the XHTML files, like the standard J2EE Form-based Authentication or ACEGI. If ACEGI or custom filter is used, Seam's conversation stack will kick in (from my experience here) very unpredictable.
|
|
My thoughts are Seam has simplified the development ALOT, but its conversation is not really ready for prime for those medium/big sized applications. If only Seam is flexible enough on its conversation setting to allow it to be on/off, then it will be more suitable. Remember that most of the applications' requirements don't NEED separate conversational workspaces at all. Why can't I turn off the conversation timer like Spring application for instance.
If you have any advice, comment or suggestion on how to stop the conversation timer or how to turn it on/off, please share. Otherwise, people like me is a bit hesitated for using Seam for any later projects.
Thank you.
John
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4038081#4038081
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4038081
19 years, 1 month