It seems to me that the naming system in turbine is constrained. For
example, to access
org.apache.turbine.flux.modules.actions.group.FluxGroupAction, it needs the
template to call
.setAction("group.FluxGroupAction").
in the template. However, because
module.package=org.myCompany.modules,org.thirdParty.modules,org.apache.turbi
ne.flux.modules
The name of "FluxGroupAction" can not be used in my module nor the
thirdParty modules. This is a constraint for exchanging packages between
developers.
One way to solve this problem is to put in a name mapping in
TurbineResources.properties, such as:
action.fluxPacakge.group.FluxGroupAction=org.apache....group.FluxGroupAction
module.package=
and use .setAction("action.fluxPackage.group.FluxGroupAction") in the
template to access this action. Is this a valid way of use in Turbine now?
Similarly to the templates naming.
flux-templates/screens/group/FluxGroupList.vm
is accessed by
template/group,FluxGroupList.vm
Because
services.TurbineTemplateService.template.path=/templates,/flux-templates
it requres that the name "FluxGroupList.vm" must not appear in
templates/screen/group/ directory. This is the same constraint as in Action
naming above and can be solved by the similar proposed way as well. I would
like to know whether the current version of turbine have implemented such a
solution.
Another question is that because it is not needed to specify the screen
directory for accessing the screen template, i.e.
template/screen,group,FluxGroupList.vm, how to call a layout template from
the browser? Or, is it true that each turbine based web site only allow one
layout template for standalone and one for embeded?
I am still at very early stage of getting into Turbine and trying to
evaluate it for our web development. Your helps are very much appreciated.
Regards,
Yi-Xiong Zhou
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
