This content has been marked as final.
Show 6 replies
-
1. Re: The Seam Lifecycle
gavin.king Oct 16, 2006 7:55 AM (in response to bluetrade)I don't want to say don't use @Service beans, because they most certainly have their place ... but from what you just described it sounds like an application-scoped JavaBean would be perfectly fine....
-
2. Re: The Seam Lifecycle
bluetrade Oct 16, 2006 8:34 AM (in response to bluetrade)thanks gavin. but is it guaranteed that there will only be one instance of a application scoped JB? I don't want to have multiple instances, because they hold a large model in the ram, and that would eat up valuable resources, that's why I figured something "singleton"-like i.e. the @Service would be the right choice...
Thanks,
joey -
3. Re: The Seam Lifecycle
gavin.king Oct 16, 2006 9:13 AM (in response to bluetrade)once instance per process
-
4. Re: The Seam Lifecycle
bluetrade Oct 16, 2006 9:27 AM (in response to bluetrade)thanks, but could you define "process"?
-
-