Interesting; I may have to do some experimenting then. I confess I
just kind of assumed it wouldn't work because the Hibernate session wasn't
that robust (few database related objects survive being passed between
physical boxes in my experience). Maybe the lads at Hibernate got it right
though.
--- Pat
> -----Original Message-----
> From: Schulte Marcus [mailto:[EMAIL PROTECTED]
> Sent: Thursday, May 19, 2005 11:06 PM
> To: 'Tapestry users'
> Subject: RE: Hibernate + Spring: LazyInitializationException
>
> > -----Original Message-----
> > From: Patrick Casey [mailto:[EMAIL PROTECTED]
> > Sent: Thursday, May 19, 2005 10:19 PM
> > To: 'Tapestry users'; [EMAIL PROTECTED]
> > Subject: RE: Hibernate + Spring: LazyInitializationException
> >
> >
> >
> > Isn't that pattern going to break down in a clustered
> > environment
> > though? I don't believe a Hibernate session will survive
> > being serialized
> > and shipped to another (different) web server if the
> > HTTPsession gets passed
> > around.
>
> Not in general, at least, Hibernate-Sessions claim to be Serializable (by
> implementing it). If your domain objects are serializable, I don't see
> more
> of a problem than you'd have with any other pattern.
> But, to be honest, I never really tried, because up to now I havent't had
> users real demand transparent failover. Usually they're much more
> concerned
> with my other bugs :(.
>
> Marcus
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
