Hi Mark,
Mark Wassermann wrote:
is there any documentation for this project?
I'm quite new to turbine, but I guess there isn't.
You can see it running in the TDK:
http://jakarta.apache.org/turbine/tdk/index.html
(@webmaster: Could you please set up there a link to:)
http://jakarta.apache.org/builds/jakarta-turbine/tdk/release/2.2/
which version or cvs-branch do I need for turbine 2.3.1?
I have set up my Turbine 2.3.1 enviroment with the META plugin. Then I fetched the newest source of flux from CVS. To get it up and running I did the following:
In MyApplication.properties: --------------------------- include = Flux.properties
# Used by Flux Templates: tool.request.link=org.apache.turbine.util.template.TemplateLink tool.request.page=org.apache.turbine.util.template.TemplatePageAttributes
#Don't forget to set up the /resources directory tool.global.ui=org.apache.turbine.services.pull.util.UIManager
# For generating the User/Group/Role/Permission lists, Flux uses an own pull tool in the templates:
tool.request.flux=org.apache.turbine.flux.tools.FluxTool
#To make Flux Action/Screens visible to Turbine: module.packages = org.apache.turbine.flux.modules
#To make the Flux Templates visible to Turbine:
services.VelocityService.file.resource.loader.path = /templates/myApp,/templates/flux
-----------------------
I'm using flux in embedded mode and use FluxMenu.vm to access it. The users accessing Flux need the turbine_root role as defined in Flux.properties!
For understanding the security model, reading admin-app in the /xdocs dir helped me a lot. I think Flux is a nice starting point for user management because it's easy to extend and maybe all you need.
regards,
Joachim
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
