anonymous wrote :
| It doesn't have to be a repository or something that persists data.
|
Not sure what you mean by that. The whole point of an entity bean is to hold persitent
data.
anonymous wrote :
| I might have entities that are domain objects which I happen to want to inject with
other domain objects that provide certain services (all my business logic is the domain
layer). Shouldn't we be able to do that? Otherwise I'd have to use singletons or
pass the referenced service to my domain object as a parameter in each method call (not
desirable at all)
|
Why not inject the entity bean into the service objects? If you use Seam, you might as
well do things the Seam way.
Regards
Felix
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4066754#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...