Hi there,

First, I'd like to thank you all, because until now all my questions 
concerning turbine were answered either by this mailing list or by 
reading the TR-docs.

For my current project it was necessary to add some properties to 
TurbineUser. For the database part this was no problem (extending the db 
xml file etc.). Now I'd like to have access to all properties of my 
TurbineUser. It's clear to me that I can modify the content of 
TURBINE_USER table through the peer mechanism of torque, but still:

- am I allowed to write a LoginAction using the torque generated peer 
classes instead of TurbineSecurity?
- if not: do I have to write my own implementation of TurbineUser (I 
mean: org.apache.turbine.om.security.TurbineUser)?
- should I create I tool like FluxTool to provide me with the Objects I 
need?
- is there a "standard" way for extending Turbine-User?

Hope, I made my point clear enough and thanks in advance...

Aleksandar


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

Reply via email to