Do I really have to create object instance before jsf can update its value?

Question

Hello,
I have jsp page with following fragment:
<h:inputText value="#{myBean.obj.value}"/>
myBean is defined as managed bean of class MyBean:
public class MyBean {
     private MyObject obj;
     public object getObj() { return obj; }
     public void setObj(MyObject obj) { this.obj = obj; }
MyObject is a POJO with getter and setter for property "value".
Now, when I display this jsp page, inputText will be empty, since getter for "obj" returned null. If I enter something in this inputText and submit the page I will get:
PropertyNotFoundException: Error testing property 'value' in bean of type null
This exception was thrown in PROCESS_VALIDATIONS phase. As I see, JSF is expecting getter for "obj" to return MyObject instance, where instead it returns null.
My question is: do I really have to have already created instance of object for validation to succed?
I know that this problem is easy to solve by placing
     private MyObject obj = new MyObject();
in class definition or similar initialization in constructor, but..
What if "obj" is a hibernate bean, that has a full tree of other hibernate beans as properties... In this case, creating a new instance of "obj" and initializing all of it nodes, is no more "one line of code" task, but instead 20 lines of, IMHO, unnecessary code.
So I was wondering why is JSF unable to create new instance of object whose properties is trying to update?
Regards,
Igor

Answer 1

Thanks for reply,
I'm aware of jsf IoC, but this does not simplify my problem.
In my case MyObject is class used by Hibernate and can be something like:
public class Employee {
private String name;
private Workgroup workGrp;
private Residence res;
// ... more properties, getters, setters
public class Residence {
private State state;
// ... more properties, getters, setters
So, in order to fully create Employee instance, I have to create and set its Workgroup and Residence properties, and then create and set State inside Residence...etc. Defining all hibernate classes as managed beans, and making dependancies between them cannot solve this problem.
Since I don't want to add constructors or initializers to hibernate classes, the only solution I can come up with is to do manual creation:
obj = new Employee();
obj.setWorkGrp(new Workgroup());
obj.setRes(new Residence());
// ...etc
and place this code in obj's getter to be executed if obj is null. This is the reason I was wondering why can't this be done by jsf automaticly?