I viewed his question as could he taking an existing ejb-ref that points to a remote jboss-4.0.x/ejb2.1 implementation, and simply point that to a remote ejb3 implementation, and visa-versa. The forward direction would probably just work if the ejb3 client jars were included, but exposing a legacy jboss-4.0.x/ejb2.1 endpoint to a remote ejb3 component might not. Its just a question of how well the legacy and new remoting transports integrate. Its something that needs to be tried.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3937023#3937023 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3937023 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
