Updates:
Status: New
Labels: -Priority-Medium -Milestone-Release2.0 Priority-Low
Comment #1 on issue 271 by limpbizkit: Scopes.SINGLETON + null doesn't work
http://code.google.com/p/google-guice/issues/detail?id=271
I investigated what it would take to fix this...
The problem is that for HTTP request and session scopes, there's no way to
differentiate between an attribute
that's null and one that's unset. Ie. there's no API equivalent to
Map.containsKey(). So for null to work, we'd
have to create a token value that stands-in for null. This is clumsy.
I'm downgrading this to low priority. If it's an actual problem for you or
your app, please comment below and
I'll increase the priority. As it stands, I'd like to defer adding the
hacks that will make this work until there's
real-world demand.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"google-guice-dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/google-guice-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
