[jboss-user] [JBoss Seam] - Re: How to control end of conversations/state of stateful be
It depends on the use case - if the user is navigating away, I don't think ending the conversation is what you want to do (take a look at how seamframework.org works). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4125919#4125919 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4125919 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: How to control end of conversations/state of stateful be
The problem I find when setting propagation="none" on my navigation links is that the conversation is not ended and is maintained on memory untill it expires. Wouldn't it be better to set propagation="end"? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4125180#4125180 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4125180 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: How to control end of conversations/state of stateful be
"[EMAIL PROTECTED]" wrote : My tip is to avoid starting conversations from navigation links (those links that take you to other areas of the app), always make navigation disable conversation propagation, and just use conversations *within* each area of the app.Excellent tip! Thank you very much, Pete. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4118907#4118907 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4118907 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: How to control end of conversations/state of stateful be
Pete, Thanks for not taking my post harshly as it wasn't meant to be as such. I, for one, am extremely appreciative of what all of you are doing to evolve Seam and to engage the end-user as much as possible, through these forums and elsewhere. We *had* been setting propagation="none" on most navigation links and just recently started to think that we actually *shouldn't* be doing this. So hearing from you that this is indeed something that should be set (to "none") helps greatly. It is tips like these that could be really helpful to people struggling to grasp ho how to use conversations. Looks like the new Wiki will be a good source for this kind of information. I'll take a look at the example itself as well. Thanks! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4118891#4118891 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4118891 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: How to control end of conversations/state of stateful be
Chris, Interesting post. Thanks for the feedback. We do have one large scale app written in Seam in the examples dir - the wiki example which is the basis of the new Seam community site (which is up and running). The problem with large example apps is that they are hard to understand which makes them bad examples! Before moving to JBoss I did work on a fairly large app with Seam using conversations, and had no real problems with conversation management. I've also seen apps use conversations well in support cases and when consulting. My tip is to avoid starting conversations from navigation links (those links that take you to other areas of the app), always make navigation disable conversation propagation, and just use conversations *within* each area of the app. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4118867#4118867 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4118867 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: How to control end of conversations/state of stateful be
I think part of the problem here is that outside of a few, small example applications provided by the gracious Seam team, there are no true examples of a large, enterprise-level application properly using Seam conversations. Seam is so closely coupled with conversations that there is no true way of escaping them. Yet the amount of confusion over how to manage them in an Web environment where the user is truly allowed to go anywhere, do anything, start any process and end it at any time, should point out to the Seam team that *are* issues with conversations in general. They're a great idea - but I know we're struggling with their usage. Results are unpredictable at best. The authors of Seam documentation attempt to show its great value but in practice it is hard to come by. Try using breadcrumbs based off of Seam conversations - I'll tell you upfront that it simply will cause more headaches than it is worth in a system with many pages and processes. I think there needs to be a definitive, large-scale example on how to manage conversations in an enterprise application. There is simply too much confusion for this to be ignored. My two cents. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4118845#4118845 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4118845 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: How to control end of conversations/state of stateful be
"gus888" wrote : "[EMAIL PROTECTED]" wrote : Have you taken a look at the way seam-gen does it? It produces a pageable, bookmarkable search screen that saves the search criteria without using a conversation. | I went through all seam examples, and I found the following search beans: | | 1. booking - HotelSearchingAction: Session bean | | 2. blog - SearchService: default bean | | 3. dvdstore - FullTextSearchAction: Conversation bean with @Begin(join=true) | | 4. wiki - WikiSearch: Conversation bean with begin (join=true) in pages.xml | | | | It seams that the blog-SearchService has bookmarkable but not pagable, but the SearchService only has one searchPattern criteria. The dvdstore and wiki search pages have pageable. Thanks. SeamGen makes a usage of Seam framework, you should take a look at it, it has all the features you asked for and the implementation is very clean, Asaf. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4117276#4117276 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4117276 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: How to control end of conversations/state of stateful be
"[EMAIL PROTECTED]" wrote : Have you taken a look at the way seam-gen does it? It produces a pageable, bookmarkable search screen that saves the search criteria without using a conversation. I went through all seam examples, and I found the following search beans: | 1. booking - HotelSearchingAction: Session bean | 2. blog - SearchService: default bean | 3. dvdstore - FullTextSearchAction: Conversation bean with @Begin(join=true) | 4. wiki - WikiSearch: Conversation bean with begin (join=true) in pages.xml | | It seams that the blog-SearchService has bookmarkable but not pagable, but the SearchService only has one searchPattern criteria. The dvdstore and wiki search pages have pageable. Thanks. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4117211#4117211 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4117211 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: How to control end of conversations/state of stateful be
Have you taken a look at the way seam-gen does it? It produces a pageable, bookmarkable search screen that saves the search criteria without using a conversation. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4117196#4117196 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4117196 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: How to control end of conversations/state of stateful be
"[EMAIL PROTECTED]" wrote : Normally you wouldn't make a search screen conversational. Why do you want to make it conversational? Hi Pete, in fact, I want to make my search screen conversational, because I need to save some search criteria, e.g. searching a classmate, it need to first select a state, then choose a city based on the selected state, select-input school name, input name and begin searching, pagination After finishing searching, the front conversation bean become back-conversation and timeout cleaning after about 5min, or click finish search to end the conversation. Is it correct design, or you may suggest a better search pattern? Thank you. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4117179#4117179 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4117179 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: How to control end of conversations/state of stateful be
"[EMAIL PROTECTED]" wrote : | Normally you wouldn't make a search screen conversational. Why do you want to make it conversational? | I wanted to be able to provide search refinement and result paging/navigation, thus storing per-search state, and allow multiple searches per session. It seemed to me like an ideal candidate for a conversation. Would you suggest a session state or stateless approach as an alternative? "[EMAIL PROTECTED]" wrote : | If you really do want to make it conversational, then you can use in pages.xml | I'm not sure how I could use end-conversation to only end the conversation prior to a new search being performed, and keep the conversation alive for result paging/navigation. Could you give an example? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4117155#4117155 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4117155 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: How to control end of conversations/state of stateful be
"schlafsack" wrote : "[EMAIL PROTECTED]" wrote : | | | * submitting a search query using the button. | | | * navigation forwards though the results using the next link. | | | * navigation backwards though the results using the previous link. | | | | | | | I'd also like the submission of a new query to start a new conversation. Ideally, clicking the button should end the existing conversation and begin a new one. So far I can't see an easy way of doing this. | | Normally you wouldn't make a search screen conversational. Why do you want to make it conversational? | | If you really do want to make it conversational, then you can use in pages.xml, and start a new conversation after the redirect. But I don't think this is the best way to write a search screen. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4117120#4117120 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4117120 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: How to control end of conversations/state of stateful be
"trouby" wrote : My case? I think it's any case with buttons that always exist on the template, | | Lets make an example: | I have a top menu(that is always with visible) with few options, | [my items: a, b, c, d] | | Pressing on one item should start a conversation, as this item is heavily being managed later on. | | I have added a 'done' button with propagation='none' but no one is using it : ) So the menu items should have propagation="none". Why do you need to start a lrc immediately on clicking on the menu item (this is the use case we are interested in, of course you want to be able to navigate away in a freeform way from within another conversation). If really need to start a new lrc from a menu item, set the propagation to none, and start up a new conversation on the destination page using pages.xml. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4117117#4117117 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4117117 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: How to control end of conversations/state of stateful be
"[EMAIL PROTECTED]" wrote : Post your use case for this. If I understand the topic of this thread, I *think* I've come up against a similar problem in the search application I'm writing to learn seam. My application has one page with a text box, a button, a results table and next/previous buttons. I'd like to define a conversation as: | * submitting a search query using the button. | * navigation forwards though the results using the next link. | * navigation backwards though the results using the previous link. | I'd also like the submission of a new query to start a new conversation. Ideally, clicking the button should end the existing conversation and begin a new one. So far I can't see an easy way of doing this. With a simple @Begin attribute on the search method, performing a second search throws an exception - which is expected, we are already in a conversation. Using @Begin(join=true) does not meet the requirement of starting a new conversation per search. I could add a clear button that calls an @End attributed method but this is does not really meet your average user's expectations of a search tool. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4117080#4117080 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4117080 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: How to control end of conversations/state of stateful be
"[EMAIL PROTECTED]" wrote : "trouby" wrote : Well, sorry for being so annoying but I still don't get the point, If I have buttons that should start a conversation, propagation='none' is not an option | | Normally I find that you don't want to start a new conversation whilst another one is running. Post your use case for this. My case? I think it's any case with buttons that always exist on the template, Lets make an example: I have a top menu(that is always with visible) with few options, [my items: a, b, c, d] Pressing on one item should start a conversation, as this item is heavily being managed later on. I have added a 'done' button with propagation='none' but no one is using it : ) Pressing on another item(from the menu) in the middle of the current long running conversation causes the error, I solved it by 'joining' to the current conversation just to fix the error but this is not too logical as the last selected item is not being managed by the user anymore. Thanks. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4117020#4117020 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4117020 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: How to control end of conversations/state of stateful be
"trouby" wrote : Well, sorry for being so annoying but I still don't get the point, If I have buttons that should start a conversation, propagation='none' is not an option Normally I find that you don't want to start a new conversation whilst another one is running. Post your use case for this. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116372#4116372 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116372 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: How to control end of conversations/state of stateful be
"trouby" wrote : So if the same method that is annotated with @begin is invoked within the same bean -instance- a new conversation is created without exception? No, this is not true. anonymous wrote : what's the difference between a new conversation starting from the same bean instance or from different bean instance? why the behavior is different? There is no difference, if there is, it is a bug. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116370#4116370 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116370 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: How to control end of conversations/state of stateful be
"gus888" wrote : No, you didn't do anything wrong. As I posted above, the
@Begin in booking example always was invoked in the same bean ("hotelBooking"),
so no exception thrown.
What Seam component conversation demarcation is expressed in has no effect on
conversation boundaries or behaviour.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116369#4116369
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116369
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: How to control end of conversations/state of stateful be
"trouby" wrote : I still don't get it, what about links that -should- start a new conversation? is it possible to combine begin/end annotations together for the same method? like ending the current conversation and starting a new one? Yes, but you have to end the current conversation before a redirect, and start a new conversation after a redirect (you can do this from pages.xml or from annotations). I've not seen a great use case for this though. anonymous wrote : btw, I have a seam link which invoke an method that is annotated with @Begin, invoking the same link just after the first invocation throws "begin method invoked from a long-running conversation, try using @Begin(join=true)", so what should I do in such situation?? I don't want -another- conversation to start in this case, If you want to join the current conversation, use join=true, otherwise, design your app so the use can't be on that page when a long running conversation is in progress. anonymous wrote : I guess I'm doing something wrong, as in seam booking example the 'setHotel' is annotated with @Begin and can be invoked many times without this exception, Yes, because you can't be on the page which calls this method and inside a long running conversation. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116366#4116366 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116366 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: How to control end of conversations/state of stateful be
Alright, Well, sorry for being so annoying but I still don't get the point, If I have buttons that should start a conversation, propagation='none' is not an option, big part of my buttons start a new conversation, so no matter what, I find myself adding join=true, at least for these buttons, But as it seems most of the people are comfortable with it, I still find it really confusing and not exactly correct, What I think is that it might be useful to have an option to end/start a new conversation on the same method/link/etc... Asaf. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116268#4116268 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116268 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: How to control end of conversations/state of stateful be
"trouby" wrote : what's the difference between a new conversation starting from the same bean instance or from different bean instance? | I think that they are the same. Both of them create new conversations with new ids. "trouby" wrote : | why the behavior is different? | I think that this is a Seam bug according to Michael Yuan's JBoss Seam book P114. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116258#4116258 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116258 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: How to control end of conversations/state of stateful be
So if the same method that is annotated with @begin is invoked within the same bean -instance- a new conversation is created without exception? what's the difference between a new conversation starting from the same bean instance or from different bean instance? why the behavior is different? Asaf. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116217#4116217 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116217 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: How to control end of conversations/state of stateful be
"trouby" wrote : I guess I'm doing something wrong, as in seam booking example
the 'setHotel' is annotated with @Begin and can be invoked many times without
this exception
No, you didn't do anything wrong. As I posted above, the @Begin in booking
example always was invoked in the same bean ("hotelBooking"), so no exception
thrown. If you change "hotelSearch" bean to CONVERSATION, then add @Begin in
find() method, you will get the exception you mentioned. In the book of JBoss
Seam (Michael Yuan) P 114, it also states that as long as you invoke new @Begin
or even have a coding error (forgot @End), the current conversation will time
out. I think it should not work at least in current Seam release.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116215#4116215
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116215
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: How to control end of conversations/state of stateful be
Hey, I still don't get it, what about links that -should- start a new conversation? is it possible to combine begin/end annotations together for the same method? like ending the current conversation and starting a new one? btw, I have a seam link which invoke an method that is annotated with @Begin, invoking the same link just after the first invocation throws "begin method invoked from a long-running conversation, try using @Begin(join=true)", so what should I do in such situation?? I don't want -another- conversation to start in this case, I guess I'm doing something wrong, as in seam booking example the 'setHotel' is annotated with @Begin and can be invoked many times without this exception, Thanks. Asaf. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116212#4116212 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116212 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: How to control end of conversations/state of stateful be
"[EMAIL PROTECTED]" wrote : I don't see why putting propagate=none for all menu type links is a problem...Hi Pete, really, it is not a problem, but what I mean whether it is possible let Seam system to do the propagate=none job for a conversation once a user propagates away from the conversation and starts a new conversation. Thanks. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4115589#4115589 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4115589 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: How to control end of conversations/state of stateful be
This is correct, I don't see why putting propagate=none for all menu type links is a problem... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=411#411 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=411 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: How to control end of conversations/state of stateful be
"[EMAIL PROTECTED]" wrote : "gus888" wrote : For "How to control end of conversations": | | I have the same problem. I think that it is critical issue for the core (conversation) of Seam. The Seam forum here suggested that you use "propagation=none" to all other buttons and links which users can reach and propagate away from the current conversation. I think, maybe I am wrong, that this way is not practicable in a production project. One reason is that maybe there are a couple of dozens links and buttons on screen, | | So this is just laziness? | Hi Pete, First, thank you for your reply. I think that it is not just laziness. The conversation is specifically useful for complicated project, based on Kavin's statements in the tutorial. For a complicated project with top drop-down menus, left bar menus and right bar menus, developers have to put "propagate=none" to **every buttons and links** at every conversation step to prevent users from propagating away from a conversation. Importantly, this way seems that software developers are completely controlled by non-coorporate user's behavior, but based on my little experience, software developers should always control non-coorporate user's behavior. Correct me if I am wrong. Thank you. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4115548#4115548 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4115548 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: How to control end of conversations/state of stateful be
"gus888" wrote : My previous suggestion is that as long as system run a @Begin, system should put current foreground conversation to background (let system timeout clean) and start a new foreground conversation (if the conversation id is automatically created by system). Currently, in the Seam, this functionality only works on the SAME foreground conversation bean, for example, I start a conversation A from Conversation Bean A by clicking @Begin from A, then if I go back to click @Begin from the same Conversation Bean A, Seam will create a new conversation, BUT instead, if I go back to click @Begin from Conversation B, the whole system will throw exception (need @Begin (join=true)) and the system will be down. This is critical problem in a production project. Please correct me if I am wrong. Not really. Clicking back *does not* propagate the conversation. It just takes you back to the page as it was when you were on it before (read about how the back button works). So if you aren't in a conversation on your "start" page, you go into conversation A, then click the back button, you won't be in a conversation, and can start another one. Seam doesn't differentiate between conversations based on what method they are started from. anonymous wrote : I like to create a JIRA if Seam team think it is necessary. Thank you and have a good holiday. I really don't think this is necessary, and would just be (another) thing to learn about Seam. So I'm -1. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4115511#4115511 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4115511 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: How to control end of conversations/state of stateful be
"gus888" wrote : For "How to control end of conversations": | I have the same problem. I think that it is critical issue for the core (conversation) of Seam. The Seam forum here suggested that you use "propagation=none" to all other buttons and links which users can reach and propagate away from the current conversation. I think, maybe I am wrong, that this way is not practicable in a production project. One reason is that maybe there are a couple of dozens links and buttons on screen, So this is just laziness? anonymous wrote : the second is that maybe there are other conversation begin buttons and links on screen. This is application design. If you *have* to start other conversations from that screen look at ending the conversation before redirect. Its perfectly possible to use conversations in an application, you just need to consider the paths the user will take through the application. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4115510#4115510 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4115510 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: How to control end of conversations/state of stateful be
For "How to control end of conversations": I have the same problem. I think that it is critical issue for the core (conversation) of Seam. The Seam forum here suggested that you use "propagation=none" to all other buttons and links which users can reach and propagate away from the current conversation. I think, maybe I am wrong, that this way is not practicable in a production project. One reason is that maybe there are a couple of dozens links and buttons on screen, the second is that maybe there are other conversation begin buttons and links on screen. My previous suggestion is that as long as system run a @Begin, system should put current foreground conversation to background (let system timeout clean) and start a new foreground conversation (if the conversation id is automatically created by system). Currently, in the Seam, this functionality only works on the SAME foreground conversation bean, for example, I start a conversation A from Conversation Bean A by clicking @Begin from A, then if I go back to click @Begin from the same Conversation Bean A, Seam will create a new conversation, BUT instead, if I go back to click @Begin from Conversation B, the whole system will throw exception (need @Begin (join=true)) and the system will be down. This is critical problem in a production project. Please correct me if I am wrong. I like to create a JIRA if Seam team think it is necessary. Thank you and have a good holiday. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4115504#4115504 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4115504 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
