Re: [Hibernate] Failure to lazily initialize a collection

[Gavin K. <ga...@ap...>]

I knew about an exception in the new Locking code in 1.1.4, 1.1.4b and I
fixed it in CVS. But I must have missed something. Thanks for picking up on
this, Mark. I'll look into it ASAP.

----- Original Message -----
From: "Mark Woon" <mor...@SM...>
Cc: "Hibernate Mailing List" <hib...@li...>
Sent: Saturday, October 12, 2002 11:09 AM
Subject: Re: [Hibernate] Failure to lazily initialize a collection


> A few more details on the exception:
>
> The session is still open when I try to access the lazily initialized
> collection.   The code is as simple as this:
>
>       Gene gene = (Gene)session.load(DbGene.class, "PA6222");
>       Set refSeqs = gene.getReferenceSequences();
>       Iterator it = refSeqs.iterator();
>
> Which triggers the exception.  The NPE in the CVS build looks like a bug
> in the new locking code, but that doesn't explain why I'm getting this
> exception with the 1.1.4b build.
>
> Here's the mapping I'm using for the set:
>
>     <set role="referenceSequences" table="ReferenceSequenceGeneAssoc"
> lazy="true" cascade="all">
>       <key column="geneId" type="string" />
>       <many-to-many column="referenceSequenceId"
> class="org.pharmgen.db.DbReferenceSequence" />
>     </set>
>
> Anyone have any idea what the problem might be?
>
> Thanks,
> -Mark
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> hibernate-devel mailing list
> hib...@li...
> https://lists.sourceforge.net/lists/listinfo/hibernate-devel