I'm customizing the Torque Security Service to adapt it to a legacy user table.
Does this service expect the same number of columns as in the TURBINE_USER table? Can I omit some columns that I don't have in my legacy table but TURBINE_USER has? Currently I'm thinking that yes I can do it as long as: a) put a valid, existing column, bean property not necessarily the expected one, this it's only needed for the init phase of the service, later on is not needed, only If I do a static call but that's out of visibility since I'm using a different class for accessing my bean properties. The only fields, bean properties that I can't omit are USER_ID, LOGIN_NAME, PASSWORD_VALUE since they are automatically used for authentication, their presence it's assumed by the service. b) since the Torque security service is calling my legacy table peers then it should be safe to assume that those peers will know how to save, retrieve my legacy rows. Under this functionality, the Torque Security service it's just acting like a proxy for my customized table, peers. am I right? Thanks in advance for any reply, Rogelio --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
