Home/ Questions/Q 932495
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-15T20:40:39+00:00

I’m new to JSF and am wondering if I got things right. Let’s say

  • 0

I’m new to JSF and am wondering if I got things right. Let’s say I have a simple CMS that makes it possible to write pages.

First, I define a JPA entity called Page:

@Entity
public class Page {

  @Id
  @GeneratedValue(strategy = GenerationType.AUTO)
  @Column
  private Long id;

  @Column private String title;

  @Column private String content;

  // getters & setters ...

}

Then I would like in a view to create Page-s. For that, it looks like I need a page bean of some sort. For now I handled things like this:

@Model
public class PageBean {

  private Page page = new Page();

    public String getTitle() {
      return page.getTitle();
    }

    public void setTitle(String title) {
      page.setTitle(title);
    }

    // rest of properties & getters & setters ...

    public void save() {
      // persist using EntityManager
    }
 }

My question is the following one: given that my JPA entity model and the model I want to use in the views are most of the time exactly the same, is there a way of avoiding to have to create a batch of getters & setters in the PageBean?

I read somewhere that you should not use a same bean as JPA entity and JSF model bean (because JSF does repeated calls to getters that may affect JPA), yet I do wonder if there is not a simpler way that would help avoiding this kind of code duplication. Especially when you’ve got an application with a large model and in many instances do not require anything special in the view beans, it looks like this can get quite cumbersome.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    […] given that my JPA entity model and the model I want to use in the views are most of the time exactly the same, is there a way of avoiding to have to create a batch of getters & setters in the PageBean?

    I don’t see the point of using a wrapper around an Entity and adding such a layer is indeed duplication. Just use the entity from your JSF page. Yes, this introduce some sort of coupling between the view and the domain but, in general, modifying the database usually means adding or removing fields on the view. In other words, I don’t buy the “decoupling” argument and I’ve written enough extra layers, mapping code, boilerplate code, etc to favor the simple approach when possible.

    I read somewhere that you should not use a same bean as JPA entity and JSF model bean (because JSF does repeated calls to getters that may affect JPA)

    I’d be interested if you could provide a reference but a wrapper class (delegating calls to the entity) is not going to change anything if there is a problem somewhere.

    Just in case, some additional resources:

    • 0