Although I can see how it was broken for that particular case, the JNDI change has made things much more difficult for many other cases.
The application I'm working on is comprised of many different deployables and each one has a version number that changes over time. I'm not even sure how to use the new EJB3 look ups to make our application work anymore. I certainly don't want to have to make a new version of every module because the version of one of the modules changed (which I would have to do if I have to start hard-coding the version numbers in the JNDI look ups). I'm guessing that we're going to have to re-name every deployable so that it doesn't have a version. That pretty much sucks. The remote vs local change is less disruptive, but even then it seems like the container should be the one to decide if the call needs a remote or local bean. Is there something I'm missing with this change? Am I making things too hard for myself some way? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3922470#3922470 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3922470 ------------------------------------------------------- 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
