SEC-270: Saved Request is not serializable #531

Closed
spring-issuemaster opened this Issue May 21, 2006 · 2 comments

Comments

Projects
None yet
1 participant
@spring-issuemaster

Luke Taylor(Migrated from SEC-270) said:

Upgrading to latest snapshot, I now get a problem with the app server complaining about non-serializable objects being stored in the HttpSession:

11:32:34,524 DEBUG [ExceptionTranslationFilter] Authentication entry point being called; SavedRequest added to Session:
SavedRequest[http://
11:32:34,524 ERROR [CHSExceptionHandlingFilter] Exception raised:
java.lang.IllegalArgumentException: Only java.io.Serializable, javax.ejb.EJBObject and javax.ejb.EJBHome instances can b
e bound to a session in a distributable web-application, not: SavedRequest[](class org.acegisecurity.ui.savedrequest.SavedRequest)
at com.evermind.server.http.EvermindHttpSession.setAttribute(EvermindHttpSession.java:97)
at com.evermind.server.http.ClusteredHttpSession.setAttribute(ClusteredHttpSession.java:65)

the SavedRequest class should be made serializable to avoid this.

@spring-issuemaster

This comment has been minimized.

Show comment
Hide comment
@spring-issuemaster

spring-issuemaster May 22, 2006

Ben Alex said:

Luke, could you please take a look at this ASAP before we release 1.0.0 final on Friday? We need to ensure this works correctly given it’s a refactoring.

Ben Alex said:

Luke, could you please take a look at this ASAP before we release 1.0.0 final on Friday? We need to ensure this works correctly given it’s a refactoring.

@spring-issuemaster

This comment has been minimized.

Show comment
Hide comment
@spring-issuemaster

spring-issuemaster May 23, 2006

Luke Taylor said:

I made the class serializable and it’s working happily with the latest snapshot.

Luke Taylor said:

I made the class serializable and it’s working happily with the latest snapshot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment