Chris Kimpton wrote:
> The problem I am getting now is that there seems to be 2 definitions of the column
>names - on TurbineUserPeer via the map builder - which was good, since I could
>override that and use my custom table/column names.
>
> But these column names are also on the User interface - as hard coded strings
>(obviously a big no-no anyway.)
>
> Now my problem is that a method like getUserName, uses User.USERNAME to find the
>username value - but since this is the hard coded string, it does find my overridden
>column name in the permstorage object....
>
> So - is this area of turbine being worked on as part of the ACL changes, or is it
>considered stable? My thoughts are to remove the column names from the user object
>and change base user to use the peer column names (again) - allowing for mapbuilder
>customisations - alternatively we move the mapbuilder stuff into the User interface
>and out of turbine user peer - but that doesn't feel right.
Yes this porblem was addressed. Now all Peers used internally by Turbine
get
all data from the MapBuilder.
Also, the keys that you use for getPerm/setPerm methods are no longer
'table.column'
indentifiers, but rather arbitrary strings definded in User interface.
You can define more keys as neccessary, and Turbine will automagically
store the
values in fields added to TurbineUser table (or in OBJECTDATA, if there
is no
corresponding clumn).
You should check out the security branch (cvs co -d turbine-security -r
security_01-branch turbine)
and see the code for yourself.
Rafal
--
Rafal Krzewski
Senior Internet Developer
mailto:[EMAIL PROTECTED]
+48 22 8534830 http://e-point.pl
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
