Hi,
Something in he changes between T2.2 and T2.3 has caused a major PITA for
me.
I have services.VelocityService.template.extension=vm
services.VelocityService.default.page=VelocityPage
services.VelocityService.default.screen=VelocityScreen
services.VelocityService.default.layout=VelocityOnlyLayout
services.VelocityService.default.navigation=VelocityNavigation
services.VelocityService.default.error.screen = VelocityErrorScreen
services.VelocityService.default.layout.template = Default.vm
I have NOT subclass VelocityPage. I have subclassed VelocitySecureScreen and
provided a com.roamware.rwtransform.modules.screens.Default.class which
changes layout template dependent on the role of the user. It does this
with:
data.getTemplateInfo().setLayoutTemplate(templateName);
which from what I understand should NOT affect the page class being used, I
expect VelocityPage to be used.
But with the above settings I get this exception:
2003-10-21 15:37:07,565 [HttpProcessor[8080][4]] ERROR
org.apache.turbine.Turbine - Turbine.handleException:
java.lang.ClassNotFoundException:
Requested Page not found: Default
Turbine looked in the following modules.packages path:
[com.roamware.rwtransform.modules, org.apache.turbine.modules]
at org.apache.turbine.modules.PageLoader.getInstance(PageLoader.java:207)
at org.apache.turbine.modules.PageLoader.exec(PageLoader.java:136)
at org.apache.turbine.Turbine.doGet(Turbine.java:796)
This occurs only when submitted for certain actions in my application. Under
what circumstances does a different name for the Page class get substituted
for VelocityPage? I repeat, I do NOT have a VelocityPage subclass anywhere
in my package.
Possibly related to this I have commented out these:
#services.TemplateService.mapper.page.class =
org.apache.turbine.services.template.mapper.DirectTemplateMapper
#services.TemplateService.mapper.screen.class =
org.apache.turbine.services.template.mapper.ClassMapper
#services.TemplateService.mapper.layout.class =
org.apache.turbine.services.template.mapper.ClassMapper
#services.TemplateService.mapper.navigation.class =
org.apache.turbine.services.template.mapper.ClassMapper
#services.TemplateService.mapper.layout.template.class =
org.apache.turbine.services.template.mapper.LayoutTemplateMapper
#services.TemplateService.mapper.screen.template.class =
org.apache.turbine.services.template.mapper.ScreenTemplateMapper
#services.TemplateService.mapper.navigation.template.class =
org.apache.turbine.services.template.mapper.DirectTemplateMapper
because if I uncomment them I get
Requested Page not found: VelocityPage.vm
Turbine looked in the following modules.packages path:
[com.roamware.rwtransform.modules, org.apache.turbine.modules]
at org.apache.turbine.modules.PageLoader.getInstance(PageLoader.java:207)
at org.apache.turbine.modules.PageLoader.exec(PageLoader.java:136)
at org.apache.turbine.Turbine.doGet(Turbine.java:796)
I find the workings of the loading Page classes very complex, I have traced
into it.
Regards,
David Wynter
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
