Databases
StackOverflow2013
Postsdbo
POGuice @SessionScoped annotation causes IllegalArgumentException with Shiro HttpSession
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POGuice @SessionScoped annotation causes IllegalArgumentException with Shiro HttpSession
    primarykey
    data
    text
    <p>I have an Apache Wicket 1.5 application that uses Shiro for security, and Guice for dependency injection. Most of its pages are stateless, but some of my model objects (user data, current menu state, ...) need to be consistent across all requests in the same session. All of these objects have both logic (mostly simple finder methods using remote EJB3 interfaces to access a database) and state, and all of them implement Serializable.</p> <p>Here's a short excerpt that should convey the idea:</p> <pre><code>@SessionScoped public class UsersImpl implements Users, Serializable { private static final long serialVersionUID = 8841809043461673585L; private final Logger log = LoggerFactory.getLogger( UsersImpl.class ); @Inject public UserService users; @Inject public RoleService roles; private UserDTO currentUser; public UserVO findUserByUser( UserVO user ) { UserDTO userDto = null; try { userDto = users.findUserByUser( user.toUserDTO() ); } catch( Exception e ) { log.error( "Error finding user:"+user.id, e ); } return userDto != null ? new UserVO( userDto ) : null; } (...) } </code></pre> <p>I developed and unit tested the classes using <code>@Singleton</code> (for simplicity), and everything works fine this way, but I get frequent errors like this, now that I have switched to <code>@SessionScoped</code> for production:</p> <pre><code>Guice provision errors: 1) Error in custom provider, org.apache.shiro.session.InvalidSessionException: java.lang.IllegalArgumentException: HttpSession based implementations of the Shiro Session interface requires attribute keys to be String objects. The HttpSession class does not support anything other than String keys. </code></pre> <p>Obviously, Guice seems to use some custom Key object to store the objects in the session, and the Shiro HttpSession implementation can't handle that. Strangely enough, though, this exception does not occur for all of the <code>@SessionScoped</code> classes, but certainly for more than one. </p> <p>I have been searching the web like crazy, looking for an idea what I could do - some way to force Guice to use Strings for keys, some other way to make the HttpSession more compatible, anything - but I can't seem to find any helpful information. Also, judging from my search results for the error message, I seem to be the only person on the planet who even has this problem at all... </p> <p>Is there any way to make this work? Or am I doing something wrong here?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USweltraumpirat
    1. USweltraumpirat
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POGuice @SessionScoped annotation causes IllegalArgumentException with Shiro HttpSession
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POGuice @SessionScoped annotation causes IllegalArgumentException with Shiro HttpSession
      1. USartbristol
      1. VTFavorite
    3. VO
      singulars
      1. POGuice @SessionScoped annotation causes IllegalArgumentException with Shiro HttpSession
      1. This table or related slice is empty.
      1. VTUpMod
    1. COHow do you initialize `Shiro`? Trough installing `ShiroModule`?
      singulars
      1. POGuice @SessionScoped annotation causes IllegalArgumentException with Shiro HttpSession
      1. USMilan Baran
    2. COI installed `ShiroAopModule` and a custom one that extends `ShiroWebModule` and has everything you would otherwise put in a `shiro.ini`. That also binds `SessionScoped.class` to `ShiroSessionScope`. There is no separate Module for `UsersImpl` - the interface `Users` is annotated with `@ImplementedBy`.
      singulars
      1. POGuice @SessionScoped annotation causes IllegalArgumentException with Shiro HttpSession
      1. USweltraumpirat
    3. COThe whole setup works fine if I use `@Singleton` instead of `@SessionScoped`: All the injections work, and the entire app runs without errors - except for the fact that it's limited to a single user, of course.
      singulars
      1. POGuice @SessionScoped annotation causes IllegalArgumentException with Shiro HttpSession
      1. USweltraumpirat
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload