[Richfaces-exadel] Re: [seam-dev] Re: ViewExpiredException
gavin at hibernate.org
Fri Mar 7 23:46:52 EST 2008
I think it is time we dropped support for JSF 1.1 in new versions of RichFaces.
People who need to use JSF 1.1 can continue to use the current version
I'm sure there are many code quality issues in the Richfaces codebase
that relate to the 1.1 support.
So lets drop it.
On Fri, Feb 22, 2008 at 6:00 AM, Alexandr Smirnov <asmirnov at exadel.com> wrote:
> I have got a lot of times to understand JSF 1.2 implementation code.
> As I guess from code, JSF 1.2 detect ViewHandler / StateManager version
> from faces-config.xml DTD/XML schema name. We can't switch RichFaces
> 3.1.x configuration files to a JSF 1.2 format, as far as it will
> completely break JSF 1.1 compatibility.
> Fortunately, there is workaround for a SUN RI framework. Just put :
> into application web.xml. It will switch framework to a JSF 1.2 behavior.
> Christian Bauer wrote:
> > On Feb 20, 2008, at 20:06 , Pete Muir wrote:
> >> There is a big difference between nightly builds and a beta. A beta
> >> means that you have done some basic QA on the build and made sure it
> >> runs. And also that Alex isn't in the middle of a big refactor (which
> >> is what happened last time I tried to use a RF 3.2 nightly)
> >> On 20 Feb 2008, at 18:32, Sergey Smirnov wrote:
> >>> You can start to test at any time with 3.2.0 nightly builds. The QA
> >>> period (releasing CRs) will start at the beginning of March.
> > Sorry to interrupt you guys arguing about version numbers, but we have
> > two production sites now that suffer from this bug. What we need is an
> > _immediate_ fix ported to the current stable version. And I mean this
> > week.
> Richfaces-exadel mailing list
> Richfaces-exadel at redhat.com
gavin.king at gmail.com
More information about the seam-dev