If 1.1 is a must then I don't see any way around having 2 trunks. The
API's between the two are not the same and when dealing with things like
decorators (which JSF makes extensive use of), you need to implement
every method on a class and ONLY those methods.
I know that for Trinidad, although 90% of our code base is the same
between JSF 1.1 and 1.2, approximately 10% is not. And that 10% is what
may well force us NOT to use the commons project for things like
Multi-part form handling. Plus, I would like to make some utilities
that would allow renderkits to have an easier time of working with a
JSR-301 portlet environment while allowing the portlet-bridge-api's and
impls to be optional at runtime. Something that could save a lot of
time for render kit developers. These will need to be 1.2 only.
Scott
Matthias Wessendorf wrote:
On Nov 29, 2007 5:57 PM, Scott O'Bryan <[EMAIL PROTECTED]> wrote:
Hey everyone,
I'm going to try to put together a proposal for some items it add to the
jsf commons fairly soon for your purusal. First off, however, I'd like
some technical information on this project as it may effect how the
project is set up.
1. Which version of JSF will be the minimum for this project? One of my
proposals involves needing an ExternalContextWrapper and the version of
JSF does make a difference. I, personally, would like to see this based
off 1.2 but if we need a 1.1 Faces Commons then I would recommend both a
1.1 and a 1.2 branch.
here we go;
my understanding is, that 1.1 is a must
2. What is the minimum JDK we are going to use for this project. My
preference would be J2SE 5 for the build. I could even live with making
sure that code can be compiled with J2SE 5 in 1.4 compatibility mode but
I think we need to be able to support generics at the very least. Of
course if we're basing the commons project off of JSF 1.2, J2SE5 is a
no-brainer. :)
JSF 1.1 => java1.4
JSF 1.2 => JDK5
