Serializable requirement isn't too strict?

[agori]

In a session scoped bean I get error like

The bean Session scoped simple bean 'userBean' org.jboss.webbeans.examples.prova.UserBean,  API types = [Object, UserBean, Serializable], binding types = [@Current] declares a 
passivating scopes but has non-serializable dependencies

The bean is:

@SessionScoped @Named
public class UserBean implements Serializable {

     @Fires Event<User> userEvents;
     
     @Current java.util.Logger logger
        
        ...  
}

I need to declare both fields as transient.
Maybe this is ok for logger, but I don't think this is correct for the webbeans interface Event.

This code as been tested on current trunk.

About logger, I used the @Produces idiom. I think the problem is that scope is the dependent scope,  so it causes the logger to be a session logger and so needs to be serializable.
Should I force 'produces' method to request scope?

[pmuir]

The normal Java rules apply - if you inject something which isn't serializable into a class declared serializable, you will get an error.

You should declare both of these transient.

[agori]

That's ok for java.util.Logger. But Event is a Webbeans class, so why not making it serializable?

Why I don't experience the same strictness in Seam? I can inject an Events component into a session scoped one, without the need of the transient keyword.

[pmuir]

Probably true :-)

File an issue in JIRA...