[jbosstools-dev] JSF 1.1.0.1 Reference Impl vs JSF 1.2

[Max Rydahl Andersen]

Igor Shabalov wrote:
> 4.2.0 have JSF 1.2 under the hood by default. It is not expected to be compatible with any JSF 1.1 templates.
> 
> We need some way to prevent deploying incompatible projects. I'd love to throw JSF 1.1 away completely, but I suspect
> that users of 4.0.5 will not appreciate such radical solution.

> Any ideas?

Isn't that was project facets are for in WTP ?

There the runtime tells you what it can actually support.

/max

> 
> -----Original Message-----
> From: jbosstools-dev-bounces at lists.jboss.org [mailto:jbosstools-dev-bounces at lists.jboss.org] On Behalf Of Marshall
> Culpepper
> Sent: Thursday, July 12, 2007 3:22 PM
> To: jbosstools-dev at lists.jboss.org
> Subject: [jbosstools-dev] JSF 1.1.0.1 Reference Impl vs JSF 1.2
> 
> Hey guys..
> 
> I've been running through a demo I'm going to give tonight at a local 
> JBoss User Group meeting, and I noticed some strange behavior with our 
> JBoss 4.2.0.GA and using the "JSF 1.1.0.1 Reference Impl" configuration 
> from the new JSF project wizard.
> 
> Basically, whenever the jsf project is deployed to my clean copy of 
> JBoss 4.2.0 , lots of exceptions show up (though the application itself 
> seems to work fine). When I start changing things from their default 
> configuration (I'm using the kickstart as a quick startup for the demo), 
> JBoss consistently throws exceptions until I hard undeploy/deploy the 
> app from the App Server.
> 
> On the other hand, if I select a "JSF 1.2" configuration in the wizard, 
> the project deploys/redeploys with no errors, and seems to work without 
> a hitch with any changes I make. I guess what I'm getting at is -- if 
> we're going to use JSF 1.1.0.1 Reference Implementation as the "default" 
> selection in the new JSF project wizard, shouldn't we be testing it's 
> "noiseyness factor"?. Would it be a problem to have JSF 1.2 selected as 
> default (or maybe another configuration that JBoss 4.2.0.GA likes?)
>