[seam-dev] deprecations on Identity

[Shane Bryzak]

Those methods are redundant now, which is why I deprecated them.  
However I do agree that we don't want to cause people to change their 
applications for no reason, so with that in mind there's no reason why 
we can't leave them in there for the next 5 years or however long we 
want.  I prefer though that new developers use the Credentials component 
instead (it's more logically correct), which is why I want to steer them 
away from using Identity via the @Deprecated methods.

Dan Allen wrote:
> Is it really necessary to deprecate get/setUsername() and
> get/setPassword() on Identity? I understand the benefits of having a
> Credentials component to hold this information, and that it can be
> swapped out, but I don't see why the pass through methods on Identity
> cannot be treated as convenience methods. I feel like we are going to
> cause a lot of people to go and change their applications for no
> reason if they are fine with their current authentication setup.
>
> Again, I am thrilled about the new security stuff. I'm just want to
> make sure we don't step on the toes of current rollouts.
>
> -Dan
>
>