[
https://issues.apache.org/jira/browse/CXF-6853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15218154#comment-15218154
]
Jim Ma commented on CXF-6853:
-----------------------------
OK. The description I added is probably misleading. I tried to modify a bit to
see if this is better now.
I am not sure if this a sensitive change and it totally breaks the match
request with encoded path value. But anyway, I changed your case a bit to
demonstrate this issue and you can start to look what can we do to fix this
issue.
> Support encoded value in @ApplicationPath
> -----------------------------------------
>
> Key: CXF-6853
> URL: https://issues.apache.org/jira/browse/CXF-6853
> Project: CXF
> Issue Type: Task
> Components: JAX-RS
> Affects Versions: 3.1.6, 3.0.9
> Reporter: Jim Ma
> Assignee: Sergey Beryozkin
> Fix For: 3.0.10, 3.1.7, 3.2.0
>
>
> If @ApplicationPath value is an encoded value, if client send request to
> http://localhost:8080/Application!/myresource and get 404 .
> @ApplicationPath("ApplicationPath%21")
> public class MyApp extends Application {
> public java.util.Set<java.lang.Class<?>> getClasses() {
> Set<Class<?>> resources = new HashSet<Class<?>>();
> resources.add(MyResource.class);
> return resources;
> }
> }
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
