> But for developing lower traffic, "intranet" style business apps (workflow > management, HR tools, etc) it's actually very good.
Perhaps, I would still go with GWT for that class of apps. Much faster, less XML and a component library that kicks tail. > And attracting the > Visual basic, "business" developer to Java via JSF's ease of use and slick > components was a big part of why JSF was created. I've developed internal > usage business apps at several different major .com (as well as Sun itself!) > using JSF but agree you would never dare to build a serious internet facing > application with it... I don't believe it was ever intended for that or that > the JSF lifecycle would scale. JSF should come with a warning label "...may cause depression, insomnia and other side effects. Contact your local JUG to see whether JSF is right for you". /Casper --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
