If I understand this right you could use this mechanism to tie JAAS / J2EE
declarative security to application data permissions.
I.E. J2EE declarative security handles Authentication (who am I), and
Authorization (can I execute this code), but it doesn't handle can I see
this data. By adding what
This kind of thing is handled automatically, and very robustly in the Spring
framework. The Spring framework also supplies good integration with
Hibernate, and a very cool and innovative configuration system. You should
check it out. The next web app I build will use Spring.
www.springframework
Hello all,
This will probably be very useful in situations where we do not have full
control of the object in question. For example Axis is a very good
framework for implementing web services, as well as Java -> XML & XML ->
Java binding. However without modification of Axis, the returned Java
o
I have posted this to the Hibernate & Spring mailing lists as I think this will
require the involvement of both development teams to answer.
Hibernate uses **javabean no-arg constructors** to instantiate objects and then uses
javabean setters / getters when mapping from / to the database.
Sprin
> Have you taken a look at Interceptor.instantiate(Class clazz, Serializable id) ?
>
> With that you can do whatever you want regarding construction of objects ;)
>
Cool, exactly what I was looking for! That along with Hibernate's Lifecycle interface
will do everything I was asking for in my
I've never used it, but this sounds similar to what you are proposing:
http://rmijdbc.objectweb.org/
Later
Rob
>
> I've been thinking about the problem of users who ask for
> "lazy fetching from the client". As we keep explaining,
> this is an incredibly bad idea, since transaction
> demarcation
