Pete, I posted a tiny little first example of what I am trying to do:
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4085264#4085264
If you could have a look at the open issues I mentioned, that would be great!
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewt
anonymous wrote :
| Specifically: Why do you need join="true" if you just have ended the
previous conversation with propagation="end"?
|
He talked about starting a new one with join=true. The join=true bit ensures
that you don't start a new one each time the page is rendered.
maku01 :
"ASavitsky" wrote : I wouldn't recommend reusing the same conversation in
different areas of the system. Whenever user switches to a different area,
scrap the old conversation and create a new one. You can do it in the same
request, by ending it in the link itself (via propagation="end") and beg
I wouldn't recommend reusing the same conversation in different areas of the
system. Whenever user switches to a different area, scrap the old conversation
and create a new one. You can do it in the same request, by ending it in the
link itself (via propagation="end") and beginning a new one in
"[EMAIL PROTECTED]" wrote : Any seam-gen application uses propagation="join".
|
Maybe, but those have no comments in them, no javadocs and the "The Seam
Application Framework" chapter in the reference does not talk about
conversations either.
Funny things is that even though you always recomm
"[EMAIL PROTECTED]" wrote : ?! It's not different from any of the existing
examples. You need to understand how propagation="none" and propagation="join"
work, and that's it.
|
In my opinion, this statement is really an oversimplification.
I tried to understand the conversation mechanisms an
Any seam-gen application uses propagation="join".
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4081152#4081152
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4081152
___
jbos
Stephen - sure, I'm not really expecting a full example (with nice explanation
text etc.) - but something is better than nothing. At least like this we can
get a better understanding of what you are after. Despite what Christian says,
I do feel we are lacking an example that uses workspace man
Now I, too, feel like an idiot because each example should be showing this, but
I still don't get it after looking at several different examples.
"[EMAIL PROTECTED]" wrote : ?! It's not different from any of the existing
examples. You need to understand how propagation="none" and propagation="jo
?! It's not different from any of the existing examples. You need to understand
how propagation="none" and propagation="join" work, and that's it.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4081084#4081084
Reply to the post :
http://www.jboss.com/index.h
Yes, an example application of this sort would be a great addition to the Seam
examples I think. Does anyone have something they can donate?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4081068#4081068
Reply to the post :
http://www.jboss.com/index.html?mo
That's exactly my use case and I don't have a solution either.
Currently the first version of my app works without using conversations which
of course seems to waste quite a lot of seams value.
A big problem is that _all_ the explanations teach you about the technical
side, e.g. what a conversat
"[EMAIL PROTECTED]" wrote : It is very unlikely that you actually _need_
conversation scope if the user simply navigates into an area. Why do you think
you need it?
The kind of the application is an administration application.
Most of the views should be master / detail views with a list view (
It is very unlikely that you actually _need_ conversation scope if the user
simply navigates into an area. Why do you think you need it?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4080967#4080967
Reply to the post :
http://www.jboss.com/index.html?module=
14 matches
Mail list logo
