Sorry, wasn't clear. JSF is completely optional in Weld, you don't need the JSF
API on your classpath to use Weld.
We do provide optional JSF support inside the jar. Currently this is compiled against JSF
1.2 for maximum compatibility. I want to change this to JSF 2 to (more simply) resolve a
bug in our JSF support. So the question is, does anyone object to dropping JSF 1.2
On 2 Dec 2010, at 11:38, Paul Bakker wrote:
There a quite a few scenarios where weld without JSF make sense:
-alternative web framework (e.g. wicket)
-a service only project (e.g. only JAX-RS)
It would be strange to pull in JSF on those kind of projects. On the other hand it's
all alternative usage of weld, and I'm not sure that's important enough to stop us
from doing this.
On Dec 2, 2010, at 12:30 PM, Pete Muir wrote:
> I am considering compiling Weld against the JSF 2 API. As both JBoss AS and GlassFish
use JSF 2, I don't see any problems there, but wanted to see if anyone would object
who is using Tomcat, Jetty or GAE?
> weld-dev mailing list
Op dit e-mail bericht is de disclaimer van Info Support van toepassing, zie