I don't think #2 does much for you. Even if the LBP used by the proxy isn't
"TransactionSticky" it's quite likely the class will be on the classpath, as
it's packaged in the same jar as the other LBP impls.
Anyway, -1 to it because you are hard-coding things so it only works if *your*
TransactionSticky is on the classpath.
Keep it simple; don't stress too much about a couple map operations. Walk a debugger
through a complete method invocation on an EJB; the amount of stuff it goes through is
amazing. :)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4108580#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...