Description Roberto Sanchez Herrera 2012-01-16 11:37:14 EST

Bug for backporting this code to WTP 3.2.5 P

+++ This bug was initially created as a clone of Bug #366346 +++

Currently, when you create a session EJB with local and/or remote view and you do not implement any other interface, the remote and/or local interfaces are created with the proper annotation (@remote or @local), and the resulting bean only implements these interfaces. But if you implement an extra interface in the wizard, the resulting bean class will have the @Remote and/or @Local annotation as well, 

This enhancement proposes to change this behavior by default, or provide a way to change this behavior, to add to the bean class the @remote and @local annotations besides implementing the interfaces even when you do not implement an extra interface, something like this:

/**
 * Session Bean implementation class MyBean
 */
@Stateless
@LocalBean
@Remote({com.test.MyBeanRemote.class})
@Local({com.test.MyBeanLocal.class})
public class MyBean implements MyBeanRemote, MyBeanLocal {
.....
}

The benefit to placing then annotations on the bean class is that it's clear what the business interfaces of an EJB are. Besides, this would help developers if they change their mind later and they want to implement an extra interface in their beans, or if they later want to add an extra remote/local business interface. This could also tools and application servers.