The module.packages parameter in TurbineResources.properties should allow you to specify an other place to look for screen ans action push classes.Thanks for the reply. That is indeed what I need to do. I had been having trouble with Default.java & just discovered why.... I have my source divided up into multiple folders like the following to allow for a little easier separation of the different pieces of the site:
Org.co.web | |----modules | |----actions | |----screens | |----admin | |----actions | |----screens | |----staff | |----actions | |----screens
However, apparently Turbine only looks for Default.java files in the
"modules" directory. I tried puting Default.java in staff.screens.staff,
staff.screens, and staff subdirectories but none worked. When I put
Default.java in modules.screens.staff, Things worked as expected.
So, problem solved (I'll just put the default.java files in subdirectories of the modules dir), but shouldn't the staff subdirectories work as well? Them not doing so kind of screws up my attempt at fully partitioning the different applications.
-d
Frédéric
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
