Thank for Your Reply, it's likely what i have to do... even if i'm
using EJB3 persistence with JBoss 4... it's implemented by Hibernate
but i don't know if this particular feature is implemented... for
example Query By Criteria and Query By Example are not part of the EJB3 Feature
And
Thank for Your Reply, it's likely what i have to do... even if i'm
using EJB3 persistence with JBoss 4... it's implemented by Hibernate
but i don't know if this particular feature is implemented... for
example Query By Criteria and Query By Example are not part of the EJB3 Feature
And
No, that's not currently possible. You cannot have an interceptor injected
by default into every service point.
-Original Message-
From: Ing. Stefano Girotti [mailto:[EMAIL PROTECTED]
Sent: Friday, May 19, 2006 9:07 AM
To: users@tapestry.apache.org
Subject: Re: Best pratice - CRUD
inline
On 5/19/06, Ing. Stefano Girotti [EMAIL PROTECTED] wrote:
Thank for Your Reply, it's likely what i have to do... even if i'm
using EJB3 persistence with JBoss 4... it's implemented by Hibernate
but i don't know if this particular feature is implemented... for
example Query By Criteria
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Carl Pelletier wrote:
Hi everyone, I'm currently building a web site and looking for
documentations on how-to or best practice of implementing Role security
in Tapestry 4.0.
It`s a Simple CRUD application and we need to give some security to
It's Tomcat security in combination with a PageValidateListener that
solves this problem for me. In each page that needs special security
there is a call to request.isUserInRole(...). If the user isn't
allowed, a PageRedirectException is thrown to redirect to an allowed
page or to the error
On 16. Mai 2006 - 10:45:45, Brian K. Wallace wrote:
| This is where I stick with ACEGI being unobtrusive. Not discounting any
| other method of doing it at all, but I found that with ACEGI I add a
| hook into login/logout pages and there's no other intrusion into my
| Tapestry applications outside
, 2006 11:57 AM
To: Tapestry users
Subject: Re: Best pratice - CRUD Security - Tapestry 4.0
On 16. Mai 2006 - 10:45:45, Brian K. Wallace wrote:
| This is where I stick with ACEGI being unobtrusive. Not discounting any
| other method of doing it at all, but I found that with ACEGI I add
I agree that ACEGI fits very nicely with Tapestry. Still, it introduces two
technologies for the team to learn, ACEGI and Spring.
Having chosen hivemind as the IOC container to use for some projects i don't
find the option to also use Spring in the same projects a very good one.
If only there was
Well, I did it for the Sprint transaction stuff. I'm sure I can do it for
the Acegi stuff. :-)
-Original Message-
From: Hugo Palma [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 16, 2006 12:09 PM
To: Tapestry users
Subject: Re: Best pratice - CRUD Security - Tapestry 4.0
I agree
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
And now, the required:
Is it done yet? Do you have a demo? ;-)
James Carman wrote:
I would probably do it as a generalized HiveMind library first which
includes an AcegiInterceptor implementation of some sort. Then, I'd write a
: Jesse Kuhnert [mailto:[EMAIL PROTECTED]
Sent: 16 May 2006 17:19
To: Tapestry users
Subject: Re: Best pratice - CRUD Security - Tapestry 4.0
You don't need oracle fine grained access control to do the same thing.
As long as your DB supports the notion of stored procs / global (transaction
bound
12 matches
Mail list logo
