Seam 2.1; currentUser or identity?

[chris.simons]

With Seam 2.1, is it still proper to use the currentUser or identity to check properties about the currently logged in User?

Thanks.

[jensaug.jens.augustsson.eu]

Sure.

If U accept a database hit instead of keeping the instance in the Session context, check out
UsingEntityHomeForEntitiesInLongrunningContexts

And if you use new fresh JpaIdentityStore, you can get your hands on that user id by listening to an Event:
(this example uses our domain specific user Entity ProcessUser)

@Observer(JpaIdentityStore.EVENT_USER_AUTHENTICATED)
public void onAuthenticated(ProcessUser u) {
  Contexts.getSessionContext().set("currentUserId", u.getId());
}

...if U use jBPM you may also in this method map domain specific roles to the Actor roles/ group actor ids.

/Jens

[chris.simons]

Cool, thanks - especially for the jBPM reference since we need to do something just like that.

[mocha]

it's also possible to extend the seam Identity to add userId which keeps this all nicely in one place.  currentUser can be factory generated as per the link above.