I'm not against, but the reason for beanName is to distinguish EJBs that
are composed of the same classes.
BeanInterface is there to differentiate between local / remote call
semantics when you inject a possible common interface.
All can be handled equally by a @Resource with a proper lookup though.
Carlo
On 07/04/2011 01:31 PM, Adam Bien wrote:
> Should we deprecate @EJB in favor of @Inject? I would like to file this issue :-)
>
> thanks,
>
> --adam