I am just curious why things like action.login, action.sessionvalidator and 
ScheduledJobs can't be fully qualified and just be anywhere in the classpath... what 
is the advantage of having an extra "classpath" type thing going on? This has been a 
problem for me a few times... I was off-line this weekend trying to do something with 
scheduled jobs, without source code or an offline copy of the web site... I didn't 
realize you needed a scheduledjobs package under modules in order for the scheduler to 
see the task... It is not in the javadoc.. at least not where I saw it... can anyone 
help me out with some thoughts on this?




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to