CODEWITHSUNDEEP
ejb-3.0cdientitymanager
user953217
user953217

Reputation: 231

Stateful session bean passivation with non-serializable EntityManager?

I have just read Why stateful and local anti-facades are KISS by Adam Bien where he suggests using a SFSB with an EntityManager to keep entities attached during the whole client interaction.

  1. Does't this fail not in a clustered environment as mentioned in a comment but also whenever the SFSB should be passivated by the container?

  2. If I'm right what kind of solution would you suggest? I thought to minimize the number of layers in the application it would be useful to bind the SFSBs to conversation scope and then reference them directly in my JSF views.

Upvotes: 3

Views: 1233

Answers (1)

Doron Manor
Doron Manor

Reputation: 596

In general, having a stateful based architecture is counter scalable.

I have been working with EJB 3 SLSBs for over 5 years now in multiple projects and never had a real issue with merging entities.

If you want to you can decouple your client layer from your persistence layer by adding a layer of DTOs. This way you can design your entity model according to what's best for the business/persistence layer and your DTOs according to the way your client wants to present the data.

If you want to use the same objects you can still do that, you should only pay attention to which objects are "in the session" and which are detached, and you won't have any merge issues.

Upvotes: 1

Related Questions