On Thu, Jun 5, 2008 at 2:52 PM, Pete Muir <pmuir(a)bleepbleep.org.uk> wrote:
2008/6/5 Christian Bauer <christian.bauer(a)gmail.com>:
> Also problematic seems to be the ManagedEntityIdentityInterceptor (I think
> we really could use a "no JavaBean clustering" switch that disables it -
> need some input from Gavin who initially wrote it if that is feasible):
100% agreed, I want to implement this as the ability to configure
(enable/disable) default interceptors.
As someone who's had a lot of headaches with
ManagedEntityIdentityInterceptor...let me just say "Yay!"
Can we detect whether we need
to enable the ManagedEntityIdentityInterceptor somehow (e.g. if aren't
in a cluster we don't need it definitely).
AFAIK there is no standard way to do this. I have a way to detect it
for Jboss/Tomcat (by checking for the presence of the ClusterManager
MBean, but that probably won't help unless we want to create a
pluggable component which has tweaks/advice for the each app server,
in which case each could also have an implementation of things like
"isSessionClustered(HttpSession)." That's a potential maintenance
nightmare, but if someone from each large app server maintained their
tweaks component, it could work.
-Clint