Week 3 - Stateful Session Beans (SFSB)

Question 1

SFSB are dedicated to one client (T or F)

Answer 1

T

Question 2

SFSB are long-lived (T or F)

Answer 2

F

Question 3

SFSB use instance pooling (T or F)

Answer 3

F - SLSB do

Question 4

SFSB are susceptible to passivation and activation (T or F)

Answer 4

T

Question 5

Why might a stateful session bean implement session synchronization?

Answer 5

jakarta.ejb.SessionSynchronization

Allows the bean to take action before or after a transaction.

With session synchronization, you can be sure that your state changes are synchronized with the commit or rollback of the transaction. This ensures data consistency and reliability across the entire transaction.

Question 6

difference between stateful session bean and cdi bean?

Answer 6

Stateful Session Beans are used when you need to track client-specific state over multiple method calls (like for user sessions).
CDI Beans are more general-purpose and allow for dependency injection and flexible state management based on different scopes (like session or application-wide state).