The Seam Lifecycle

[bluetrade]

Hi,
I have some questions regarding the Seam lifecycle. I have some @Service annotated EJBs, i.e. Singletons, because they are pretty resource intensive, they parse large XML files etc. (is this the best approach btw for this task? - i hear traditional Singletons are evil in a container because the statics are often not cleaned up when redeploying...), but I also wanted to use some Seam functionality (like Injection) in these Services, e.g. the @Log annotation. However, when I try to access the Logger in the start() method, it throws a NullPE. It's understandable, since Seam doesn't seem to be "started" at that point - is there a work-around for that? It seems to me that Seam should support the @Service annotation...

Thanks,
joey

[gavin.king]

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....

[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

[gavin.king]

once instance per process

[bluetrade]

thanks, but could you define "process"?

[gavin.king]

JVM

[bluetrade]

thanks :)