[Richfaces-exadel] Re: [seam-dev] Re: ViewExpiredException

[Gavin King]

OK, thanks.

On Sun, Mar 9, 2008 at 9:11 PM, Pete Muir <pmuir at redhat.com> wrote:
> RF 3.2 drops support for JSF 1.1.
>
>
>
>  On 8 Mar 2008, at 05:46, Gavin King wrote:
>
>  > 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
>  > of RichFaces.
>  >
>  > 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 :
>  >>   <context-param>
>  >>   <param-name>com.sun.faces.disableVersionTracking</param-name>
>  >>   <param-value>true</param-value>
>  >>   </context-param>
>  >>  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
>  >>  https://www.redhat.com/mailman/listinfo/richfaces-exadel
>  >>
>  >
>  >
>  >
>  > --
>  > Gavin King
>  > gavin.king at gmail.com
>  > http://hibernate.org
>  > http://jboss.com/products/seam
>  > http://in.relation.to/Bloggers/Gavin
>
> > _______________________________________________
>  > seam-dev mailing list
>  > seam-dev at lists.jboss.org
>  > https://lists.jboss.org/mailman/listinfo/seam-dev
>
>  --
>  Pete Muir
>  http://www.seamframework.org
>  http://in.relation.to/Bloggers/Pete
>
>
>
>
>



-- 
Gavin King
gavin.king at gmail.com
http://in.relation.to/Bloggers/Gavin
http://hibernate.org
http://seamframework.org