Hi Bjørn,
For your last question. Depending on what you want to do - if there is
no action to perform except navigation to a new page it is enough by
just setting the action attribute to the string representing your
outcome in the faces navigation case e.g. action="success". For the
actual binding there are several options; you could pass values on the
requestScope or sessionScope, and pull them off from there. For most of
the time I have, personally, been using value bindings pointing to a
property in my managed bean. This way I can easily manipulate the value
of the property before any values are pulled in by the "new" page.
Thanks
- Jonas
Jesse Alexander (KBSA 21) wrote:
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
