Rick Reumann wrote:
On 8/24/05, *David Haynes* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
Rick Hightower does this in his "Clearing the FUD about JSF"
http://www-128.ibm.com/developerworks/java/library/j-jsf1/
He has the XyzBeand and XyzController with the controller containing:
XyzBean xyzBean = new XyzBean();
and then supporting the methods etc. via xyzBean.method() calls. His
Controller is your Action.
See his extremely fine articles for more details.
No offence, but I've looked at that article and it doesn't even
remotely address what this thread is asking about
Well then, I apologize for missing the point.
[snip]
Imagine you need to perform tasks on an Employee - saveEmployee,
getEmployee, etc. Yet, after getting an employee from the backend, you
will then also need a reference to this employee object that you
returned from the backend for use on your page. Someone previously
mentioned use getEmployeeAction (does the business delegate call) and
getEmployee (returns the instance of the Employee object from your
backing bean). Hightower's example is dealing with a calculator and
performing calculator operations - not returning a cacluator for use
in the view..
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?
-david-
