+1 for the change
too.
Sorry Chris but what
you are saying here does not make sense to me.
In the rendering your
model is going to get accessed, this model may contain a lazy loaded
collection. So you still need to have the hibernate session running at
rendering time.
Unless you would have
accessed the lazy collection before, causing it to load, but in order to do
that in a generic way you would pretty much have to copy the behavior of
rendering (without writing to the output stream) and that would (I m o) be
wrong.
I you see things
different let me know.
Maurice
-----Oorspronkelijk
bericht-----
Van: Christopher
Turner [mailto:[EMAIL PROTECTED]
Verzonden: dinsdag 22 maart 2005
10:00
Aan:
'[email protected]'
Onderwerp: RE: [Wicket-develop] major
rendering phase change
I'm +1 for this change having already discussed it
with Jon previously. I think the decoupling of making the structure of the
page from the rendering also has some other advantages. On particular I can
think of right away is that Hibernate lazy loaded collections are easier
to use as you don't need to keep the session factory/transaction active for
the whole rendering process.
Regards,
Chris
>
> given a particular problem in versioning and some
anticipation of a
> horde of other problems, i think we need to
change our model for
> rendering components a little. eelco and
maurice verbally agree, but
> we'd like any feedback from the list too.
the versioning problem is
> that urlFor() can be called during rendering to
create a url
>
of version
>
N. if a component further down the page makes a structural
> change while
> rendering,
it will increase the version at that time,
> resulting in urls
> further down
the page having version N + 1. the root problem here is
> one that
chris and i wanted to fix some time ago and one that seems
> worth
fixing: once rendering begins, the component hierarchy
> should be
> immutable. any attempt to
change the structure during
> rendering would
> result in an exception. to
implement this change, we'll have
> to change
> ListView (yet again... sorry juergen!!) so that
it has a component
> building (populate) phase and a render phase
which are decoupled. i
> think this is a really good change, but i could
be missing something
> too... does anyone see any problems with
this?
>
>
jon
>
>
>
>
-------------------------------------------------------
> SF email is sponsored by -
The IT Product Guide
> Read honest & candid reviews on hundreds of
IT Products from
> real users. Discover which products truly live up
to the
> hype.
Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396>
&op=click
>
>
_______________________________________________
>
> Wicket-develop mailing list
[email protected]
> https://lists.sourceforge.net/lists/listinfo/wicket-develop
>
>
