Good point about the size of the facelets work. Simon, is there part of
the facelets work that we could pick up for you guys? We're looking to
help out where our efforts would be most useful instead of just grabbing
random issues to work on.
I agree for the most part about your proposed contents for an alpha
release. I would also like to stress the importance of regression
testing with JSF 1.1/1.2 apps as part of any alpha release.
-Mike
[email protected] wrote:
I'm currently working on the annotation processing stuff
(@ManagedBean, @ManagedProperty...). Already made a first attempt for
the managed beans, but there is still some work to do (converters,
components, event listeners, etc). I hope I can apply the same logic
for those other components as well.
With Werner working on Ajax and Simon on Facelets, we already cover a
large portion of JSF2. Facelets is big, though, since it also contains
tags for all components, EZComp, JSF2-Facelets/Original-Facelets
switching, etc... Resource handling/relocation is also a mandatory
requirement for Ajax to work.
But I think an alpha release should at least contain these essential
JSF2 components: AJAX, Facelets, annotation based configuration. I
think those components are the base of the JSF2 work. Adding in other
features should not be too hard when those three are in place properly.
About Shale-test, is it right to use Shale classes in MyFaces Core? Of
course it's just the unit tests, but in some way it's still a cyclic
dependency which is usually a bad thing...
/Jan-Kees
