If you have an existing server-side domain model and are using Hibernate use
the HibernateAssembler. If you don't have any current server-side code and just
want to expose some tables in your database to clients use the SQLAssembler.
It really comes down to whether it makes sense for your client
Hi,
I'm still struggling with a many-to-many example that I'm creating, but
seeing what I've done so far may be helpful to you. My .java and
.hbm.xml files were auto-created using HibernateTools (with a few
tweaks) and contain files for the middle table. While I don't know
Hibernate very well,
Haven't done it yet... been
using Hibernate 2.1.8 for now in the integration layer with Flex as the
presentation layer. It shouldn't be any different. What problem are you
experiencing?
Dimitrios "Jimmy" Gianninas
RIA Developer
Optimal Payments Inc.
From: Rich Tretola [mailto:[EMAIL P
ationException: could not
> initialize proxy - the
> owning Session was closed
>
>
>
> Any idea what I might be forgetting?
>
>
>
> Ryan
>
>
>
> _
>
> From: Steven Shaw [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, April 12, 2005
closed
Any idea what I might be forgetting?
Ryan
From: Steven Shaw
[mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 12, 2005 7:22 PM
To: flexcoders@yahoogroups.com
Subject: Re: [flexcoders] Hibernate
You will want to watch your server log closely as you probably are
getting
You will want to watch your server log closely as you probably are
getting errors in there about lazy instantiation. Putting lazy="true"
in your mapping file does not guarantee that the association will be
instantiated. It depends in max-fetch-depth and perhaps other things.
You could try using
6 matches
Mail list logo
