architectural issue regarding depending objects

[digit0815]

Hi there,

i've got a question regarding storage of composite objects.
in case i need to persist an object having child tied/related to it.
furthermore given is that child objects have changed in the meantime.

do i have to fire every 'save' - for instance in every related EntityHome - on my own or does seam do that?
so, do i have to apply the composite entity pattern on my own?

thx and have fun

[alartin]

Actually, It is only related to your hibernate/JPA mapping rather than Seam.
Seam only provides a Home to manager an entity's CRUD. You need to add anontations to your Entities to mapping the relation and cascade.