Hi,
>> So you want me to help me after you dis my documentation ;) <<
sorry - did not (at all) want to complain about or dis' this documentation!
>> You have to take your application server down. <<
o.k.
>> Where are you changing the property files,
>> in the jetspeed distribution or
in the expanded web application?
I tried to change it either ways.
If the 'rule' is, to change it in the source,
then to build it, deploy it (hot),
and restart - o.k - i'll do it.
(this is just for keeping the turnaround time
a bit faster, and anyway being sure, that my testing reflect my real
changes...)
>> If you are just replacing the
>> UserManagement service, then just write a new
>> UserManagement service and implement your User class.
>> In the JetspeedSecurity.properties, change:
>>
>>
services.UserManagement.classname=org.apache.jetspeed.services.security.turb
ine.TurbineUserManagement
>>
services.JetspeedSecurity.user.class=org.apache.jetspeed.om.security.BaseJet
speedUser
>>
>> with your implementations
hmm.
i did change
...TurbineUserManagement
to point to my class.
but not yet the BaseJetspeedUser.
I followed the NoUserManagement approach...
So i won't have to change any other settings in the
JetspeeSecurity.properties file,
to have Jetspeed follow my classes functionalities ??
Thanks very much for the help
(and for the docs!)
I'll keep it a try.
best wishes.
thomas
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
