the non-optimized is a packaging problem on your end, class definitions are picked up in different classloaders and thus cannot be shared. This is done easier in 3.0.
EJB2.0 local interfaces are supported in 2.4*, however the 2.0 cmp stuff is only in 3.0
Thanks for your input- actually though the localInterfaces I am using are only with stateless session beans- It just seems strange that the JNDI name is registered with JBoss but they are not bound to the localEJBObject- I look forward to the local Interface stuff in 3.0.
The different classloaders causing a problem with JBoss_2.4.4-Tomcat_4.0.1 are a pain- especially as it works so nice with JBoss2.4.4_Tomcat3.2.3 (passing-by-refernce)- hopefully they will all be loaded the same in JBoss 3.0- so a static variable in 1 class is truly static within the whole application- and without having to worry about a class being loaded by the .war file and a different 1 loaded in a ejb .jar file causing headaches.
Hopefully 3.0 will be released soon with an integrated stack with Tomcat- for now though I will skip Tomcat4- it proves to have too many differences for my older code.