On Dec 12, 2005, at 4:30 PM, John Coleman wrote:
Statically typed, eh? Again, what about all that reflection going
on? Let's take the most basic Java interfaces, List and Set.
Good points. Reflection should be kept out of critical stuff like
business
logic, and ideally collections as well, use arrays instead.
I wouldn't at all go that far. Nothing wrong with reflection.
Again folks, write tests - don't think your compiler is helping you
much. Use reflection anywhere you like, just test your use of it.
Perhaps I'm an old fart, I used to code RPG3 and green screens in SDA.
Everything was pretty simple and tightly coupled. Tapestry has
taken us a
bit closer to that, than straight JSP+servlets, but not very far.
I'm still
unhappy how long it takes to write and debug the average web app. I
used to
get done in hours what I achieve in days with JSP and servlets.
You really ought to give RoR a try then. It lives up to the hype of
productivity gains.
However, it might be feasible to produce a validator for the .page
and .html
files? This could at least check for property existence.
Definitely possible. I looked at using the core of Spindle to do
this at point, but it is very connected to the Eclipse API, making it
prohibitive to create an Ant task that Tapestry could ship for such
things.
Erik
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
