ry to make JSF successful.
Regards,
Yee
-Original Message-
From: Simon Kitching [mailto:[EMAIL PROTECTED]
Sent: Sunday, 15 January 2006 12:20 PM
To: 'MyFaces Discussion'
Subject: RE: JSF Flaw: Comopnent not preserving it state
On Sun, 2006-01-15 at 01:18 +0800, Yee CN wrote:
&
On Sun, 2006-01-15 at 01:18 +0800, Yee CN wrote:
> Simon,
>
> It is a lot more complex than it looks on the surface. Looks like I have
> opened a can of worms.
Yep :-)
>
> Firstly Hibernate LazyInitializationException problem is inherent in the
> SessionPerRequest pattern. It is universal to al
sage-
From: Simon Kitching [mailto:[EMAIL PROTECTED]
Sent: Saturday, 14 January 2006 6:48 PM
To: 'MyFaces Discussion'
Subject: RE: JSF Flaw: Comopnent not preserving it state
Rich's point is a good one. If you load an entity from a database using
Hibernate, it is a "live"
om: Richard Wallace [mailto:[EMAIL PROTECTED]
> Sent: Saturday, 14 January 2006 3:04 PM
> To: MyFaces Discussion
> Subject: Re: JSF Flaw: Comopnent not preserving it state
>
> The biggest problem I can see with making the default value for this
> true for the dataTable component
lto:[EMAIL PROTECTED]
Sent: Saturday, 14 January 2006 3:04 PM
To: MyFaces Discussion
Subject: Re: JSF Flaw: Comopnent not preserving it state
The biggest problem I can see with making the default value for this
true for the dataTable component is that the DataModel could very well
be backed by d
The biggest problem I can see with making the default value for this
true for the dataTable component is that the DataModel could very well
be backed by data loaded from an ORM tool such as Hibernate. In this
case, it would be very easy to run into LazyInitializationExceptions or
equivalent.
I definitely consider this a flaw. There is no reason why a dataTable should
behave differently from an inputText. preserveDataModel should be enforced
in all components and enabled by default. It should only be disabled with
explicit settings.
This has been a major stumbling block for me to get a
7 matches
Mail list logo
