Hibernate eager loading broken?  
---------------------------------

         Key: SPRING-29
         URL: http://team.andromda.org:8080/jira/browse/SPRING-29
     Project: Spring Cartridge
        Type: Bug
    Reporter: Peter Friese
 Assigned to: Chad Brandon 


The spring cartridge doc states that if I model a composition between two
classes (and set the multiplicty to "1 to many"), this will result in an eager 
loading collection in the hibernate mapping file, like this:

<class name="sample.BookingImpl" table="BOOKING">
  <set name="items" order-by="BOOKING_FK" lazy="false" outer-join="auto" 
inverse="true" cascade="delete">
    <key>
      <column name="BOOKING_FK"/>
    </key>
    <one-to-many class="sample.ItemImpl"/>
  </set>
</class>

I tried to apply this to my model, but to no avail. Since I am
not using MagicDraw (but Together Designer with a custom made XMI export
filter), I first suspected an error in the produced XMI. After having spent
some time comparing the XMI of Magic and my own XMI, I found that they are
quite similar. 

So I decided to have a second look at the test model for the cartridge, which 
contains quite a
number of compositions - but none of them gets mapped to an eagerly loading
collection. This is why I suspect a bug in the cartridge.


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://team.andromda.org:8080/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Andromda-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/andromda-devel

Reply via email to