I have looked into this, there is nothing that makes the service come into
the correct JavaEE context with Spring. Spring attempted to insert Proxy
(with Spring DM), but at best this proxy would only try to adjust the Thread
Context Classloader. Actually there is nothing in the Enterprise OSGI
specification that would ensure a correct Java EE context transfer. As far as
I know, The context is buried in the thread locals which only glassfish knows
how to read and set.
--
[Message sent by forum member 'chejavara']
View Post: http://forums.java.net/node/892780