Atleprange,
Watch out for the performance I would say
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4038397#4038397
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4038397
___
Just a short comment: i had the similar issues you mentioned, as I also was
risking an huge growth of un-ended conversations. (But my application requires
multiple parallell windows.)
I was overwhelmed by the possibilites that the conversation context gave me
that i started to see almost every u
Atleprange,
Yes, I did all of your mentioned methods. Otherwise, you think I could get it
done :).
For tree component, I was using Apache Tree2. The weird thing is the
combination of AJAX4JSF won't work well with the . I had to use
instead. Now for ending the a form's conversation when use
If you set the conversation id manually, you can control the number of
conversations created. (The side effect is that you might rejoin the
conversation even if you don't want to.)
You could also be sure to end conversations whenever a new treenode or tab is
clicked. That way you only have one
"[EMAIL PROTECTED]" wrote : Did you read my post carefully yet :)
Yes, I have read it several times - I want to understand what you want/what
your issues so we can try to make your apps work better with Seam. You are
using a common paradigm for a user interface - one that you say Seam doesn't
anonymous wrote :
| -> SESSION scope is never a good implementation unless you have a very good
reason to go for,
|
| Yes, you shouldn't put data that doesn't need to be session scoped into the
session. But if your spec says that you need session scope views then...
Did you read my post
If your spec calls for session scoped atomic "conversations" (here I mean a
dialog between the user and the application then thats what you have to give.
Of course Seam's CONVERSATION scope also gives you browser window isolation.
View the original post :
http://www.jboss.com/index.html?module
"[EMAIL PROTECTED]" wrote :
| -> SESSION scope is never a good implementation unless you have a very good
reason to go for,
Yes, you shouldn't put data that doesn't need to be session scoped into the
session. But if your spec says that you need session scope views then...
anonymous wrote :
Petemuir,
anonymous wrote : I don't quite get what you are after here. You want to have
it so that conversations can never timeout? Then it's just SESSION scope (but
admittedly isolated)...
-> SESSION scope is never a good implementation unless you have a very good
reason to go for, neither a
So you're asking for something like @Begin(timeout=ms)?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4038097#4038097
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4038097
___
anonymous wrote :
| * Maintaining the session timeout, say 30 minutes
|
| * Maintaining the EJB3 timeout
|
This is a pain:
http://jira.jboss.com/jira/browse/EJBTHREE-788
"[EMAIL PROTECTED]" wrote : * Live development in Eclipse using Tomcat plug-in
for quick monkey-do-monkey-see wil
11 matches
Mail list logo
