You can think of a home object as providing the necessary methods for CRUD - you certainly don't have to use them - most of the examples don't...
i coded the wizard using a Stateful EJB because i initially thought i needed it for only flushing after completion of registration (conversation end) and keeping state between requests and it worked.
After giving it some more thought and understanding the process a bit more, i changed to a Home object that calls userHome.persist() after jpdl completion and after battling conversation propagations and correct action linking, i got it to work.
Right now i'm coding Home objects that delegate database logic to simple DAO's and it's working so i'll stick with it for now :)
i'm really loving the programming model.
That seems counter intuitive to me - Home objects are really a generic DAO pattern.
hum i see. i was following seam wiki example. i this case i see the dao's more like helper classes for hql related stuff and database logic, i'm using home beans as actions listeners. im still on the learning curve :)