Re: [LiveUser] Avoiding multiple objects with the same handle?

Jeff Schmidt wrote:

I admit that I don't necessarily fully understand the relationship between the Admin classes, and the 'regular' classes. As far as I can grok, it appears the admin classes are just supposed to provide additional functionality like creating users and groups, adding users to groups, creating rights, etc, that would only be used for administrative purposes. And the non-admin classes are 'read-only' - that is, they let you query the container class for information about what objects are already in it.

yes that is correct

The other main problem I am having - I found userExists(), but I can't seem to locate any groupExists(), applicationExists(), or areaExists(). Do you guys plan to implement this functionality? Or is there another way to accomplish what I want (namely, to avoid creating additional objects in the container that have the same name as existing objects)?

there are several get* methods which led you fetch data from the database which you can limit by providing filters. regards, Lukas Smith smith@backendmedia.com _______________________________ BackendMedia www.backendmedia.com berlin@backendmedia.com Linn Zwoch Smith GbR Pariser Str. 44 D-10707 Berlin Tel +49 30 83 22 50 00 Fax +49 30 83 22 50 07