"local" (not remote) global lookup means you leak the classloader which means you can break any app easily. jboss has a mode to deactivate it - at least a few versions ago it was possible.
Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://rmannibucau.metawerx.net/> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> 2018-01-23 15:47 GMT+01:00 Dignesh <[email protected]>: > Thank you very much Romain. I had the same kind of setup in my config. I > missed to replace my jar after updating my bean to remote. > > Just curious to know why the global lookup is not allowed in TomEE , - I > see > classcastexceptions > I dont see this issue with JBoss app server. I am able to do global lookup > successfully. > > Any other way through which we can achieve this behavior ? > > > > -- > Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev- > f982480.html >
