On 8/24/05, David Haynes <[EMAIL PROTECTED]> wrote:
Well for example after you used your backing bean to "get an employee" (getEmployee method?), you would then want to display the employee name on the page.. so you might have...
employeeBackingBean.employee.name
But that above would attempt to call 'getEmployee' which, if where my initial confusion on 'best practice' came from since 'getEmployee' could either mean 'get me the instance of the employee object from my backing bean' or 'call some backend method to get me an instance of the employee from the backend.'
--
I'm confused here. If the EmployeeBean object is embedded in the
EmployeeController and all the methods of EmployeeBean are available via
the EmployeeController, why do you need the EmployeeBean directly?
Well for example after you used your backing bean to "get an employee" (getEmployee method?), you would then want to display the employee name on the page.. so you might have...
employeeBackingBean.employee.name
But that above would attempt to call 'getEmployee' which, if where my initial confusion on 'best practice' came from since 'getEmployee' could either mean 'get me the instance of the employee object from my backing bean' or 'call some backend method to get me an instance of the employee from the backend.'
Rick
