On 7/29/07, souravm [EMAIL PROTECTED] wrote:
However, I'm still not very sure whether the design approach of Swing/VB is a
right fit for a
scenario where the underlying technology is http. They are good for a thick
client
scenario where most of the event handlings happen in client machine
Sorry, I couldn't resist.
On 7/26/07, souravm [EMAIL PROTECTED] wrote:
Regarding going for JSF due to componentization, I'm again not sure what
additional componentizations JSF does compared to struts. Apart from the fact
that JSF does not need a layer like Action Classes, all other
On Mon, July 30, 2007 9:39 am, Ted Husted wrote:
On 7/29/07, souravm [EMAIL PROTECTED] wrote:
However, I'm still not very sure whether the design approach of Swing/VB
is a right fit for a
scenario where the underlying technology is http. They are good for a
thick client
scenario where most
My comments embedded.
Regards,
Sourav
-Original Message-
From: Frank W. Zammetti [mailto:[EMAIL PROTECTED]
Sent: Monday, July 30, 2007 7:20 AM
To: Struts Users Mailing List
Cc: Struts Users Mailing List
Subject: Re: Is Struts still a better choice over JSF as on today ?
On Mon, July
Hi Frank,
Thanks again for the detailed response.
I think I've got your points. Yes I'm aware of Swing/VB technology and that
analogy helped me a lot to understand the perspective.
However, I'm still not very sure whether the design approach of Swing/VB is a
right fit for a scenario where
Not nearly as good would be my guess :)
--
Frank W. Zammetti
Founder and Chief Software Architect
Omnytex Technologies
http://www.omnytex.com
AIM/Yahoo: fzammetti
MSN: [EMAIL PROTECTED]
Author of Practical Ajax Projects With Java Technology
(2006, Apress, ISBN 1-59059-695-1)
and JavaScript, DOM
Hi Frank,
Thanks again for sharing the anecdotes of those projects which used JSF. I
fully agree with your observations/comments regarding RAD tools. I work for a
software service provider organization and seen the same things happening (for
the projects using RAD tools) many a times.
2007/7/26, Frank W. Zammetti [EMAIL PROTECTED]:
(this was a case of the generated code having to be mucked
with to get it right, and it turned into a big, heaping plate of spaghetti
in the process).
I always wonder what kind of spaghetti have you got outside of Italy :-D
Antonio
Hi Frank,
Thanks a lot for your opinions/inputs. Found it very informative.
For me so far I don't see any reason why people should go for JSF except for
moving ahead with a standard. As such I don't even see much use of event
handling at UI layer - I always like to keep UI layer simple.
Now
On Thu, July 26, 2007 1:23 pm, souravm wrote:
For me so far I don't see any reason why people should go for JSF except
for moving ahead with a standard. As such I don't even see much use of
event handling at UI layer - I always like to keep UI layer simple.
But remember that something can be a
souravm wrote:
Regarding going for JSF due to componentization, I'm again not sure what additional componentizations JSF does compared to struts.
JSF is inherently a component-based framework, meaning you aren't really
thinking in terms of pages, your thinking in terms of components of a
souravm wrote:
Will you consider Struts to be a better choice today compared to JSF ?
In *most* cases, for me, yes I would, but that's just my opinion, and
I'm about to invalidate it at the end of this :)
Especially, given the fact that JSF has better controller
flexibility, event
12 matches
Mail list logo
