SessionScoped or ConversationScoped beans in Seam Cron Module

[suikast42]

Hi guys,

is it possile to use seam cron with SessionScoped or ConversationScoped beans??

If I try this I get an Exception with the Errorcode WELD-001303 No active contexts for scope type javax.enterprise.context.SessionScoped.

I hoped that seam cron can do better work then EJB Timerservice. U can't use the Timerservice of EJB for Stateful beans. So the same here ?? . I hope thats planed for the future.

[lightguard]

No, as the error states, those contexts aren't available. Seam Cron effectively runs in the background and is not tied to a request, or even an HttpSession. You can't guarantee those scopes will be active.

[suikast42]

And whats about custom scopes ??

[lightguard]

A custom scope should be okay, depending on when it's active.

[suikast42]

ThanksI'll try and an give a feedback

[tdtappe]

And would it be possible to programmatically start a session/conversation when the cron job is triggered?

The problem is that all my business logic heavily depends on session/conversation/request scoped beans.

[lightguard]

No, probably not because they're bound to an HttpSession. In your case, I'd look at either creating your own scopes or seeing how you can break things up into to composite parts and build things up with injection, probably having the small bits be DependantScoped.

[tdtappe]

Or is it somehow possible to fake an HttpSession?

As I am not very familiar with custom scopes how would I do such a thing? If I got you right I might introduce some new scopes like MySessionScoped, MyConversionScoped and MyRequestScoped.

These scopes have to be bound to standard SessionScoped, ConversationScoped and RequestScoped for normal (non-cron) usage. And in case of cron-usage I have to start/end these scopes on my own. How can these two things be done?