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=bbop=viewtopicp=4125919#4125919
Reply to the post :
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 :
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
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
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
[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,
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.
[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
[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
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
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
[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
[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
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=bbop=viewtopicp=4117196#4117196
Reply to the post :
[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 -
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
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.
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
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.
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
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,
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
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
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?
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
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,
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
[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
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=bbop=viewtopicp=411#411
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=411
[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
30 matches
Mail list logo
