-
1. Re: conversation ended unexpectantly
constantin.cash Nov 5, 2007 5:53 PM (in response to gothmog)If you using ajax4jsf, use queue. If simulate a queue.
Or use stateless beans, you stateful session beans are not thread save. -
2. Re: conversation ended unexpectantly
gothmog Nov 5, 2007 5:58 PM (in response to gothmog)ok, I'm using richfaces and simple pojos, no SLSB or SFSB. How does queue work?
-
3. Re: conversation ended unexpectantly
constantin.cash Nov 6, 2007 5:10 AM (in response to gothmog)http://labs.jboss.com/file-access/default/members/jbossrichfaces/freezone/docs/devguide/en/html/RichFacesComponentsLibrary.html
some of tags have a attribute "eventsQueue" -
4. Re: conversation ended unexpectantly
gothmog Nov 6, 2007 3:22 PM (in response to gothmog)I came across that, but it doesn't really make any sense to me
Name of requests queue to avoid send next request before complete other from same event. Can be used to reduce number of requests of frequently events (key press, mouse move etc.)
Are there any examples floating around on how to use this feature? -
5. Re: conversation ended unexpectantly
pmuir Nov 8, 2007 11:06 AM (in response to gothmog)I wrote this up in the Seam docs for Seam2. Take a look, it mostly applies to Seam 1 as well.
-
7. Re: conversation ended unexpectantly
tim_ph Nov 8, 2007 11:28 AM (in response to gothmog)Now, that explains it. I've been working around this problem for a long time. Finally, figure out eventsQueue is the only thing that helps. Not 100% though. These actions are just update and validate field data, but result has got into timeout almost every time unless you enter a value, sip some tea, then hit the button.
I just read the new document. That definitely will help.
Thanks, Pete.