I double checked the code and I don't quite understand how it happens. The part of code dealing with that has not changed since 2.0.0
Can you revert back and see if it happens?
Did you change any other thing in your environment?
degradedto 2.0.0 and everything works fine.
We did however an upgrade on Richfaces to the 3.2.1 - could that be an issue ?
I guess Richfaces should not influence.
Does the dvdstore and blog demo work in your environment?
First, if you are not using Hibernate Search yet, there is really no harm in this message. It is telling you that the Hibernate Search version of the Hibernate Session could not be created, so it just falls back to the regular Hibernate Session. Look further down in the stack trace and see if there is something related to the Hibernate Search instantiation that is failing. My guess is that while it sees the Hibernate Search API, there is another class missing that Hibernate Search needs to load properly.
As a quick explanation, Seam looks to see if one of the classes in the Hibernate Search API is present. If so, it tries to instantiate the Hibernate Search Session Proxy constructor. If that instantiation fails, it just falls back to instantiating the regular Hibernate Session Proxy constructor.