StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POSpring 3 <mvc:interceptors> flawed?
primarykey
Id
7505968
data
AcceptedAnswerId
7520892
AnswerCount
2
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-09-21T20:07:59.140
FavoriteCount
1
LastActivityDate
2011-11-10T21:35:06.347
LastEditDate
2011-09-21T21:28:13.857
LastEditorUserId
957130
OwnerUserId
608794
ParentId
0
PostTypeId
1
Score
3
ViewCount
1024
LastEditorDisplayName
text
Body
I have a Spring 2.5.x application which I'm migrating to Spring 3 and just bumped into a little problem. I have an handler mapping like so: <pre><code><bean id="handlerMappings1" class="org.springframework.web.servlet.handler.SimpleUrlHandlerMapping"> <property name="interceptors"> <list> <ref bean="interceptor1" /> <ref bean="interceptor2" /> .... <ref bean="interceptorN" /> </list> </property> <property name="urlMap"> <map> <entry key="/url1.html" value-ref="controller1" /> <entry key="/url2.html" value-ref="controller2" /> .... <entry key="/url100.html" value-ref="controller100" /> </map> </property> </bean> </code></pre> and another one like this: <pre><code> <bean id="handlerMappings2" class="org.springframework.web.servlet.handler.SimpleUrlHandlerMapping"> <property name="urlMap"> <map> <entry key="/urlA.html" value-ref="controllerA" /> <entry key="/urlB.html" value-ref="controllerB" /> .... <entry key="/urlN.html" value-ref="controllerN" /> </map> </property> </bean> </code></pre> I'm slowly replacing both with <code>@RequestMapping</code> annotations with a <code><context:component-scan></code> (which basically registers a <a href="http://static.springsource.org/spring/docs/3.0.x/javadoc-api/org/springframework/web/servlet/mvc/annotation/DefaultAnnotationHandlerMapping.html" rel="nofollow"><code>DefaultAnnotationHandlerMapping</code></a>). In Spring 3 I saw the <a href="http://blog.springsource.com/2009/12/21/mvc-simplifications-in-spring-3-0/" rel="nofollow"><code><mvc:interceptors></code></a> tag which can be used to add interceptors to certain URLs but you can specify only one interceptor, at least that's what I see <a href="http://www.springframework.org/schema/mvc/spring-mvc-3.0.xsd" rel="nofollow">from the schema</a>. From what I can figure, I have to register one of these for each interceptor which will duplicate all my URLs for as many times as I have interceptors (and I don't even know in what order they will run). On the other hand I can't add the iterceptors on the <code>DefaultAnnotationHandlerMapping</code> because they will run for all my controllers annotated with <code>@RequestMapping</code> and I don't want that. So how can I specify interceptors is Spring 3 for some URLs, without repeating the URL's and keeping the URL to controller mapping based on the <code>@RequestMapping</code> annotation?
Tags
<java><spring><model-view-controller><controller><spring-3>
Title
Spring 3 <mvc:interceptors> flawed?
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USMarcin Pietraszek
UserOwnerUserId
1. USElenaT
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POSpring 3 <mvc:interceptors> flawed?
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POSpring 3 <mvc:interceptors> flawed?
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 POSpring 3 <mvc:interceptors> flawed?
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTApproveEditSuggestion
CommentsPostId
1. This table or related slice is empty.

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.