You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@turbine.apache.org by Ma...@ing.com.au on 2002/04/10 08:55:19 UTC

Why Turbine security om classes didn't use om classes generated by Torque?


I 've recently spent some time explored Turbine security service features. Some
concerns:

*  Why Turbine security om classes(UserPeer, RolePeer, PermissionPeer etc)
didn't use om classes generated by Torque?

My user, role, permission database table schema is a bit different as Turbine
security table schema. I planed to port the Turbine Security service on my
security tables. I've used Torque to generate my security om classes. But I
failed to reuse those security services provided by Turbine since they are
tightly coupled with those om classes which don't have the same API as generated
by Torque. My next step is to build my security service from scratch so I could
use my Torque generated om classes. I found out if I want to plug in my security
model into Turbine, I have to change the source code of class
TemplateSessionValidator. I am wondering whether are there any better ways to do
that? Or am I on the right track?

* How do I configure my own security service to work together with Turbine?

Regards,
Qingwen


NOTICE
The information contained in this electronic mail message is privileged and
confidential, and is intended only for use of the addressee.  If you are not the
intended recipient, you are hereby notified that any disclosure, reproduction,
distribution or other use of this communication is strictly prohibited.  If you
have received this communication in error, please notify the sender by reply
transmission and delete the message without copying or disclosing it.



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: Why Turbine security om classes didn't use om classes generatedby Torque?

Posted by John McNally <jm...@collab.net>.
The security classes are generated by torque.

john mcnally

Mao.Qingwen@ing.com.au wrote:
> 
> I 've recently spent some time explored Turbine security service features. Some
> concerns:
> 
> *  Why Turbine security om classes(UserPeer, RolePeer, PermissionPeer etc)
> didn't use om classes generated by Torque?
> 
> My user, role, permission database table schema is a bit different as Turbine
> security table schema. I planed to port the Turbine Security service on my
> security tables. I've used Torque to generate my security om classes. But I
> failed to reuse those security services provided by Turbine since they are
> tightly coupled with those om classes which don't have the same API as generated
> by Torque. My next step is to build my security service from scratch so I could
> use my Torque generated om classes. I found out if I want to plug in my security
> model into Turbine, I have to change the source code of class
> TemplateSessionValidator. I am wondering whether are there any better ways to do
> that? Or am I on the right track?
> 
> * How do I configure my own security service to work together with Turbine?
> 
> Regards,
> Qingwen
> 
> NOTICE
> The information contained in this electronic mail message is privileged and
> confidential, and is intended only for use of the addressee.  If you are not the
> intended recipient, you are hereby notified that any disclosure, reproduction,
> distribution or other use of this communication is strictly prohibited.  If you
> have received this communication in error, please notify the sender by reply
> transmission and delete the message without copying or disclosing it.
> 
> --
> To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>