Hi,
> So it would be really cool if the User ( which implements UserDetails )
> also had an id ( Integer ) properties.
You can return any object implementing UserDetails interface from your
loadUserByUsername() implementation of AuthenticationDao interface, so at
any place you can cast this user
Ok so the three things i think i need to do are as follows.
This bean will be created per request
public class SystemUserHolder implements ISystemUserHolder{
private final SystemUser systemUser;
/**
*
*/
public SystemUserHolder() {
super();
SecureContext secure
bryan wrote:
Then my methods that are in the orderService class can
call systemUserHolder.getSystemUser.getId() and
do searches for example where the user is only allowed
to see financial data for a certain region.
I am very much new to Spring so if I'm completely off the
mark here feel free to
Thanks Ben,
What I'm trying to do on a functional level is quite straightforward.
The application that I am writing is intended for the real estate business.
In this business a sales agent will only be able to view/edit properties
that he/she has been assigned/brought into the company.
So when for
Actually here is a good example of a future use of what I am planning on
doing.
This is not possible now but if I structure my application the way I am
saying
then it will be a great way to do it in the future.
Filtering using hibernate 3 filters.
http://www.theserverside.com/blogs/showblog.tss
administrator wrote:
Thanks Ben,
What I'm trying to do on a functional level is quite straightforward.
The application that I am writing is intended for the real estate
business.
In this business a sales agent will only be able to view/edit properties
that he/she has been assigned/brought into th
Ben Alex wrote:
administrator wrote:
Thanks Ben,
What I'm trying to do on a functional level is quite straightforward.
The application that I am writing is intended for the real estate
business.
In this business a sales agent will only be able to view/edit properties
that he/she has been assigne
Ben Alex wrote:
administrator wrote:
Thanks Ben,
What I'm trying to do on a functional level is quite straightforward.
The application that I am writing is intended for the real estate
business.
In this business a sales agent will only be able to view/edit properties
that he/she has been assigne
> Using hibernate it is possible to do the following ( pseudo code )
>
> SalesPerson salesPerson = hibernate.find( "SalesPerson as
> salesperson where salesperson.id = 1");
>
Why not just use the username (which should be unique) to lookup the
SalesPerson?
SalesPerson salesPerson = hibernate.
Oliver Hutchison wrote:
Using hibernate it is possible to do the following ( pseudo code )
SalesPerson salesPerson = hibernate.find( "SalesPerson as
salesperson where salesperson.id = 1");
Why not just use the username (which should be unique) to lookup the
SalesPerson?
SalesPerson salesPers
BTW, we use hibernate for all our data access.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf
Of
> Ben Alex
> Sent: Tuesday, August 17, 2004 5:35 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [Acegisecurity-developer] hibernate comp
. The docs are pretty good for any software but the test
cases are great.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf
Of
> Ben Alex
> Sent: Tuesday, August 17, 2004 5:35 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [Acegisecurity
re pretty good for any software but the test
> cases are great.
>
>
>
> > -Original Message-
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED] On Behalf
> Of
> > Ben Alex
> > Sent: Tuesday, August 17, 2004 5:35 PM
> > To: [E
13 matches
Mail list logo
