[jira] [Commented] (FEDIZ-19) Single Sign Out
[ https://issues.apache.org/jira/browse/FEDIZ-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13434967#comment-13434967 ] Yang Hua Jie commented on FEDIZ-19: --- Sign out is one of the basic functions. I tried to expire the tomcat sessions, but no luck, after a browser refresh, it still can login. I also tried to clear the browser history, it do sign out the current user. But it should not like that. > Single Sign Out > --- > > Key: FEDIZ-19 > URL: https://issues.apache.org/jira/browse/FEDIZ-19 > Project: CXF-Fediz > Issue Type: New Feature >Reporter: Romain Manni-Bucau > > The goal is to invalidate all sessions of "related" webapps with a single > action (button). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CXF-4473) PathParam null when @Path annotations are the same
[
https://issues.apache.org/jira/browse/CXF-4473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13434990#comment-13434990
]
Sergey Beryozkin commented on CXF-4473:
---
Hi - I can not reproduce with the tests.
Can you please provide a simple war or maven based project ?
> PathParam null when @Path annotations are the same
> --
>
> Key: CXF-4473
> URL: https://issues.apache.org/jira/browse/CXF-4473
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
>Affects Versions: 2.5.4
> Environment: java version "1.6.0_24"
> OpenJDK Runtime Environment (IcedTea6 1.11.3) (6b24-1.11.3-1ubuntu0.12.04.1)
> OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode)
>Reporter: Chris Eineke
>
> For some reason, the JAX-RS runtime doesn't provide the value of a
> @GET-annotated method and @PathParam-annotated method parameter if another
> @PUT-annotated method with the same @ParamParam-annotated method parameter
> has the same @Path annotation:
> @GET @Path("/users/{username}/foo")
> public Foo getFoo(
> @PathParam("username") String username)
> @PUT @Path("/users/{username}/foo")
> public Foo setFoo(
> @PathParam("username") String username,
> Foo foo)
> The runtime correctly invokes the first method for a GET. If I change the
> last path segment of the first method to anything but "foo", the runtime will
> provide the method parameter properly, but if I keep them the same the value
> of username will always be null.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CXF-4473) PathParam null when @Path annotations are the same
[
https://issues.apache.org/jira/browse/CXF-4473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13434997#comment-13434997
]
Sergey Beryozkin commented on CXF-4473:
---
Tried the request-scoped bean, also works...
> PathParam null when @Path annotations are the same
> --
>
> Key: CXF-4473
> URL: https://issues.apache.org/jira/browse/CXF-4473
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
>Affects Versions: 2.5.4
> Environment: java version "1.6.0_24"
> OpenJDK Runtime Environment (IcedTea6 1.11.3) (6b24-1.11.3-1ubuntu0.12.04.1)
> OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode)
>Reporter: Chris Eineke
>
> For some reason, the JAX-RS runtime doesn't provide the value of a
> @GET-annotated method and @PathParam-annotated method parameter if another
> @PUT-annotated method with the same @ParamParam-annotated method parameter
> has the same @Path annotation:
> @GET @Path("/users/{username}/foo")
> public Foo getFoo(
> @PathParam("username") String username)
> @PUT @Path("/users/{username}/foo")
> public Foo setFoo(
> @PathParam("username") String username,
> Foo foo)
> The runtime correctly invokes the first method for a GET. If I change the
> last path segment of the first method to anything but "foo", the runtime will
> provide the method parameter properly, but if I keep them the same the value
> of username will always be null.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CXF-4473) PathParam null when @Path annotations are the same
[
https://issues.apache.org/jira/browse/CXF-4473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13435125#comment-13435125
]
Chris Eineke commented on CXF-4473:
---
Another @GET-annotated method with the same @Path and a @MatrixParam was
interfering with the lookup process.
> PathParam null when @Path annotations are the same
> --
>
> Key: CXF-4473
> URL: https://issues.apache.org/jira/browse/CXF-4473
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
>Affects Versions: 2.5.4
> Environment: java version "1.6.0_24"
> OpenJDK Runtime Environment (IcedTea6 1.11.3) (6b24-1.11.3-1ubuntu0.12.04.1)
> OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode)
>Reporter: Chris Eineke
>
> For some reason, the JAX-RS runtime doesn't provide the value of a
> @GET-annotated method and @PathParam-annotated method parameter if another
> @PUT-annotated method with the same @ParamParam-annotated method parameter
> has the same @Path annotation:
> @GET @Path("/users/{username}/foo")
> public Foo getFoo(
> @PathParam("username") String username)
> @PUT @Path("/users/{username}/foo")
> public Foo setFoo(
> @PathParam("username") String username,
> Foo foo)
> The runtime correctly invokes the first method for a GET. If I change the
> last path segment of the first method to anything but "foo", the runtime will
> provide the method parameter properly, but if I keep them the same the value
> of username will always be null.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CXF-4473) PathParam null when @Path annotations are the same
[
https://issues.apache.org/jira/browse/CXF-4473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13435185#comment-13435185
]
Sergey Beryozkin commented on CXF-4473:
---
Can you clarify further ? How did the signature for that another GET method
look like ? What that extra method had to do with PUT method not capturing
'username' ?
> PathParam null when @Path annotations are the same
> --
>
> Key: CXF-4473
> URL: https://issues.apache.org/jira/browse/CXF-4473
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
>Affects Versions: 2.5.4
> Environment: java version "1.6.0_24"
> OpenJDK Runtime Environment (IcedTea6 1.11.3) (6b24-1.11.3-1ubuntu0.12.04.1)
> OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode)
>Reporter: Chris Eineke
>
> For some reason, the JAX-RS runtime doesn't provide the value of a
> @GET-annotated method and @PathParam-annotated method parameter if another
> @PUT-annotated method with the same @ParamParam-annotated method parameter
> has the same @Path annotation:
> @GET @Path("/users/{username}/foo")
> public Foo getFoo(
> @PathParam("username") String username)
> @PUT @Path("/users/{username}/foo")
> public Foo setFoo(
> @PathParam("username") String username,
> Foo foo)
> The runtime correctly invokes the first method for a GET. If I change the
> last path segment of the first method to anything but "foo", the runtime will
> provide the method parameter properly, but if I keep them the same the value
> of username will always be null.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CXF-4473) PathParam null when @Path annotations are the same
[
https://issues.apache.org/jira/browse/CXF-4473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13435201#comment-13435201
]
Chris Eineke commented on CXF-4473:
---
I should explain my goals here.
a) Provide "/users/{username}/foo" resource to GET and POST toward a single
user entity.
@GET @Path("/users/{username}/foo")
public Foo getFooOfUser(@PathParam("username") @DefaultValue("") String
username)
@POST @Path("/users/{username}/foo")
public Foo postFooOfUser(@PathParam("username") @DefaultValue("") String
username)
b) Provide "/users/{usernames}/foo" resource to GET and POST towards multiple
user entities.
@GET @Path("/users/{username}/foo")
public List getFooOfUsers(@MatrixParam("username") List
usernames)
@POST @Path("/users/{username}/foo")
public List postFooOfUsers(@MatrixParam("username") List
usernames, List foos)
This is of course wrong, because matrix params aren't path params.
> PathParam null when @Path annotations are the same
> --
>
> Key: CXF-4473
> URL: https://issues.apache.org/jira/browse/CXF-4473
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
>Affects Versions: 2.5.4
> Environment: java version "1.6.0_24"
> OpenJDK Runtime Environment (IcedTea6 1.11.3) (6b24-1.11.3-1ubuntu0.12.04.1)
> OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode)
>Reporter: Chris Eineke
>
> For some reason, the JAX-RS runtime doesn't provide the value of a
> @GET-annotated method and @PathParam-annotated method parameter if another
> @PUT-annotated method with the same @ParamParam-annotated method parameter
> has the same @Path annotation:
> @GET @Path("/users/{username}/foo")
> public Foo getFoo(
> @PathParam("username") String username)
> @PUT @Path("/users/{username}/foo")
> public Foo setFoo(
> @PathParam("username") String username,
> Foo foo)
> The runtime correctly invokes the first method for a GET. If I change the
> last path segment of the first method to anything but "foo", the runtime will
> provide the method parameter properly, but if I keep them the same the value
> of username will always be null.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CXF-4473) PathParam null when @Path annotations are the same
[
https://issues.apache.org/jira/browse/CXF-4473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13435274#comment-13435274
]
Sergey Beryozkin commented on CXF-4473:
---
{code:java}
@GET @Path("/users/{username}/foo")
public List getFooOfUsers(@MatrixParam("username") List usernames)
{code}
is technically a valid syntax, as you may have
'/users/bob;username=mary;username=fred' and the above should capture 'mary' &
'fred, with 'bob' captured but not explicitly requested in the code;
But I can see where the confusion may be coming from.
I guess I'm going to close it as Not A Problem ?
> PathParam null when @Path annotations are the same
> --
>
> Key: CXF-4473
> URL: https://issues.apache.org/jira/browse/CXF-4473
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
>Affects Versions: 2.5.4
> Environment: java version "1.6.0_24"
> OpenJDK Runtime Environment (IcedTea6 1.11.3) (6b24-1.11.3-1ubuntu0.12.04.1)
> OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode)
>Reporter: Chris Eineke
>
> For some reason, the JAX-RS runtime doesn't provide the value of a
> @GET-annotated method and @PathParam-annotated method parameter if another
> @PUT-annotated method with the same @ParamParam-annotated method parameter
> has the same @Path annotation:
> @GET @Path("/users/{username}/foo")
> public Foo getFoo(
> @PathParam("username") String username)
> @PUT @Path("/users/{username}/foo")
> public Foo setFoo(
> @PathParam("username") String username,
> Foo foo)
> The runtime correctly invokes the first method for a GET. If I change the
> last path segment of the first method to anything but "foo", the runtime will
> provide the method parameter properly, but if I keep them the same the value
> of username will always be null.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CXF-4446) CXF JAX-RS can't handle spaces in the URL when used with Apache Tomcat
[ https://issues.apache.org/jira/browse/CXF-4446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13435282#comment-13435282 ] Sergey Beryozkin commented on CXF-4446: --- Do you have any update on this issue you were seeing ? I'm keen to close it as Can Not Reproduce > CXF JAX-RS can't handle spaces in the URL when used with Apache Tomcat > -- > > Key: CXF-4446 > URL: https://issues.apache.org/jira/browse/CXF-4446 > Project: CXF > Issue Type: Bug > Components: JAX-RS >Affects Versions: 2.6.1 > Environment: Scientific Linux 6.1, Apache Tomcat 7.0.22, Java 1.6.0_29 >Reporter: Andrew Rowley > > Putting an encoded space (%20) in the url gets the following exception: > java.lang.IllegalArgumentException > java.net.URI.create(URI.java:842) > > org.apache.cxf.transport.servlet.BaseUrlHelper.getBaseURL(BaseUrlHelper.java:49) > > org.apache.cxf.transport.servlet.ServletController.getBaseURL(ServletController.java:73) > > org.apache.cxf.transport.servlet.ServletController.updateDestination(ServletController.java:82) > > org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:153) > > org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:129) > > org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:187) > > org.apache.cxf.transport.servlet.AbstractHTTPServlet.doGet(AbstractHTTPServlet.java:115) > javax.servlet.http.HttpServlet.service(HttpServlet.java:621) > > org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:166) > > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:368) > > org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:109) > > org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:83) > > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:380) > > org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:97) > > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:380) > > org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:100) > > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:380) > > uk.ac.nactem.kalliope.security.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:85) > > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:380) > > org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter.doFilter(SecurityContextHolderAwareRequestFilter.java:54) > > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:380) > > org.springframework.security.web.savedrequest.RequestCacheAwareFilter.doFilter(RequestCacheAwareFilter.java:35) > > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:380) > > org.springframework.security.web.context.SecurityContextPersistenceFilter.doFilter(SecurityContextPersistenceFilter.java:79) > > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:380) > > org.springframework.security.web.FilterChainProxy.doFilter(FilterChainProxy.java:169) > > org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:237) > > org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:167) > root cause > java.net.URISyntaxException: Illegal character in path at index 50: > http://www.nactem.ac.uk/ArgoDemoTest/services/test test > java.net.URI$Parser.fail(URI.java:2809) > java.net.URI$Parser.checkChars(URI.java:2982) > java.net.URI$Parser.parseHierarchical(URI.java:3066) > java.net.URI$Parser.parse(URI.java:3014) > java.net.URI.(URI.java:578) > java.net.URI.create(URI.java:840) > > org.apache.cxf.transport.servlet.BaseUrlHelper.getBaseURL(BaseUrlHelper.java:49) > > org.apache.cxf.transport.servlet.ServletController.getBaseURL(ServletController.java:73) > > org.apache.cxf.transport.servlet.ServletController.updateDestination(ServletController.java:82) > > org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:153) > > org
[jira] [Commented] (CXF-4473) PathParam null when @Path annotations are the same
[
https://issues.apache.org/jira/browse/CXF-4473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13435319#comment-13435319
]
Chris Eineke commented on CXF-4473:
---
Not a problem.
> PathParam null when @Path annotations are the same
> --
>
> Key: CXF-4473
> URL: https://issues.apache.org/jira/browse/CXF-4473
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
>Affects Versions: 2.5.4
> Environment: java version "1.6.0_24"
> OpenJDK Runtime Environment (IcedTea6 1.11.3) (6b24-1.11.3-1ubuntu0.12.04.1)
> OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode)
>Reporter: Chris Eineke
>
> For some reason, the JAX-RS runtime doesn't provide the value of a
> @GET-annotated method and @PathParam-annotated method parameter if another
> @PUT-annotated method with the same @ParamParam-annotated method parameter
> has the same @Path annotation:
> @GET @Path("/users/{username}/foo")
> public Foo getFoo(
> @PathParam("username") String username)
> @PUT @Path("/users/{username}/foo")
> public Foo setFoo(
> @PathParam("username") String username,
> Foo foo)
> The runtime correctly invokes the first method for a GET. If I change the
> last path segment of the first method to anything but "foo", the runtime will
> provide the method parameter properly, but if I keep them the same the value
> of username will always be null.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CXF-4476) Content-Disposition header may be incorrectly set in MTOM under windows
Aki Yoshida created CXF-4476: Summary: Content-Disposition header may be incorrectly set in MTOM under windows Key: CXF-4476 URL: https://issues.apache.org/jira/browse/CXF-4476 Project: CXF Issue Type: Bug Components: Core Affects Versions: 2.6.1 Environment: windows Reporter: Aki Yoshida Assignee: Aki Yoshida Priority: Minor This problem can be seen in the following test case when it is executed under windows. Failed tests: testMtomWithFileName(org.apache.cxf.systest.mtom.ClientMtomXopTest): can't get file name expected: but was: The problem is the way how the file name is extracted in AttachmentUtils.createMtomAttachmentFromDH. Concretely, this method extracts the part of the data handler's URL string after the last File.separator, where this string is given as the standard URL syntax which does not contains the windows' File.separator. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
