I am the same way. I have a large collection of common libraries that I have developed over the past 5 years or so. Each iteration, they get a little more powerful. I can create a highly scalable and complex application very quickly using Struts because of this. Yes java may be overkill for a personal home page, but for mission critical applications or sites that require 1000's of transactions per hour, it is a must. I hope JSF takes off and becomes as easy to use as VS 2005, but until a wide range of either customer components or vendor developed components are available, its reach will be limited by comparision. I think it will happen, but not over night. Until then, there are very few languages that can deliver the power and speed of development as my struts / Java library.
"Mark Benussi" <[EMAIL PROTECTED]>
07/26/2005 07:45 AM
|
|
Luckily my apps are written with a large amount of the code written for each
customer, with reusable taglibs plugging into each site. All my DAO etc is
done as the sites use the same DB schema and therefore code.
I am 90% of the way there from day 0 with each customer so this is not an
issue.
I dont think i am falling for any marketing theory, I have bene doing Java
apps for about 7 years. I didnt even see your point anyway. Is it marketing
hype to state that Struts/Java/Servlets is for large
applications and I would not build a suite of actions and database pooling
for my old mans plane photos web site
----Original Message Follows----
From: netsql <[EMAIL PROTECTED]>
Reply-To: "Struts Users Mailing List" <user@struts.apache.org>
To: user@struts.apache.org
Subject: Re: JSF is the beginning of the end of Struts !!!
Date: Tue, 26 Jul 2005 06:27:35 -0500
Mark Benussi wrote:
>
>I have never done any PHP so I can't comment, but agree with the previous
>comments in so far as Struts/Java/Servlets is for large applications. I
>would not build a suite of actions and database pooling for my old mans
>plane photos web site.
>
>
You may be just repeating the marketing theory, not what was validated in
practice. Friendster switched to PHP after Java, so I guess they did not
find Java scaleable.
On a large project you may want to reduce risk by starting w/ 80% of project
done and customize the last 20%. Imagine, 1st week and you are 80% done.
There is DAO, etc for PHP, take a look at architecture of TikiWiki.
And my faviorte lesson: Home page of Spring is in Plone.
Here is a good summary of what's out there:
http://www.opensourcecms.com/index.php?option=content&task=view&id=388&Itemid=143
So if you do non RiA application.... you need to objactivley consider php
and plone, see if they have a solution w/ less risk.
.V
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
