You may want to look at:
http://www.jboss.com/index.html?module=bbop=viewtopict=97618
If its the same issue, it has been fixed in CVS
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4003115#4003115
Reply to the post :
Thanks for the quick response.
Created Jira 618
http://jira.jboss.org/jira/browse/JBSEAM-618
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3995128#3995128
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3995128
Just some more clarification. The method that is cleaning up timed out
conversations is:
org.jboss.seam.core.Manager.endRequest(ContextAdaptor session)
Specifically the line: Manager.instance().conversationTimeout(session);
Line number 347
View the original post :
Ok. I think I found the problem in the class:
org.jboss.seam.interceptors.RemoveInterceptor
The line (77):
getComponent().getScope().getContext().remove( getComponent().getName() );
Will remove a bean with the specified name from the conversation associated
with the current thread.
The
My intended usage of remoting is a single conversation for my entire page
experience.
In the Seam documentation, it says:
anonymous wrote : If you are working with just a single conversation, then you
don't need to do anything special. (regarding setting the conversation id).
Therefore I
Forgot to mention I am using Seam-Version: 1.1.0.GA
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3994543#3994543
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3994543
___
I think I may have finally figured out the answer (this has been bothering me
for a few days, but of course I figure it out right after I post).
The application server reloaded my application, and I didn't refresh the page.
Therefore I am requesting an invalid conversation id.
Hopefully this
I am using Seam heavily on my latest project, especially the remoting.
One question I am having trouble finding a concrete answer to is the best
practices regarding 'timeout's of various components.
Please correct me if I am wrong, but I understand there to be three components
whose timeouts
I am using Jboss Seam 1.1 CR2.
With regards to remoting, when attempting to call a method that is overloaded
(one version has 2 arguments, the other 3 arguments) I recieve the error
call.callback is not a function in line 693 of remote.js.
When I change the method signature of the 3 argument
The seam examples ship with a web.xml that references servlet 2.5. I had to
downgrade this declaration in order to get JSTL to work.
Anybody else had to do this? I am surprised that the Seam examples ship with a
servlet 2.5 declaration, when JBoss 4.0.x that uses Tomcat pre 6.0 doesn't
10 matches
Mail list logo
