Hi Mike,
Thx for the answers, I'll be looking into the solutions and trying them
out. Certainly the one for x:saveState is going to be very beneficial!
However your answer to my dataTable problem still leaves me with a problem.
The reason that I split the data up in the first place is because I need
to place header text between the different data, specifying the
different costs associated with the purchace. see below
Travel costs
2-room appartment 340.00
reservation costs 30.00
Total travel costs 370.00
Administration Costs
foo1 10.00
foo2 20.00
Insurances
foo1 50.00
foo2 60.00
Total costs 510.00
Thoughts on this?
Colin
Mike Kienenberger wrote:
On 8/11/05, Colin Chalmers <[EMAIL PROTECTED]> wrote:
1. I have a couple of managed beans in session scope. After making the
purchase definate I want to remove them, or reset them in session. Is
there a recomended way of doing this or it simply, find them in the
context and invoke a reset method clearing all data in that object? Or
can I remove the object from facescontext in some way?
You can look at using request-scoped beans and the <x:saveState> component.
The x:saveState component will preserve a target (like your bean) so
long as the x:saveState component specification for that bean appears
on a page. As soon as your user navigates to a page without such an
x:saveState component, it'll be lost.
2. I have to show data from several different lists in tabular format,
in one table to be exact. I tried 3 seperate dataTables under each other
which shows the correct data but looks ugly. Something along the lines
of panelgrid with embedded datatable would probably be appropriate but
is not giving correct result. I need some help on this one
Have your dataTable binding point to a getter method that combines the
three lists into one.
3. Is there some way to show a datatable only if the list data being
provided is greater than zero or does one have to revert to JSTL to
solve this, checking for > 0 in an if statement before writing the table?
Use the rendered attribute. ie, rendered="#{listDataIsNonEmpty}"
4. Is there any way to pass arguments to methods being invoked? I read
somewhere that this was a restriction in EL and was not possible. Is
that the case?
There's a lot of ugly workarounds for this, but there's no direct
support for it.
You can also use an alternate EL.
