Hi Adam,
I would recommend taking a look at JBoss Seam, which solves many (possibly all) of these issues. Enjoy, and don't give up, Daniel. _____ From: Simon Lessard [mailto:[EMAIL PROTECTED] Sent: Tuesday, 12 December 2006 2:11 AM To: MyFaces Discussion Subject: Re: JSF is the answer? I don't think so... Hello Adam, Most of those problems can be handled by other frameworks complementary to JSF. JSF was not made specifically, nor only, for transaction based application. All the problems you're mentioning are linked to stateful applications. There're many solutions then, like container managed transaction for example. You can give a look to what Hibernate, Spring, EJB 3 and such have to offer for some/all of the issues. JSF works great with any of those technologies. Regards, ~ Simon On 12/10/06, Adam Koprowski <[EMAIL PROTECTED]> wrote: Hello, Approximately one year ago, together with my colleague, we had to make a decision what technology to use for the development in some project of ours. At the time, after quick investigation, we came up with the idea of using J2EE, that is EJB + JSF. Let alone the EJB but let me share with you some thoughts that I have about JSF after this year of work with it. Below you will find a mixture of features (that I would expect any decent web framework to support) and problems (that I would expect any decent framework to solve and let developer not worry about it). Here we go: -) use of browser back button, -) page bookmarking, -) double form submission (by double user click), -) opening link in new browser tab/window, -) having multiple copies of a page/service in different browser tabs/windows Now, correct me if I'm wrong, but I think all of the above pose some (lots of?) difficulties in JSF. And I know that some of those are not easy issues (like browser's back button) but personally I think this list is way too long... I don't really know any alternative web frameworks so I cannot compare but is it really that the developer has to deal with all of those issues on his own? Or are there frameworks where one does not need to worry about those irritating problems and can concentrate on real development... and JSF is just too immature to provide that? I know this is not a myfaces specific question but I decided to post this provocative question on this list as I'm curious about your opinion guys... Best wishes, Adam Koprowski -- ===================================================== [EMAIL PROTECTED] , ICQ: 3204612 http://www.win.tue.nl/~akoprows <http://www.win.tue.nl/%7Eakoprows> The difference between impossible and possible lies in determination (Tommy Lasorda) =====================================================
