tag:blogger.com,1999:blog-6474777515149871807.post2003068696518326410..comments2024-03-08T10:45:11.911+01:00Comments on Warlock's Thoughts: Spring MVC - Session Attributes handlingvarð-lokkur (warlock)http://www.blogger.com/profile/08196109352954198217noreply@blogger.comBlogger9125tag:blogger.com,1999:blog-6474777515149871807.post-3447457588005189302015-06-18T13:06:32.072+02:002015-06-18T13:06:32.072+02:00Hey thanks man :)Hey thanks man :)puneehttps://www.blogger.com/profile/03790718280491997452noreply@blogger.comtag:blogger.com,1999:blog-6474777515149871807.post-50134278436373984632015-06-03T10:28:05.459+02:002015-06-03T10:28:05.459+02:00superbsuperbAnonymoushttps://www.blogger.com/profile/12431132499431474410noreply@blogger.comtag:blogger.com,1999:blog-6474777515149871807.post-84918251140535735672013-03-09T18:55:51.289+01:002013-03-09T18:55:51.289+01:00Really useful. Thank you :)Really useful. Thank you :)Anonymoushttps://www.blogger.com/profile/05088724411346536434noreply@blogger.comtag:blogger.com,1999:blog-6474777515149871807.post-42315539578593804712012-10-23T07:20:52.831+02:002012-10-23T07:20:52.831+02:00but when i'm using sessionStatus.setComplete()...but when i'm using sessionStatus.setComplete() it showing error in my methodanuhttps://www.blogger.com/profile/10394059041951886131noreply@blogger.comtag:blogger.com,1999:blog-6474777515149871807.post-76811901739146854572012-04-17T10:35:50.891+02:002012-04-17T10:35:50.891+02:00@warlock
It seems that in Spring 3.1 @SessionAttr...@warlock <br />It seems that in Spring 3.1 @SessionAttributes mechanism has been redesigned. Since Spring 3.1 out-of-box uses RequestMappingHandlerAdapter, ModelFactory and SessionAttributesHandler i haven't faced the problems you mentioned. It can happen that the issues you described are still buried within AnnotationMethodHandlerAdapter (actully within HandlerMethodInvoker and milushttps://www.blogger.com/profile/04255791953013506623noreply@blogger.comtag:blogger.com,1999:blog-6474777515149871807.post-9212193054790384672012-02-17T15:55:33.705+01:002012-02-17T15:55:33.705+01:00Thanks for the clear article
As Warlock said, th...Thanks for the clear article<br /><br /> As Warlock said, the current implementation of @SessionAttributes is too bloated for the cleaning step.<br /><br /> However, as always with Spring, the framework is flexible enough to let you inject your own implementation of SessionAttribureStore.<br /><br /> Indeed it is very easy to create your own SessionAttribureStore impl. Just create a POJO with a DOAN DuyHaihttps://www.blogger.com/profile/09461994905762777837noreply@blogger.comtag:blogger.com,1999:blog-6474777515149871807.post-70432758066905187632011-01-22T16:38:15.683+01:002011-01-22T16:38:15.683+01:00I see now days every single library is following A...I see now days every single library is following Annotation based programming model , spring is no exception.<br /><br />Thanks<br />javin<br /><a href="http://javarevisited.blogspot.com/2010/10/why-string-is-immutable-in-java.html" title="Why String is immutable in Java" rel="nofollow">Why String is immutable in Java </a>Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6474777515149871807.post-17074152028175249932011-01-15T07:57:39.949+01:002011-01-15T07:57:39.949+01:00@ernstbusch - agree (and wrote about it a little a...@ernstbusch - agree (and wrote about it a little around ClassCastException in my post ;) ), using @SessionAttributes in complicated application can be very tricky, at least with the default Spring setup, but sometimes it is necessary anyway ... Thankfully it can be tuned using your own SessionAttributeStore implementation :)<br /><br />@Sandeep and @ernstbusch - thanks for the remarks :)varð-lokkur (warlock)https://www.blogger.com/profile/08196109352954198217noreply@blogger.comtag:blogger.com,1999:blog-6474777515149871807.post-82091961267736960282011-01-11T14:09:54.349+01:002011-01-11T14:09:54.349+01:00At first I used Spring's @SessionAttributes to...At first I used Spring's @SessionAttributes to store model objects in the session when the user was creating/editing something. The biggest problem came when the user opened multiple editing forms in different browser tabs because session attributes were getting overriden and only the last tab was actually working.<br />As I found no easy way to overcome this (and other) limitations, I Anonymousnoreply@blogger.com