Commonly, the post is related to task when we deal with JSF managed beans.
TO – transfer object for DAO. It presents a big temptation to use TO as a field of JSF Bean.

For ex. in this case we have a TO:

public class SomeTO {
  private String id;
  private String name;
  private String value;
}

TO is used by DAO:

public class SomeDAO {
  public SomeTO get() {
    return new SomeTO();
  }
}

A JSF Bean (wrong way!):

public class SomeBean implements Serializable {
  private SomeTO to;

  public SomeTO getTo() {
    if (to == null) {
      to = new SomeTO();
    }
    return to;
  }
}

And so, on page:

 <p:inputText id="name" value="#{SomeBean.to.name}" />

BUT! A little problem occurs here. We lost the most important thing – loose coupling
So, the right way is to use next:

public class SomeBean implements Serializable {
  private String id;
  private String name;
  private String value;
}

And then, on page:

 <p:inputText id="name" value="#{SomeBean.name}" />

Yes, we duplicate the code. But save it free if we decide to change TO anytime.
Be sure for the mistake!
JSF beans are the part of presentation and they must be independent out of core.