Oops. I didn't notice you specifically asked Christian to file the issue until
after I created it. :) Anyway here you go:
http://jira.jboss.org/jira/browse/JBSEAM-1281
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4042458#4042458
Reply to the post :
Hehe :) I've closed one of them as duplicate
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4042460#4042460
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4042460
___
jboss-user
Figured it out. The Ajax4jsf filter was executing after the seam filter. I
had my filters configured like so:
|filter-mapping
| filter-nameajax4jsf/filter-name
| servlet-nameFaces Servlet/servlet-name
| dispatcherREQUEST/dispatcher
|
I ran into this as well and found quite a few other postings about a broken
filter configuration. We should move away from web.xml, it's just pain. Maybe
we can make the a4jsf filter a Seam AbstractFilter and run it first if the
component is on the classpath? Then we wouldn't need a4jsf
Ok, so I got a build working today and I'm still experiencing the problem.
Maybe I'm just using seam wrong but here are some more details on what I'm
doing.
I have a list detail page. I'm storing the current page the user is on in a
conversation bean.
I begin a conversation in the list
For some reason this tool blanked out my redirect tag in the navigation-case.
Believe me it is there. :)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4041917#4041917
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4041917
Mike, what version of Seam are you running? CVS head is running on the RI now,
and I've not *seen* any problems propagating conversations across redirects
with it.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4041513#4041513
Reply to the post :
I'm getting the problem using a head build from about 2 weeks ago. I tried a
new build as of right now but there is a problem with a JSP 2.1 dependency.
JBSEAM-1265.
If you're not having any trouble I'll try again when the when JBSEAM-1265 is
fixed.
Mike
View the original post :
