Hi Pam,
JSecurity as a framework (not necessarily the Grails plugin)
explicitly stays away from this. To create automated support for
User/Role/Permission management, which are part of your domain model,
would require the framework to know about your domain model. Domain
models change dramatically across organizations and applications, so
there might not be easy way to solve this.
For example, it is easy to think of adding and creating users, which
implies a User class. But does that User class extend a Person class?
Maybe the Person class has a collection of postal addresses and phone
numbers for address book management. Maybe the application uses
Roles, but maybe also Groups. Maybe Roles reference permissions for
fine grained control, but maybe the application doesn't need
permissions at all. Maybe the User class has a change history
requirement so reports can be run on what the users did and when....
I think you get my point.
In order to have good User management capabilities, you have to assume
quite a bit about a domain model, which is incredibly difficult to do
in an application-agnostic manner.
Perhaps if you can describe exactly what you're looking for then we
can make some adjustments and add support code to make this even
easier for many applications. I'm certainly open to suggestions,
because if it can be done, then you bet we'll do our best to make it
happen :)
Cheers,
Les
On Wed, May 14, 2008 at 4:12 PM, Callaway, Pamela <
pcallaway@...> wrote:
>
>
>
>
> Hi folks,
>
>
>
> Is there a default behavior for account creation and user management with
> Jsecurity? I started to flesh out this function and I realized it was
> getting a bit complicated.
>
>
>
> Also, is there some way to specify the name of the table used for a
> one-to-many mapping, using the static mapping closure?
>
>
>
> Thanks,
>
>
>
> Pam
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
