Entity with multiple names.

[norman.richards]

There is no reason you can't do this. You just need to have something called "currentUser" and something called "userBeingCreated" in one of your scopes. You can use value="..." to provide different names and you can use required=false to say that the value doesn't have to already exist. Unfortunately, what you can't easily do is use create=true. Instance creation requires seam to have an actual component mapped to that type.

[gavin.king]

The current approach is @Out(scope=..., value=...)

The next release of Seam should support multiple component roles with @Roles({@Role(name=..., scope=...), ....}).

[cesarizurieta]

I have a working patch that implements the @Roles thing.
With this you can annotate a class this ways:

@Name("name")
@Scope(EVENT)
public class Class {
...

Or

@Role(name="name", scope=EVENT)
public class Class {
...

Or

@Roles({
 @Role(name="name1", scope=EVENT),
 @Role(name="name2", scope=SESSION)
})
public class Class {
...

Can anybody try this?

http://jira.jboss.org/jira/browse/JBSEAM-64

The patch patches also the Registration example.

[gavin.king]

Thanks, I had a quick look and it looks about right.

I will take a closer look later.