>> So by backward compatibility, you mean that people ought to be able to take >> a faces 1.2 jar, drop it into their application and it will run without >> recompiling the application code? > > Yep. Or, rather, that you should take an application > built with JSF 1.1 or use a component library built against > JSF 1.1, drop it into a appserver that contains JSF 1.2, > and run.
Hmm. Seems an awfully restrictive definition of backwards compatibility to me. I still think that in this case, the API is broken, and ought to be fixed, even if it means breaking backwards compatibility. Sure, it's a good goal to make new versions backwards compatible, but it should never get in the way of fixing problems. Don't you think in this case it is better to get it right? -- Colin Sharples CAUTION - This message may contain privileged and confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message you are hereby notified that any use, dissemination, distribution or reproduction of this message is prohibited. If you have received this message in error please notify Bank of New Zealand immediately. Any views expressed in this message are those of the individual sender and may not necessarily reflect the views of Bank of New Zealand.
