Having our proxies implement EJBObject is to be backwards compatible to EJB2.1 clients -
isn't that a major point of the spec? I know the details aren't there, but the
spirit of the spec is to be 2.1 client compatible.
Creating multiple proxies is a nightmare. It's confusing enough as it is since
it's not in the spec.
Again, can't we just tell SEAM to change their method name and disallow EJBObject
methods on Remote interfaces like EJB2.1 does?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4090427#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...