You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Andy McCright (Jira)" <ji...@apache.org> on 2020/09/22 21:28:00 UTC

[jira] [Created] (CXF-8347) URL/URI Handling issues

Andy McCright created CXF-8347:
----------------------------------

             Summary: URL/URI Handling issues
                 Key: CXF-8347
                 URL: https://issues.apache.org/jira/browse/CXF-8347
             Project: CXF
          Issue Type: Bug
    Affects Versions: 3.4.0
            Reporter: Andy McCright


There have been a few cases where IBM has made changes to the Open Liberty "fork" of CXF to resolve issues with URLs/URIs, including:
* EndpointInfo can occasionally be set to null in multithreaded environments causing NPEs on subsequent lookups.
* URITemplate needs better handling of parameter resolution.
* URITemplate is expensive and many times the same URI is re-generated - a cache should speed up performance and CPU utilization.
* FormUtils.isFormPostRequest() does not take into account charset parameters or sub-types, etc.
* HttpUtils base URI processing can be optimized for better performance
* Lifecycle methods (PostConstruct/PreDestroy) need to be able to be invoked even if they are package/protected.
* Async Resource methods are not required to be void return types
* Need to be able to handle CDI constructor injection into resources/providers
* A few doPrivs needed for environments running with a Java 2 security manager
* Need a way to "wrap" the runnable used by the workqueue in HTTPConduit - Open Liberty basically needs a way to transfer contexts (like Java EE metadata, security contexts, etc.)
* 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)