Hi there, I wonder if anybody is out there who has been trying to "synchronize"
a) org.apache.turbine.om.security.TurbineUser, the User-Implementation that offers Turbine-backend functionality with b) com.mycom.om.TurbineUser(Peer), the Peer classes that are used to access table turbine_user in order to have the functionality of both classes under a single cover(class). I have not yet understood if there is a common solution for this, or if this is solved completely according to individual needs. Can somebody give me an idea briefly? Also, it irretates me that *both* org.apache.turbine.om.security.TurbineUser and com.mycom.om.TurbineUser provide get/set-methods for the fields in table turbine_user. Why is that? Actually I have been trying the whole week to discover the most clean way to implement custom business logic for the user. TurbineUserPeer apparently is one place to do that. But when it comes to extending security management, extending org.apache.turbine.om.security.TurbineUser seems to make more sense. So... I was wondering if it's possible to have a single class for all kind of user-functionality, including my own custom methods. Thanks. Marc -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
