Vinay Kejriwal

Thanks Luan. It helped.

Excellent explanation.

Basically it means that withouth @DeclaredRoles or <security-role-ref>, it is not possible to invoke ctx.isCallerInRole("role") in the bean code.

Explanation given here by enthuware seems to be confusing.
http://enthuware.com/forum/viewtopic.php?f=4&t=417


Thanks,

Thanks Luan,

But shouldn't this code fail at compile time? I have seen this kind of code getting compiled without any error. So what exactly would be the behavior. Will jvm simply ignore this at runtime?

Hi,
Though not related to actual question here, I am puzzled with the usage @TransactionAttribute(TransactionAttributeType.REQUIRED) (CMT annotation) in the TestAddCommand ejb, even though the class has got @TransactionManagement(TransactionManagementType.BEAN) annotation (BMT).

Sorry for asking this if this is too trivial, I have started learning ejb recently and got confused seeing such a code.

Thanks

Hi,

I came across a piece of code where the bean implementation class has @TransactionManagement(TransactionManagementType.BEAN) annotation wherein methods are annotated with CMT @TransactionAttribute. Is is valid? I am puzzled?
Can an EJB with BMT persistence use CMT transaction annotation? What will be the behavior at runtime?

@Stateless( mappedName = "Abc") @Remote("AbcRemote.class") @Local("AbcLocal.class") @TransactionManagement(TransactionManagementType.BEAN) public class AbcBean implements AbcLocal, AbcRemote{ @Resource private UserTransaction utx; @PersistenceUnit private EntityManagerFactory emf; @Override @TransactionAttribute(TransactionAttributeType.REQUIRED) public Abc getAlpbabets(String name) { EntityManager em = null; try { em = emf.createEntityManager(); } catch (RuntimeException re) { throw re; } finally { } } }

Thanks in advance.