At 12:37 �� 27/8/2001 +1000, you wrote:
>Hi Filippos,
>This may not be very helpful, though when I initially started
>using velocity, I was able to debug it quite nicely
>under Jbuilder 4 on linux.
>Since moving to the TDK, I have never attempted to debug Turbine as
>it has such a nice logging facility in Log4J, so I sprinkly my code with
>Log.debug( ) statements, providing more than adequate insight.
>I use JBuilder 4 for building all my classes etc.
I won't dissagree with you.. Every programmer has it's own approach.. One
to fill his code with Log.debug statements and other to use breakpoints ;)
But note, that Turbine is an open source project and as with all open
source projects it somehow lacks of up-to-date documentation, therefore
time to time is *very* helpful to follow the execution path (with a good
debbuger) right inside Turbine's core to understand what is actually
happening.. For instance, I recall a situation where I couldn't use the
intake service correctly (the intake howto is out of date), but following
the execution path with my VAJ's debugging facilities just gave me the
answer (wrong rules xml specification) :)
Best Regards
Filippos Slavik
>Regards,
>
>Patrick.
################################################################
Filippos Slavik
FORTHnet R&D, Heraklion, Greece
e-mail : [EMAIL PROTECTED]
phone : (+3) 081 391230
################################################################
"The software said 'runs on Win95 or better,' so I installed it
on Linux..."
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
