On 5/10/06, Mike Kienenberger <[EMAIL PROTECTED]> wrote:
On 5/10/06, Adam Winer <[EMAIL PROTECTED]> wrote:
> > I think we'll want to make it a separate jar and project because
> > facelets depends on JSF 1.2 RI and the Glassfish EL jars. And maybe
> > JSP 2.1 as well. Those don't need to be dependencies for standard
> > tomahawk use.
>
> FYI, it doesn't depend on the JSF 1.2 RI, and it *definitely*
> doesn't depend on JSP 2.1 (or anything in JSP, for that matter).
> It does require a javax.el implementation; I don't remember offhand
> if it's hardcoded against the Glassfish implementation or if
> that's pluggable.
Adam,
When I was working on custom components for the Optional Validation
Framework, I had issues with dependencies on
javax.servlet.jsp.tagext.Tag. I went back and reviewed the project,
but I couldn't duplicate the issue -- I'm probably misremembering the
root cause and was due to JSP tags instead.
However, com.sun.facelets.tag.jsf.ComponentHandler references
javax.faces.component.ActionSource2 (a dependencies on the JSF 1.2
api). I thought for sure that this was causing a compile-time
dependency, but again I can't repeat the problem.
I should clarify: there's definitely a compile-time dependency
on JSF 1.2. But I got Jacob to make it so that it's compile-time
only, and there's no runtime dependency.
-- Adam
In that case, I'd prefer option 1!
