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

[Max Rydahl Andersen]

Alexey Kazakov wrote:
> Hello Gurkan,
> 
> If we use RHDS JSF Project Wizard and RHDS JSF 1.1 Templates with JBoss 4.2 Runtime
> then we add:
>  <context-param>
>   <param-name>org.jboss.jbossfaces.WAR_BUNDLES_JSF_IMPL</param-name>
>   <param-value>true</param-value>
>  </context-param>
> into Web.xml
> It allows us to run JSF project with bundled implementation.
> In this case we can deploy and run JSF 1.1 project via RHDS.
> I see some exceptions in JBoss console but it seams project works.

there shouldn't be exceptions ... ;(

m/ax

> 
> 
> Monday, July 16, 2007, 2:29:56 PM, you wrote:
> 
>> In WTP JSF project, you can create JSF library with wizard, then
>> add jsf-runtime you wish and use it. But it also provides
>> default runtime, while creating the Dynamic Web Project with JSF facet.
> 
>> Maybe exadel could do this;
> 
>> Gurkan
> 
>> ----- Original Message ----
>> From: Max Rydahl Andersen <max.andersen at redhat.com>
>> To: Igor Shabalov <ishabalov at exadel.com>
>> Cc: jbosstools-dev at lists.jboss.org
>> Sent: Monday, July 16, 2007 1:21:24 PM
>> Subject: Re: [jbosstools-dev] JSF 1.1.0.1 Reference Impl vs JSF 1.2
> 
>> 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?)
>>>
> 
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
> 
> 
> 
> 
> 
>>      
>> ____________________________________________________________________________________
>> Shape Yahoo! in your own image.  Join our Network Research Panel
>> today!   http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7 
> 
> 
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
> 
>