[jira] [Commented] (CXF-6452) Spring Autowired annotataion on HttpServletRequest can not get latest request
[ https://issues.apache.org/jira/browse/CXF-6452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14585233#comment-14585233 ] Sergey Beryozkin commented on CXF-6452: --- It is Won't Fix as far as JAX-RS is concerned because it won't be JAX-RS. > Spring Autowired annotataion on HttpServletRequest can not get latest request > - > > Key: CXF-6452 > URL: https://issues.apache.org/jira/browse/CXF-6452 > Project: CXF > Issue Type: Bug >Affects Versions: 3.1.0 > Environment: Windows, Java HotSpot(TM) 64-Bit Server VM (build > 24.60-b09, mixed mode) >Reporter: xfcjscn > Labels: autowired, request, spring > > Autowired HttpServletRequest updated to wrapped version in > FrameworkServlet.processRequest() via > RequestContextHolder.setRequestAttributes(), so that further processes which > rely on Autowired HttpServletRequest can get wrapped version not original > version. > While CXF spring integration don't update it, and it will get original > request not wrapped version. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CXF-6462) Local Transport between 2 war applications in same JVM
Akash Borkar created CXF-6462: - Summary: Local Transport between 2 war applications in same JVM Key: CXF-6462 URL: https://issues.apache.org/jira/browse/CXF-6462 Project: CXF Issue Type: Wish Components: Samples Reporter: Akash Borkar -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CXF-6461) Smarter deactivation of SpringAopClassHelper
[ https://issues.apache.org/jira/browse/CXF-6461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14585262#comment-14585262 ] Sergey Beryozkin commented on CXF-6461: --- The property that supports using Spring is set to true by default, and it can only be disabled by the system flag; having the property itself set to true is not sufficient for Spring to be used as SpringAopClassHelper will fail to initialize if no Spring is available on the classpath. Does it not work in your case ? > Smarter deactivation of SpringAopClassHelper > > > Key: CXF-6461 > URL: https://issues.apache.org/jira/browse/CXF-6461 > Project: CXF > Issue Type: Improvement > Components: Tooling >Affects Versions: 3.0.5 >Reporter: John D. Ament > > Improve how ClassHelper activates Spring or default implementation. > https://github.com/apache/cxf/blob/3.0.x-fixes/core/src/main/java/org/apache/cxf/common/util/ClassHelper.java#L40 > Instead of relying solely on the JVM flag, also check for spring on the > classpath. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CXF-6461) Smarter deactivation of SpringAopClassHelper
[ https://issues.apache.org/jira/browse/CXF-6461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14585303#comment-14585303 ] John D. Ament commented on CXF-6461: Actually, I spent a lot of time trying to figure out why this wasn't working for me. Then it dawned on me to check spring versions. So, yes, what I put in the ticket is incorrect. Spring is properly checked on the classpath, however there are some compatibility issues. My app does package spring, but not by my own choice (it comes from one of our internal libraries that brings in all of spring, even though most of its not used). For deployment reasons, the whole thing ends up there. In CXF 2.7, you're depending on Spring 3.0.7 which happens to be what I'm pointing to. CXF 3 is using Spring 3.2, which is not compatible. The check on load is checking for classes, however there are method differences between the two. It looks like in my app currently, I am using Spring's AOP support. So, would it be worth extending the spring check to also check for method existence? > Smarter deactivation of SpringAopClassHelper > > > Key: CXF-6461 > URL: https://issues.apache.org/jira/browse/CXF-6461 > Project: CXF > Issue Type: Improvement > Components: Tooling >Affects Versions: 3.0.5 >Reporter: John D. Ament > > Improve how ClassHelper activates Spring or default implementation. > https://github.com/apache/cxf/blob/3.0.x-fixes/core/src/main/java/org/apache/cxf/common/util/ClassHelper.java#L40 > Instead of relying solely on the JVM flag, also check for spring on the > classpath. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
