ejb-3.1

Can an EJB bean implement multiple user defined interfaces, except business interfaces (@Local, @Remote) or No-Interface view (@LocalBean)? For example define two interfaces UserInterface1 , UserInterface2 , with no annotation. Is this legal to implement: @Stateless public class MyBean implements UserInterface1, UserInterface2 { ... Then I have another confusion: @Stateless public class MyBean implements Runnable { ... //inside I won't try to manage thread } Is this legal or illegal, I found that glassfish support this situation. The given example is illegal, but nevertheless accepted by quite

I'm using inheritance with EJB in a few scenarios, sometimes with annotations in the super class like this generic entityDAO: public class JpaDAO<T>{ protected Class<T> entityClass; @PersistenceContext(unitName="CarrierPortalPU") protected EntityManager em; protected CriteriaBuilder cb; @PostConstruct private void init() { cb = em.getCriteriaBuilder(); } public JpaDAO(Class<T> type) { entityClass = type; } @TransactionAttribute(TransactionAttributeType.REQUIRED) public void create(T entity) { em.persist(entity); } @TransactionAttribute(TransactionAttributeType.NOT_SUPPORTED) public T find

Currently I am trying to inject a stateless EJB into a CDI managed controller on Jboss 6 AS Final. The controller is managed in the context an accessible from the JSF pages. If I inject the stateless bean with @EJB it is working. If I inject the stateless EJB with @Inject I get the following Exception: My controller: @Named("TestController") public class TestController { @Inject private TestManagerLocal myTestManager; ... } } My stateless bean: @SuppressWarnings("unchecked") @Stateless public class TestManagerBean implements TestManagerLocal { @PersistenceContext private EntityManager em; ...

I am planning to use EJBContext to pass some properties around from the application tier (specifically, a message-driven bean) to a persistence lifecycle callback that cannot directly be injected or passed parameters (session listener in EclipseLink, entity lifecycle callback, etc.), and that callback is getting the EJBContext via JNDI. This appears to work but are there any hidden gotchas, like thread safety or object lifespan that I'm missing? (Assume the property value being passed is immutable like String or Long.) Sample bean code @MessageDriven public class MDB implements MessageListener

Using Glassfish, I can setup a string jndi entry: JNDI name: "com/xyzcompany/echo/EchoServiceBean/viewName" Factory Class: org.glassfish.resources.custom.factory.PrimitivesAndStringFactory Properties: value="Testing123" I can then inject this container configured string into my EJB: @Resource(lookup = "com/xyzcompany/echo/EchoServiceBean/viewName") String viewName; The lookup= appears to internally do an InitialContext.lookup(...). However, this uses ejb3.1, but unfortunately my prod environment is only ejb3.0. I guess i'm trying to figure out is there a way to use @Resource(name=) or