I consider example 2 the better approach. Relationships are quite complicated to manage, so it is better to keep this logic in the session bean layer and hide it from the client.
This way, you can change e.g. CascadeTypes of the relation without having to change client code.
But this are just my personal opinion, don't consider it a design pattern ;-).
yes I agree that example 2 is better because when you use that way it is possible to change the view-technology if that is necessary.
But I was not sure if those methods should be part of the ejbs.
Thanks for your answer!
Any other opinions?