Does someone have any fresh idea?
On Tue, Oct 20, 2009 at 10:32 PM, Roman Ilin roman.i...@gmail.com wrote:
My components should stay visible all time. But data should be
filtered by customer currently logged in.
On Tue, Oct 20, 2009 at 10:29 PM, Pedro Santos pedros...@gmail.com wrote:
I
Are you using Hibernate? If so, you could use filters. Also, Oracle
has something built in that will automatically rewrite your queries
for you based on the database user that's connected (most people don't
use Oracle usernames to connect, though).
On Wed, Oct 21, 2009 at 7:48 AM, Roman Ilin
No I use plain Spring JDBC in one of my projects (there is old legacy DB)
but probably I'm going to use Hibernate in next one.
On Wed, Oct 21, 2009 at 2:13 PM, James Carman
jcar...@carmanconsulting.com wrote:
Are you using Hibernate? If so, you could use filters. Also, Oracle
has something
We use a thread local to store the organization of our user, and have
custom createCriteria() methods in our DAO's to add restrictions on
the organization.
Martijn
On Tue, Oct 20, 2009 at 10:14 PM, Roman Ilin roman.i...@gmail.com wrote:
Hi *,
I develop WebApplication where database records
Two questions:
1) why do you use thread local and don't store organization in session
2) to pass organization to your createCriteria() you have to have
organization as parameter in every DAO method where it is appropriate,
right?
On Wed, Oct 21, 2009 at 2:17 PM, Martijn Dashorst
On Wed, Oct 21, 2009 at 8:22 AM, Roman Ilin roman.i...@gmail.com wrote:
Two questions:
1) why do you use thread local and don't store organization in session
If you store it in your session, you have to mix your data access
layer with your web layer. With thread-local variables, you don't
(you
every time for every component
why not for every query?
On Tue, Oct 20, 2009 at 6:23 PM, Roman Ilin roman.i...@gmail.com wrote:
Sure I save my user in session.
The problem is that I have to implement this filter functionality
every time for every component.
On Tue, Oct 20, 2009 at 10:18
Sorry. I do it for every query but normally every component has its own query.
On Tue, Oct 20, 2009 at 10:26 PM, Pedro Santos pedros...@gmail.com wrote:
every time for every component
why not for every query?
On Tue, Oct 20, 2009 at 6:23 PM, Roman Ilin roman.i...@gmail.com wrote:
Sure I
I had application with components that override the isVisible method testing
for
return session.getUser().hasAccessFor(this)
but the major access logic is implemented on data access layer
On Tue, Oct 20, 2009 at 6:26 PM, Pedro Santos pedros...@gmail.com wrote:
every time for every component
My components should stay visible all time. But data should be
filtered by customer currently logged in.
On Tue, Oct 20, 2009 at 10:29 PM, Pedro Santos pedros...@gmail.com wrote:
I had application with components that override the isVisible method testing
for
return
10 matches
Mail list logo
