Quoting Matthias Wessendorf <[email protected]>:

+1
doesn't hurt to have our app/framework working with both (see [1]).

I totally agree. You should make sure your app always runs with either JSF impl so that you can switch based on which impl runs your final app better.


Actually even if you prefer one over the other, different containers
may ship different JSF implementations.

I have to pipe up and toot my own horn here. JBoss AS6 now ships with three JSF implementations. Changing to a different impl is just a matter of changing a single param in your web.xml or a single param in the main JBossWeb configuration file.

http://jsfunit.blogspot.com/2010/12/jsf-on-jboss-as6-final.html

Would be kinda odd if your tool does only support one.

Once our are able to use both, I'd suggest to collect some (perf)
stats, to measure/test your needs.

-Matthias

[1] http://markmail.org/message/2ts6xjrkw3x4mhdm

On Thu, Jan 20, 2011 at 12:40 PM, Werner Punz <[email protected]> wrote:
Am 20.01.11 12:14, schrieb Agam Dass:

Hi,
We are also using myfaces for JSF 1.2 reference implementation in our UI
framwork project. Now we have a push that we should replace it with
Mojarra project implementaion. What do you suggest about these two
implemenations w.r.t. JSF 2.0.

Best bet is to make your ui framework work on both impls and if you run into
bugs where one thing works while the thing on the other does not
then please immediately post a bugreport so that we can fix it.
That way you can switch over to one impl or the other as the need arises
(which is often imposed by management not by quality criteria)

The implementors on both impls work hard to deliver a solid experience, so
it is hard to tell which implementation is the better, of course I am biased
in favor of myfaces naturally, but you will get the answer towards Mojarra
in a mojarra centric forum.

I personally think that both implementations of JSF 2.0 are by now pretty
mature so it is really hard to give an preferences here for one of those.


just my 2c

Werner






--
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf






Reply via email to