Hi Bj�rn In the project I am actually working on, we decided that our managed beans cover one usecase and therfor contain quite some logic and reducing the number of "data-transfers" between mangaed beans... The actual business-logic is packed within service-objects which are served by a factory and called from the managed beans. The service objects will then call the dao-layer or some other backend to do persistence-work.
Whether this is the "best practise"? I do not know, but it works (so far) for our project on which 4 people are working full time plus one JSF component developer. hth Alexander -----Original Message----- From: Bj�rn T Johansen [mailto:[EMAIL PROTECTED] Sent: Monday, May 23, 2005 8:52 AM To: MyFaces Discussion Subject: Best practice? I was wondering what's the best way of handling the following: - A managed bean need to be "filled" with data from a database using DAO methods; is it best just to pass the managed bean as parameter og should one use another VO bean and populate the managed bean from the VO bean? - when moving to a page, some fields need to be filled with existing values, is this best done in the action method that "calls" the new page and value binding against a managed bean for that page or is there another better way of doing this? Regards, BTJ -- ----------------------------------------------------------------------------------------------- Bj�rn T Johansen [EMAIL PROTECTED] ----------------------------------------------------------------------------------------------- Someone wrote: "I understand that if you play a Windows CD backwards you hear strange Satanic messages" To which someone replied: "It's even worse than that; play it forwards and it installs Windows" -----------------------------------------------------------------------------------------------
