In my (limited) experience:
EntityHome is most useful when you need to do CRUD operations on a single entity. It makes it super-convenient if you do things the "seam-gen way".
If you don't want to do things that way, it can be hard to work with. So, for example, if you want a component that does CRUD simultaneously on multiple entity objects, then I think you're better off with an EntityController.
EntityHome extends EntityController, by the way, which is why most of the methods are the same. EntityController really just provides a ton of convenience methods.
I find that I use EntityController more often than EntityHome.
As Matt says. EntityHome is great for scaffolding CRUD, EntityController is great if you are writing more complex components which control entites.
I got it. Thank you so much, Matt and Pete. And also appreciate the Seam team's great work.
in the examples that come with seam, which ones use EntityHome and what ones use EntityController? I would like to take a look at their implementations.
seamdiscs is the only one my IDE search found for EntityController.
EntityHome is used in the wiki, seamdiscs, quartz, and seampay
Thanks Matt I appreciate your help.