If you can manage to add this feature by only deriving and extending some special classes I do not see a problem. Place your additions into the  "components and extensions" src tree. This way there will be no interfere with the standard 1.1 implementation and we could easily migrate this code into JSF 1.2 code later.
-Manfred

On 4/19/05, Sean Schofield <[EMAIL PROTECTED]> wrote:
What about the 1.2 changes that do not conflict with 1.1?  For
example, encryption of the client-side state.  Does it make sense to
implement those features now as long as they don't interfere with the
1.1 TCK?  That one in particular I have been thinking about for a
while so I was glad to see it added to the spec.

sean


On 4/18/05, Craig McClanahan <[EMAIL PROTECTED]> wrote:
> On 4/18/05, Sean Schofield < [EMAIL PROTECTED]> wrote:
> > With the 1.2 spec nearing finalization what are the plans for TCK?
> > Would we try to certify MyFaces against 1.1 or 1.2?  If we are going
> > for 1.2 that is a ways off but on the other hand, we could start
> > thinking about implementing some of the stuff in 1.2 that is also
> > going to be implemented in the RI version.
> >
>
> As there hasn't been any implementation work on the 1.2 changes yet,
> I'd certainly recommend going for 1.1 certification in the short term.
>  That would be what people are using today.
>
> Craig
>

Reply via email to