Hi,
can anybody give me a rationale for not replicating final and static fields in
PojoCache? I can think of some scenarios where there could be problems, but I'm
not sure why it is not even offered as an option.
I couldn't find an explanation in the documentation, on the wiki, or in the
Thanks for the quick answer.
Concerning final, I see that it makes no sense replicating final fields that
point to immutable objects (e.g. Strings). But when the referenced object is
mutable I might want to replicate changes to it, too.
Objects are mapped into the cache by reachability, but
Oh yes, the documentation makes it clear that those are not replicated; I was
just curious about the reasoning behind that (a customer asked and I couldn't
come up with entirely satisfactory answers).
For the static case, I agree that this shouldn't be the default. But as with
final, in simple
Thanks, j2ee_junkie!
So it's related to me using Java 5! And indeed, it works fine with JDK 1.4.
That's a workable solution for now.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3950630#3950630
Reply to the post :
I am trying to secure the detached jmx invoker on a JBoss AS 3.2.6 as described
in the SecureTheInvokers wiki entry
(http://wiki.jboss.org/wiki/Wiki.jsp?page=SecureTheInvokers).
However, I get this error on startup (trace is from a 3.2.5 version, which
shows the same problem):
12:22:56,680
