StackOverflowException is thrown when a bag of entities which have a composite-id is retrieved with fetch=join strategy

I check your mappings and how you are working.
You are doing something not necessary and some other bad practices from the point of view of ORM.

BTW

<class name="Item" table="tblitems" lazy="false">
<id name="Id" column="ItemId">
<generator class="guid.comb" />
</id>

<version name="Version" access="nosetter.camelcase"/>

<property name="Name" column="itemname" />
<list name="ItemDetails" access="field.camelcase-underscore" fetch="join"
lazy="false" cascade="all" table="tblDetails">
<key column="itemid" />
<list-index column="DetailId"/>
<composite-element class="ItemDetail">
<parent name="Owner"/>
<property name="Code"/>
</composite-element>
</list>
</class>
and this is the ItemDetail
public class ItemDetail
{
private string code;
private Item owner;

public Item Owner
{
get { return owner; }
internal set { owner = value; }
}

public string Code
{
get { return code; }
set { code = value; }
}
}

The ItemDetail is a value type (don't have a real ID and can be accessed only trough the parent).
There are various others things to say but is better if you use the users forum for support question
http://groups.google.com.ar/group/nhusers

In the users forum we can help you to choose better/right way to mapping and work with your entities (believe me).
There are some others way to map your two entities depending on what you need in your real app.

Bye Frederik, see you in the forum.

P.S. if you want use composite-id take care to override Equals and hashcode with the properties of the composite-id and, in general, use a specific class to represent the Id or use natural-id.

I've added a new testcase (NH1460_FG.zip). I hope it is now more useable for the NH team. I've downloaded the testproject you've refferred to, and created a testfixture which inherits from the abstract TestCase class.

There are 2 tests in the test-case: one which retrieves the entities using a select fetch strategy, and one which retrieves the entities using a join strategy.

While creating the tests, I've also noted another strange thing:

• when I specify fetch='join' in the mapping file, the retrieval of an entity fails.

• when I call SetFetchMode on the criteria, and I specify 'SELECT', the retrievel works.

• when I specify fetch='select' in the mapping file, but override this FetchMode to 'join' by calling SetFetchMode(FetchMode.Join), it seems that retrieving the entity works. ?

(This workaround doesn't solve the problem though when you want to use the ISession.Get() method to retrieve an entity).

Frederik, if you want create useful tests for NH team please follow want Marco done.
Mean:
1) create a separate folder for test using NHibernate.Tests project or EntitiesPersistenceTestEnvironment.7z available here http://groups.google.com/group/nhusers/files
2) attach the test to the JIRA ticket

An useful help is available here
http://www.nhforge.org/blogs/nhibernate/archive/2008/09/06/prepare-your-system-for-nhibernate.aspx

Hope soon we have another blog-post or a wiki about: How to create a test for a bug

Normally, I use transactions, in this example it is possible that I left them out for simplicity
Normally, if I use versions, I use version in all my entities I'll see if I can create a new (better) testcase in the following days.

@Marco
Your test probably find the same problem but is different than the mapping of Frederik

• you are not using cascade

• you are using fetch=join

• Frederik use versions only for child (another strange thing) and you never use it

All this things are not trivial because each change the why on how NH load object.

Interesting Issue, two test for the same problem.