One thing to be aware of is that the same db-row, in two different
Hibernate-Session, corresponds to two different objects. So with
session-per-request, if your PSModel is loaded in one request, and your
value-parameter-object in another. If you don't override
Object.equalsappropriately, Tapestry cannot know which list member to
show for a given
value.

2007/8/28, Jan Vissers <[EMAIL PROTECTED]>:
>
> Hi,
>
> I'm witnessing some 'interesting' behavior, using lazily loaded
> collections (Hibernate) combined with PropertySelectionModel stuff. Before
> getting into too much detail - using my JUnit tests I can prove that
> traversing the (nested) objectgraph actually has the information (albeit
> via CGLIB proxies). When using this in my T4.1.2 page however, I see that
> the correct poplist value doesn't get selected. In a read only version of
> the page on the other hand - where the poplist is dynamically replaced by
> a readonly display item - the information is shown.
>
> Is there something that I should be aware of in using T4/Hib3 regarding
> the selectionmodel component?
>
> -J.
>
> BTW: I'm using OpenSessionInView provided by Spring.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Marcus Schulte
http://marcus-schulte.blogspot.com

Reply via email to