[jira] [Created] (CXF-8344) org.apache.cxf.jaxrs.utils.AnnotationUtils#getNameBindings does not use ClassUnwrapper
Romain Manni-Bucau created CXF-8344: --- Summary: org.apache.cxf.jaxrs.utils.AnnotationUtils#getNameBindings does not use ClassUnwrapper Key: CXF-8344 URL: https://issues.apache.org/jira/browse/CXF-8344 Project: CXF Issue Type: Bug Reporter: Romain Manni-Bucau ... which leads to miss the whole annotated model with some proxies -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CXF-8345) Improve Performance by avoiding MessageImpl resizing
Andy McCright created CXF-8345: -- Summary: Improve Performance by avoiding MessageImpl resizing Key: CXF-8345 URL: https://issues.apache.org/jira/browse/CXF-8345 Project: CXF Issue Type: Improvement Affects Versions: 3.4.0 Reporter: Andy McCright Assignee: Andy McCright The IBM performance team noticed that a significant amount of time is spent resizing the underlying data store of MessageImpl when using CXF in Open Liberty, and that a lot of time/resources can be saved by specifying an initial size of 16 and a load factor of 1. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CXF-8346) JAX-RS TCK: Resolve test cases where empty entities are checked
Andy McCright created CXF-8346: -- Summary: JAX-RS TCK: Resolve test cases where empty entities are checked Key: CXF-8346 URL: https://issues.apache.org/jira/browse/CXF-8346 Project: CXF Issue Type: Bug Components: JAX-RS Affects Versions: 3.4.0 Reporter: Andy McCright Assignee: Andy McCright In Open Liberty's "fork" of CXF, we made some changes to better handle cases where an entity is empty. IIRC (and we made this change a while back, so my memory is a little fuzzy), the TCK checks things where the entity stream is null and when the entity stream is non-null but empty - in both cases the "hasEntity" method should return false. I believe that the changes that we made affected multiple similar test cases to this one: com/sun/ts/tests/jaxrs/ee/rs/container/requestcontext/JAXRSClient.java#hasEntityWhenNoEntityTest_from_standalone: -- This message was sent by Atlassian Jira (v8.3.4#803005)
[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)
[jira] [Commented] (CXF-8347) URL/URI Handling issues
[ https://issues.apache.org/jira/browse/CXF-8347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17200396#comment-17200396 ] Andy McCright commented on CXF-8347: also TCK test com/sun/ts/tests/jaxrs/servlet3/rs/applicationpath/JAXRSClient.java#applicationPathAnnotationEncodedTest_from_standalone failed without the UriEncoder class change. > 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 >Priority: Major > > 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)
