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-developer] hibernate compatability ( blah
blah
blah
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
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
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.find(
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
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 compatability ( blah
blah
blah
. 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-developer] hibernate
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.
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
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
Hi there,
I am new to acegi and have been working with it just over the weekend
so some of this stuff may be absolute bs but please bear with me on this.
I am currently evaluating the use of acegi for my open source project
jestate ( http://jestate.sourceforge.net )
Jestate is (currently) built
12 matches
Mail list logo
