Spring 3 @PathVariable problem with slash

[Ronwaldo Cruz]

Hi,

I'm new to Spring 3. I'm trying to use @PathVariable as follows:

    @RequestMapping(value = { "/test/{someString}/test" }, method = { RequestMethod.GET })
    public void test(@PathVariable final String someString) {
        System.out.println(someString);
    }

It works well for URLs like /test/someValueHere/test. However when someString needs to have a slash in it like /test/abc/abc/test, Spring doesn't recognize it anymore as matching the pattern. Previously I do it like /test/**/test in Spring 2.5 but this time I need to use PathVariable to easily extract out the someString value.

Anyone can help? Thanks

[Mark Spritzler]

Ronwaldo Cruz wrote:Hi,

I'm new to Spring 3. I'm trying to use @PathVariable as follows:

    @RequestMapping(value = { "/test/{someString}/test" }, method = { RequestMethod.GET })
    public void test(@PathVariable final String someString) {
        System.out.println(someString);
    }

It works well for URLs like /test/someValueHere/test. However when someString needs to have a slash in it like /test/abc/abc/test, Spring doesn't recognize it anymore as matching the pattern. Previously I do it like /test/**/test in Spring 2.5 but this time I need to use PathVariable to easily extract out the someString value.

Anyone can help? Thanks

Well, to Spring those are two totally different URLs a slash has meaning in a URL. the "**" is just a wildcard the PathVariable isn't a wildcard.

Why would you want someString parameter to be "abc/abc"? Because each PathVariable usually has some kind of meaning and to me "abc" has one meaning and the other "abc" would have a different meaning.

Mark

[Ronwaldo Cruz]

Hi,

Ok. I understand what you mean. abc would be "sort of" a directory structure and then inside it is another abc "directory." But the thing is this is the situation I'm in. I have a url where someString in test/someString/test is a value that can have a slash in it. That is the business requirement. Is there any way of forcing the issue here and extracting someString from the path?

[Mark Spritzler]

Ronwaldo Cruz wrote:Hi,

Ok. I understand what you mean. abc would be "sort of" a directory structure and then inside it is another abc "directory." But the thing is this is the situation I'm in. I have a url where someString in test/someString/test is a value that can have a slash in it. That is the business requirement. Is there any way of forcing the issue here and extracting someString from the path?

The only way around it is to create two methods mapped to the two totally different URL and have one of them call the other

@RequestMapping(value = { "/test/{someString}/test" }, method = { RequestMethod.GET })
public String someMethod(@PathVariable("someString") String value)

@RequestMapping(value = { "/test/{someString}/{otherString}/test" }, method = { RequestMethod.GET })
public String someOtherMethod(@PathVariable("someString") String firstValue, 
                                              @PathVariable("otherString") String secondValue) {
    return someMethod(firstValue + "/" + secondValue)

Now you mapped both versions and the someOtherMethod just calls someMethod so the someOtherMethod is just there to map the other URL and get that slash in there.

Hope that helps

Mark

[Ronwaldo Cruz]

Thanks.

[Qunfeng Wang]

I think that's not a good idea. How about the parameter has one more slash?

I have a same issue. The parameter exists in many rest API. It's annoying to add one more method seldom used to every rest API.

[Mark Spritzler]

qunfeng wang wrote:I think that's not a good idea. How about the parameter has one more slash?

I have a same issue. The parameter exists in many rest API. It's annoying to add one more method seldom used to every rest API.

But in each REST api, each URL is a different resource. Nothing to do with WebPage requests. So another slash would be a different resource. So you would have that mapped to a different method. HATEOAS

Mark

[Mark Spritzler]

Also. Please don't resurrect old threads. This is almost a year old. The poster probably won't see your post anyway, and has already moved on long ago.

Thanks

Mark