No worries! Yes I know how hard it is to use WAS. Anyway, thanks for providing us with a sample to reproduce.
It was not that hard to fix or to allow such a use case. We are always happy to fix or to help in portability issues. Sometimes it's harder or it has huge impacts even on performance that's why we think twice before patching. Long story short, I'm glad you enjoy using TomEE. Feel free to shoot again if you have other issue or any suggestion to make TomEE even better. You guys are helping TomEE! So thanks again. JLouis 2013/4/25 skay <[email protected]> > Hi, > > I just tried my 'ejblookup' test on Webshere 8.5 : it works perfectly also > on this AS. No surprise. > Even if I took half a day in order to download (!) and take hand on this > f** > AS(s) :) > > I would like to tell you that you should get inspired on other Application > Severs implementation. > For example, JBoss even if they try to do always specific (e.g. JNDI > names), > have good ideas, that sometimes comes to standards. In JBoss 7.1, they have > an interesting idea to force classloading policy within the MANIFEST file. > Websphere is too compicated; but if you take a little time to go inside > that > machine, you'll find very intersting ideas you should consider. Example : > admin wizards / configuration to control each module class loading policy. > > Now I'm sorry having been insistant about my issue, but I think that even > if > you consider it as 'portability' issue, you'll got it back sooner or later > as a scalability issue on TomEE. > > I think that TomEE should / and anyways will/ be *the* solution for > developping on the JEE Platform. I took less than 10 mins to separate what > should be a bug instead of a lack of knowledge on my side. > This is very important, and I think that I'll never have this sensitivness > with no other AS, even with 10 days instead of 10 mins, because TomEE is so > simple and transparent. > > Now, I'm looking forward installing next snapshot of TomEE in order to > validate that I can start my development on it instead of Jboss or > Glassfish. > > BR. > > > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/Classcast-execption-on-proxy-when-looking-up-remote-interface-tp4662060p4662462.html > Sent from the OpenEJB User mailing list archive at Nabble.com. > -- Jean-Louis
