Me :-) It actually works, but we had some problems with TreeCacheAop, where Javassist wanted to instrument the JNDI code as well.
I haven't checked whether this works from a rich client (outside the JBoss process), I have only tested JNDI lookup from a *co-located* servlet. If you happen to have some cycles, it would be nice if you could test that and let me know whether it works.
I'll revisit this.
I have a class extending TreeCache and overridden the startService method to bind the treecache to the JNDI tree. No need to uncomment code
works fine (so far...)