Currently i am calling EJB 3
Session Beans from JSF 2
. However, i am not sure if i should be passing JSF managed beans into EJB?
Assuming that whatever on the form (and thus the backing bean) was everything i needed to persist through the EJB layer, should i clone out all the attributes by hand into a transfer object, or is there a better way of doing this?
The backing bean though POJO
is heavily annotated with JSF lifecycle tags (Such as @ManagedBean
) and resides in the Web project
while the EJBs reside separately in the EJB project
.
I was trying to do the same with CDI and the main diffrence (excluding using
@Named
instead of@ManagedBean
) was that I had to initialize my transport object in the Controller class.So instead of:
private Product product;
I had to use:
private Product product = new Product();
Maybe it will help someone :)
It sounds like as if you've tight-coupled the model with the controller like as shown in most basic JSF tutorials. You should decouple the model from the controller into its own class. As you're using EJBs, the chance is big that you're also using JPA (how else would EJBs be really useful for persistence?), you can just use the existing JPA
@Entity
class as model.E.g.
with
which is to be used as