[b]Mapping documents:[/b]

<class name="Person" table="PERSON">
...
<set name="subjectAddress" lazy="true">
<key column="SUBJECT_ID"/>
<one-to-many
class="SubjectAddress"/>
</set>
</class>

<class name="SubjectAddress"
table="SUBJECT_ADDRESS">

...
<many-to-one name="emailAddress"
class="EmailAddress"
column="ADDRESS_ID"
outer-join="true" insert="false" update="false"
cascade="none"/>
</class>

Whe I get one Person
select pers from Person where pers.subjectId=:sid
I get an:
No row with the given identifier exists: 2528, of class: EmailAddress
because that person doesn't have an email address.

What am I doing wrong in preventing Hibernate loding the entire object graph?

I've set hibernate.max_fetch_depth but I did not obtained the desired result.

Please, at least give me a hint.
I'm sure you don't give an answer to many (usualy stupid) questions just to avoid encouraging lack of sduty and superficiality from the developer side.

I can assure you I've read the book. It's possible to have overlooked something. Now I'm too tierd and don't have enough time to start all over again. Please help me.

I've remembered something. Lazy fetching for assocations cand be done using lazy="true" for a class or the proxy attribute.
I also removed the outer-joined attributes from my relation mapping to avoid overridng the fatching strategy.

What else should I pay attention to?

Use a <one-to-one><formula></one-to-one> mapping instead of a <many-to-one> in HB3.