Which three methods can Bean Developer use in any EJB compliant container implementing the full Java EE6 product? (Choose three.)

The correct answer is B. FileInputStream.read C. DataSource.getConnection D. EJBContext.getCallerPrincipal. D: UseEJBContext.getCallerPrincipal()to obtain the java.security.Principal that identifies the A: Do not load native libraries. E: Not allowed:Starting, stopping, or managing threads in any way. That restriction eliminates the possibility of conflicts with the EJB container's…

EJB Lite

Question

Which three methods can Bean Developer use in any EJB compliant container implementing the full Java EE6 product? (Choose three.)

Options

AClass.getClassLoader
BFileInputStream.read
CDataSource.getConnection
DEJBContext.getCallerPrincipal
EExecutors.newSingleThreadExecutor
FQueueConnection.createQueueSession

How the community answered

(29 responses)

A
3% (1)
B
72% (21)
E
10% (3)
F
14% (4)

Explanation

D: UseEJBContext.getCallerPrincipal()to obtain the java.security.Principal that identifies the A: Do not load native libraries. E: Not allowed:Starting, stopping, or managing threads in any way. That restriction eliminates the possibility of conflicts with the EJB container's responsibilities of managing locking, threading, and concurrency issues. Programming restrictions on EJB javax.ejb Interface EJBContext

Topics

#allowed APIs#bean developer restrictions#container compliance#Java EE methods

Community Discussion

No community discussion yet for this question.

Full 1Z0-895 Practice