I don't disagree with the assertion that it shouldn't be necessary.
We've got a bit of a special case, though, where we need to get the User
from the Session. Otherwise, we've got some restructuring to do. It
may not be worthwhile for a single case, though. I'm OK with a little
smell in that instance. Should we encounter more of this, then it'll be
time to refactor.
Thanks for the information!
Dave
Musachy Barroso wrote:
You can get it from ActionContext.getContext().getSession(), but I second
Dave's opinion.
On Wed, Nov 19, 2008 at 1:22 PM, David C. Hicks <[EMAIL PROTECTED]> wrote:
Should I take that as a "no" ?
Dave Newton wrote:
--- On Wed, 11/19/08, David C. Hicks wrote:
Is there a way to get hold of the Session object from inside
a Validator or TypeConverter?
Why would you want to? That smells like an unnecessary dependency.
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]