After updating seam jars to current CVS, I'm hitting the same pb ...
Anybody solved that one ?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4072008#4072008
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4072008
You need to do an ant clean build. You should always do this before reporting
problems with CVS.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4072012#4072012
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4072012
First of all, thanks for the replies!
I'm also not convinced that my problems are based on ajax configuration,
since I removed them all from the xml's.
If I change the delegate member accessibility to protected, the error goes away
(There comes a different error for me though which I did not
I rebuild from the start my project with seam-gen, and now it's ok.
So it must be a mess with an old library or some configuration parameter...
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4069181#4069181
Reply to the post :
Read the seam2migration.txt file that is in the root of the Seam distribution.
One of the lines there states:
* remove the Ajax4JSF filter and mappings
When I followed that migration guide my app was fine (apart from problems with
conversations that is still outstanding.)
Cheers,
Damian.
After updating one hour ago, I get now the same exception.
I don't think it's about declaration of Ajax4JSF filter in web.xml as:
- i was already working with Seam 2 cvs but updated may be 10 days ago
- there is no Ajax4JSF filter in the project web.xml, and this since i work
with seam 2
So...
Yeah, I hit the same thing not long ago. Look carefully at the package names:
tried to access field org.jboss.seam.web.Ajax4jsfFilter.del
| egate from class org.jboss.seam.ui.filter.Ajax4jsfFilter.
I don't remember the exact fix, but I think it was that I referred to the wrong
filter in one