Jon Stevens wrote:
> How is that? You are asking me to compare Velocity and JSP, but you aren't
> really saying why other than it concerns you.
>>If you come from a Perl or PHP background, JSP is a way to take
>> your pain to new levels. --Anonymous
My suspicions are that JSP is painful as in difficult to debug.
That part about 'pain to new levels' is very concerning for anyone planning
on working with JSP on a big project.
Isn't that what you intended, for people to ask why it is so painful?
Anyway, Thanks for the quick response, now you really have my interest!
Id like to start developing with the Pull Service Model.
Is the Pull Service still being designed and developed, can I start writing
Application Tools with it today?
I looked at the classes last week (1/28 build), and there wasn't much there
yet.
(Dont get me wrong, simplicity is often brilliance)
How would one go about writing Application Tools?
Is it as simple as writing any class and inheriting from an ApplicationTool?
Then the methods are found with introspection...
Is there some kind of persistent registry of tools?
Looking at the impl of TurbinePullService, there is a Map: private Map
toolBox;
Are there plans for hierarchies or categories of application tools?
Look forward to reading your page on the negatives of JSP
thanks, and sorry for all the questions, but this is very interesting to me,
and hopefully the other jetspeeders,
- david
> output .sql files (@see Turbine's Torque system), send email [2] and do
many other cool
> things that you just can't do easily with JSP.
>
Ive seen the database stuff linking to form input fields, that is cool and
worth checking out
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/[email protected]/>
List Help?: [EMAIL PROTECTED]
