Optional path segments in Spring MVC

Question

Reading this (Spring 3) article from 2010, it discusses using an extension to provide a convenient way to include optional path segments:

@RequestMapping("/houses/[preview/][small/]{id}")
public String handlePreview(@PathVariable long id, @PathVariable("preview/") boolean preview, @PathVariable("small/") boolean small) {
    return "view";
}

I know I could just implement a number of request mappings to achieve the same effect:

@RequestMapping(value="/houses/preview/{id}")
...

@RequestMapping(value="/houses/{id}")
...
~~~ snip ~~~

But depending on the number of possible permutations, it seems like a very verbose option.

Does any later version of Spring (after 3) provide such a facility? Alternatively, is there any mechanism to chain portions of the request URL to feed a larger response method signature?

Update

This answer to a question relating to sharing path variables and request parameters suggests an approach like:

@RequestMapping(method=RequestMethod.GET, value={"/campaigns","/campaigns/{id}"})
    @ResponseBody
    public String getCampaignDetails(
         @PathVariable("id") String id)
    {
        ~~~ snip ~~~

But the path variable cannot be set to null. Just going to /campaigns will return a 400 response.

Nearly, Javi's answer with the multiple request values - value={"/campaigns","/campaigns/{id}"} is very nearly there, but I'd like to map fixed segments in the URL. — Michael
– Michael, Commented Sep 11, 2014 at 10:05
this question already discussed on one forum, this is same asked here: java.dzone.com/articles/spring-3-webmvc-optional-path — user3145373 ツ
– user3145373 ツ, Commented Sep 11, 2014 at 10:07
Yes, that's the article I link to in my question... hence why I'm asking for alternatives. ;) — Michael
– Michael, Commented Sep 11, 2014 at 10:11
If all else fails, you could always rewrite the URLs with filter like this one: tuckey.org/urlrewrite — Krešimir Nesek
– Krešimir Nesek, Commented Sep 11, 2014 at 13:07

Tunaki · Accepted Answer · 2016-04-13 09:58:28Z

8

Why you don't use java.util.Optional if you are using Java 1.8. To take your later example, you can avert a 400 response with put a Optional<String> instead of String representing your eventualy path like this:

@RequestMapping(method=RequestMethod.GET, value={"/campaigns","/campaigns/{id}"})
@ResponseBody
public String getCampaignDetails(
     @PathVariable("id") Optional<String> id)
{ 
  if(id.isPresent()){
      model.addAttribute("id", id.get());//id.get() return your String path
  }
}

edited Apr 13, 2016 at 9:58

Tunaki

138k46 gold badges370 silver badges443 bronze badges

answered Apr 13, 2016 at 9:36

Tanorix

2302 silver badges16 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Optional path segments in Spring MVC

1 Answer 1

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related