On 8/24/05, Sean Schofield <[EMAIL PROTECTED]> wrote:
I'm a bit confused about what you mean in the above. Are you registering more than one managed bean in reference to an Invoice? My concern is that "getInovice" can either mean 'perform some business action to retrieve an invoice (maybe based on an id) OR "getInvoice" can me simply get the "existing reference to an invoice for use on a form." I'm not sure how your facade pattern here addresses the issue.
I think I'm going to try the "getInvoiceAction" "getInvoice" and use one backing bean with an InvoiceVO nested inside.... although I like the idea of keeping the backing bean and vo as separate managed beans. I don't really know enough about how managed beans work in order to accomplish this later approach. I'll ask my question in reply to that e-mail vs asking it here.
You could also use a facade pattern. We have one in our Struts app
and we're planning on keeping the facade when we move to JSF.
Before you had ...
Facade::getInvoice
InvoiceForm::setInvoice, etc.
InvoiceAction::execute
Now you have ..
Facade::getInvoice
InvoiceBacker::getInvoice
I'm a bit confused about what you mean in the above. Are you registering more than one managed bean in reference to an Invoice? My concern is that "getInovice" can either mean 'perform some business action to retrieve an invoice (maybe based on an id) OR "getInvoice" can me simply get the "existing reference to an invoice for use on a form." I'm not sure how your facade pattern here addresses the issue.
I think I'm going to try the "getInvoiceAction" "getInvoice" and use one backing bean with an InvoiceVO nested inside.... although I like the idea of keeping the backing bean and vo as separate managed beans. I don't really know enough about how managed beans work in order to accomplish this later approach. I'll ask my question in reply to that e-mail vs asking it here.
