This is one of the issues I'm trying to handle internally.
We had two browser sessions opened and update the tables and perform
delete actions.
What we found was that the selection of objects to delete by one user
actually deletes the elements added by another user. And this was
because we work o
ssion
Subject: Re: DataTable Problem
We have quite a lot of such issues. Maybe we should add a check if the
number of rows in the decode phase don´t match with the row number
while rendering.
2005/10/26, CONNER, BRENDAN (SBCSI) <[EMAIL PROTECTED]>:
> Oh, I understand now. Sorry for
to both of you!
>
> - Brendan
>
> -Original Message-
> From: Mike Kienenberger [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, October 26, 2005 11:29 AM
> To: MyFaces Discussion
> Subject: Re: DataTable Problem
>
>
> What Mathias is saying is that you have to maintain t
Oh, I understand now. Sorry for being so dense!
Thanks to both of you!
- Brendan
-Original Message-
From: Mike Kienenberger [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 26, 2005 11:29 AM
To: MyFaces Discussion
Subject: Re: DataTable Problem
What Mathias is saying is that you
hat
> provides the link that we click. The problem is, when we click the link, the
> next page does not get displayed.
>
> - Brendan
>
> -Original Message-
> From: Mathias Brökelmann [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, October 26, 2005 3:05 AM
> To:
ailto:[EMAIL PROTECTED]
> Sent: Wednesday, October 26, 2005 3:05 AM
> To: MyFaces Discussion
> Subject: Re: DataTable Problem
>
>
> The value for #{maintainSkillBean.skillList} must
> not return null or
> an empty list during the decode phase. Place a
> debug-br
, October 26, 2005 3:05 AM
To: MyFaces Discussion
Subject: Re: DataTable Problem
The value for #{maintainSkillBean.skillList} must not return null or
an empty list during the decode phase. Place a debug-breakpoint into
the getter method to see when it is called. You can also use
t:datatable and
The value for #{maintainSkillBean.skillList} must not return null or
an empty list during the decode phase. Place a debug-breakpoint into
the getter method to see when it is called. You can also use
t:datatable and preserveDataModel="true".
2005/10/26, CONNER, BRENDAN (SBCSI) <[EMAIL PROTECTED]>:
the column footers are now rendered before the table body containing
the rows (as it is recomended by html spec). Take a look into the
rendered html code. The result is that your valuebinding in your
footers are called before the value binding of your datamodel.
--
Mathias
> public String
Carsten Fregin wrote:
I would be interested *g*
Sent it down the list yesterday... see thread Hibernate datamodel
werner
I would be interested *g*
Werner Punz <[EMAIL PROTECTED]> wrote on 31.01.2005
17:05:43:
> Ok I got it working...
> the problem was on my side (some bugs in
> the backend bean which interfered with the scope
> of the Hibernate data model)
> The whole thing now works as expected
> except some unwa
Ok I got it working...
the problem was on my side (some bugs in
the backend bean which interfered with the scope
of the Hibernate data model)
The whole thing now works as expected
except some unwanted behavior in the saveState controls
which I have to figure out.
If anybody is interested in the fin
Korhonen, Kalle wrote:
Yeah, you are definitely doing something wrong. The problem in your case
is that you are using two different beans with different scopes. The
properties of the longer-than-request scoped bean are populated before
the action in your request scoped bean is executed, but you are
> -Original Message-
> From: Werner Punz [mailto:[EMAIL PROTECTED]
> Subject: Re: Datatable Problem/Bug second attempt
> Mhh no answer, guess I am alone with my problem...
> Does anybody use the data table at all in combination with a
> search area on the same page?
&
Mhh no answer, guess I am alone with my problem...
Does anybody use the data table at all in combination with a
search area on the same page?
If yes... can any hints towards a best practice pattern, for this case?
Werner
Werner Punz wrote:
Since I got no concrete answer on my problem I'll make a s
Title: Re: Datatable Problem
Thanks alot Werner!
This looks very helpful.
Rian
From: Werner Punz
[mailto:[EMAIL PROTECTED]Sent: Thu 1/27/2005 10:29 AMTo:
MyFaces DiscussionSubject: Re: Datatable Problem
Werner Punz wrote:> Rian Houston
wrote:>>> Hi Werner,>> >
Yes immediate does not change anything regarding my problem.
(true or false no big difference)
Ok, I guess I found the problem, or sort of, I am still
kindof stuck on why this happens.
What happens is that the table is rendered before the query values
are set into the query bean.
What happens now i
Werner Punz wrote:
Rian Houston wrote:
Hi Werner,
Sorry I can't help with your problem. But I would be very interested
in hearing more about how you implemented your custom data model and
how you use it with the dataTable component. I need to do a similar
thing and am struggling with it...
Rian Houston wrote:
Hi Werner,
Sorry I can't help with your problem. But I would be very interested
in hearing more about how you implemented your custom data model and
how you use it with the dataTable component. I need to do a similar
thing and am struggling with it...
Well what I intent
Title: Datatable Problem
Hi Werner,
Sorry I can't help with your problem.
But I would be very interested in hearing more about how you implemented your
custom data model and how you use it with the dataTable component. I need
to do a similar thing and am struggling with it...
TIA
R
have you put the "immediate" attribute on the link?
regards,
Martin
On Thu, 27 Jan 2005 16:18:06 +0100, Werner Punz <[EMAIL PROTECTED]> wrote:
> Hi, I have a weird problem, where I dont know what the cause is.
> Following Situation, I am trying to do a search form with a result
> data table wit
21 matches
Mail list logo
