It's normal to split your entity (model) and action beans into different classes. You'll run into problems if you try to put the action methods on entities (e.g. Seam annotations have no effect).
With Seam it's up to you whether you use POJOs for action beans or EJB3 Session beans.
Or is that not what you are asking?
You'll run into problems if you try to put the action methods on entities (e.g. Seam annotations have no effect).
Oh i see, so i really have to split actions and model(entity) bean (like it is
shouldnt this difference be reflected in your package structure or would u put all into the same package
-Group.java //entity bean
-ManageGroup.java //action interface
-ManageGroupAction.java //action interface implementation
i noticed when i put actions and beans into the same package and that package contains, lets say 6 entity classes - u will have 18 classes
(6*3 [1 for the entity , 1 for the action interface, 1 for the action implementation]) in one singly package, its gets too huge very quick.
Should i make a subfolder action in every package or do it this way ?
or just like this way
or this way
or finally this way
waht solution would u choose ?
I prefer 2) but i am not sure anymore, can u help please?
I use (3) but it is a personal choice :)
Well, ok that means u have
package in every module, did i understood you right?
I have to decide between 2 and 3, if u say solution 3) works good for you , ill adopt it.
Thank you very much,