erm, isn't that a bit counterproductive? I've got a Remote interface that remote clients use, but actually two different implementations depending on the enviroment.
Now with this change the remote client application needs to know what implementation is deployed onto JBoss, and any abstraction that EJB gave us are gone. Why is that? How do you do lookups now w/o knowing what Bean implements the remote interface? Another thing: Jobss doesn't deploy to EJBNAME/remote but to EARNAME/EJBBEANNAME/remote, so you also need to know the EAR name. Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3922903#3922903 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3922903 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
