[jira] [Resolved] (CXF-8117) Make dependencies optional

[ https://issues.apache.org/jira/browse/CXF-8117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-8117. --- Resolution: Information Provided > Make dependencies optional > -- > >

[jira] [Resolved] (CXF-8118) CXF LoggingInInterceptor: CachedWriter leaks

[ https://issues.apache.org/jira/browse/CXF-8118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-8118. --- Fix Version/s: 3.3.4 3.2.11 3.4.0 Resolution: Fixed > CXF

[jira] [Assigned] (CXF-8118) CXF LoggingInInterceptor: CachedWriter leaks

[ https://issues.apache.org/jira/browse/CXF-8118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-8118: - Assignee: Freeman Fang > CXF LoggingInInterceptor: CachedWriter leaks >

[jira] [Commented] (CXF-8117) Make dependencies optional

[ https://issues.apache.org/jira/browse/CXF-8117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931676#comment-16931676 ] Freeman Fang commented on CXF-8117: --- The main idea here isn't necessary or not for most users, it's about

[jira] [Commented] (CXF-8117) Make dependencies optional

[ https://issues.apache.org/jira/browse/CXF-8117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931511#comment-16931511 ] Freeman Fang commented on CXF-8117: --- So far I don't think we should mark this as optional. You can only

[jira] [Assigned] (CXF-8117) Make dependencies optional

[ https://issues.apache.org/jira/browse/CXF-8117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-8117: - Assignee: Freeman Fang > Make dependencies optional > -- > >

[jira] [Commented] (CXF-8112) Default WebApplicationExceptionMapper is preferred over custom one but Documentation states opposite

[ https://issues.apache.org/jira/browse/CXF-8112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16929512#comment-16929512 ] Freeman Fang commented on CXF-8112: --- [~dan...@peger.de], thanks, revised accordingly. > Default

[jira] [Assigned] (CXF-8096) Adding LoggingFeature causes blocking read

[ https://issues.apache.org/jira/browse/CXF-8096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-8096: - Assignee: Freeman Fang > Adding LoggingFeature causes blocking read >

[jira] [Resolved] (CXF-8096) Adding LoggingFeature causes blocking read

[ https://issues.apache.org/jira/browse/CXF-8096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-8096. --- Resolution: Information Provided > Adding LoggingFeature causes blocking read >

[jira] [Issue Comment Deleted] (CXF-6568) Default WebApplicationExceptionMapper should be optionally made less specific

[ https://issues.apache.org/jira/browse/CXF-6568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated CXF-6568: -- Comment: was deleted (was: Thanks for reporting this issue Document updated, should be published in a

[jira] [Commented] (CXF-8112) Default WebApplicationExceptionMapper is preferred over custom one but Documentation states opposite

[ https://issues.apache.org/jira/browse/CXF-8112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16929288#comment-16929288 ] Freeman Fang commented on CXF-8112: --- Thanks for reporting this issue Document updated, should be

[jira] [Commented] (CXF-6568) Default WebApplicationExceptionMapper should be optionally made less specific

[ https://issues.apache.org/jira/browse/CXF-6568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16929286#comment-16929286 ] Freeman Fang commented on CXF-6568: --- Thanks for reporting this issue Document updated, should be

[jira] [Resolved] (CXF-8112) Default WebApplicationExceptionMapper is preferred over custom one but Documentation states opposite

[ https://issues.apache.org/jira/browse/CXF-8112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-8112. --- Resolution: Fixed > Default WebApplicationExceptionMapper is preferred over custom one but >

[jira] [Commented] (CXF-8113) SocketTimeoutException when remote server closes connection after payload has been delivered

[ https://issues.apache.org/jira/browse/CXF-8113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16928041#comment-16928041 ] Freeman Fang commented on CXF-8113: --- Yes, first glance it's a regression from httpcore-nio side, using

[jira] [Assigned] (CXF-8112) Default WebApplicationExceptionMapper is preferred over custom one but Documentation states opposite

[ https://issues.apache.org/jira/browse/CXF-8112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-8112: - Assignee: Freeman Fang > Default WebApplicationExceptionMapper is preferred over custom one but

[jira] [Comment Edited] (CXF-8096) Adding LoggingFeature causes blocking read

[ https://issues.apache.org/jira/browse/CXF-8096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16927108#comment-16927108 ] Freeman Fang edited comment on CXF-8096 at 9/10/19 11:17 PM: - Hi [~kkurucz], I

[jira] [Commented] (CXF-8096) Adding LoggingFeature causes blocking read

[ https://issues.apache.org/jira/browse/CXF-8096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16927108#comment-16927108 ] Freeman Fang commented on CXF-8096: --- Hi [~kkurucz], I took a close look at the problem you described,

[jira] [Resolved] (CXF-8105) introduce a property for JMS transport client to decide reset JMS connection or not when client timeout

[ https://issues.apache.org/jira/browse/CXF-8105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-8105. --- Fix Version/s: 3.3.4 3.2.11 3.4.0 Resolution: Fixed >

[jira] [Commented] (CXF-8105) introduce a property for JMS transport client to decide reset JMS connection or not when client timeout

[ https://issues.apache.org/jira/browse/CXF-8105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16922464#comment-16922464 ] Freeman Fang commented on CXF-8105: --- [~coheigea], yes, will do > introduce a property for JMS transport

[jira] [Assigned] (CXF-8105) introduce a property for JMS transport client to decide reset JMS connection or not when client timeout

[ https://issues.apache.org/jira/browse/CXF-8105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-8105: - Assignee: Freeman Fang > introduce a property for JMS transport client to decide reset JMS

[jira] [Created] (CXF-8105) introduce a property for JMS transport client to decide reset JMS connection or not when client timeout

Freeman Fang created CXF-8105: - Summary: introduce a property for JMS transport client to decide reset JMS connection or not when client timeout Key: CXF-8105 URL: https://issues.apache.org/jira/browse/CXF-8105

[jira] [Commented] (CXF-7910) Change JAX-WS javax to jakarta artifact dependencies

[ https://issues.apache.org/jira/browse/CXF-7910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16907698#comment-16907698 ] Freeman Fang commented on CXF-7910: --- Hi Guys, The last time I tried, there's still some issues in OSGi

[jira] [Resolved] (CXF-8090) Warnings when using cxf-codegen-plugin

[ https://issues.apache.org/jira/browse/CXF-8090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-8090. --- Resolution: Fixed Fix Version/s: 3.3.4 > Warnings when using cxf-codegen-plugin >

[jira] [Commented] (CXF-8090) Warnings when using cxf-codegen-plugin

[ https://issues.apache.org/jira/browse/CXF-8090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16903992#comment-16903992 ] Freeman Fang commented on CXF-8090: --- This is caused by new properties name introduced since velocity 2.1

[jira] [Assigned] (CXF-8090) Warnings when using cxf-codegen-plugin

[ https://issues.apache.org/jira/browse/CXF-8090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-8090: - Assignee: Freeman Fang > Warnings when using cxf-codegen-plugin >

[jira] [Resolved] (CXF-8088) ensure jaxrs endpoint can work correctly when using a shared bus exposed from another bundle

[ https://issues.apache.org/jira/browse/CXF-8088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-8088. --- Resolution: Fixed Fix Version/s: 3.2.10 3.3.3 > ensure jaxrs endpoint can

[jira] [Created] (CXF-8088) ensure jaxrs endpoint can work correctly when using a shared bus exposed from another bundle

Freeman Fang created CXF-8088: - Summary: ensure jaxrs endpoint can work correctly when using a shared bus exposed from another bundle Key: CXF-8088 URL: https://issues.apache.org/jira/browse/CXF-8088

[jira] [Assigned] (CXF-8088) ensure jaxrs endpoint can work correctly when using a shared bus exposed from another bundle

[ https://issues.apache.org/jira/browse/CXF-8088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-8088: - Assignee: Freeman Fang > ensure jaxrs endpoint can work correctly when using a shared bus exposed

[jira] [Commented] (CXF-8082) [Apache cxf 3.1.4] ConcurrentModificationException

[ https://issues.apache.org/jira/browse/CXF-8082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16899094#comment-16899094 ] Freeman Fang commented on CXF-8082: --- Hi [~Samadou], As I pointed the doc here

[jira] [Resolved] (CXF-8082) [Apache cxf 3.1.4] ConcurrentModificationException

[ https://issues.apache.org/jira/browse/CXF-8082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-8082. --- Resolution: Information Provided > [Apache cxf 3.1.4] ConcurrentModificationException >

[jira] [Resolved] (CXF-8084) Wrong adress for endpoints is generated with autoRewriteSoapAddressForAllServices

[ https://issues.apache.org/jira/browse/CXF-8084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-8084. --- Resolution: Information Provided > Wrong adress for endpoints is generated with >

[jira] [Commented] (CXF-8084) Wrong adress for endpoints is generated with autoRewriteSoapAddressForAllServices

[ https://issues.apache.org/jira/browse/CXF-8084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16899068#comment-16899068 ] Freeman Fang commented on CXF-8084: --- Hi [~morse] FYI, the "http.base.path" is calculate from the

[jira] [Resolved] (CXF-8083) ensure java2swagger-plugin|java2ws-plugin m2e compatible

[ https://issues.apache.org/jira/browse/CXF-8083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-8083. --- Resolution: Fixed Fix Version/s: 3.2.10 3.3.3 > ensure

[jira] [Commented] (CXF-8084) Wrong adress for endpoints is generated with autoRewriteSoapAddressForAllServices

[ https://issues.apache.org/jira/browse/CXF-8084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16897303#comment-16897303 ] Freeman Fang commented on CXF-8084: --- Hi [~morse], I don't think we really need the "services" between if

[jira] [Created] (CXF-8083) ensure java2swagger-plugin|java2ws-plugin m2e compatible

Freeman Fang created CXF-8083: - Summary: ensure java2swagger-plugin|java2ws-plugin m2e compatible Key: CXF-8083 URL: https://issues.apache.org/jira/browse/CXF-8083 Project: CXF Issue Type:

[jira] [Assigned] (CXF-8083) ensure java2swagger-plugin|java2ws-plugin m2e compatible

[ https://issues.apache.org/jira/browse/CXF-8083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-8083: - Assignee: Freeman Fang > ensure java2swagger-plugin|java2ws-plugin m2e compatible >

[jira] [Resolved] (CXF-8081) should cache reactor OutputStream

[ https://issues.apache.org/jira/browse/CXF-8081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-8081. --- Resolution: Fixed Fix Version/s: 3.2.10 3.3.3 > should cache reactor

[jira] [Commented] (CXF-8082) [Apache cxf 3.1.4] ConcurrentModificationException

[ https://issues.apache.org/jira/browse/CXF-8082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16897051#comment-16897051 ] Freeman Fang commented on CXF-8082: --- Hi [~Samadou], Could you please elaborate the scenario how you run

[jira] [Updated] (CXF-8081) should cache reactor OutputStream

[ https://issues.apache.org/jira/browse/CXF-8081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated CXF-8081: -- Summary: should cache reactor OutputStream (was: org.apache.cxf.systest.jaxrs.reactor.FluxReactorTest

[jira] [Updated] (CXF-8081) org.apache.cxf.systest.jaxrs.reactor.FluxReactorTest failed for all JDKs

[ https://issues.apache.org/jira/browse/CXF-8081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated CXF-8081: -- Summary: org.apache.cxf.systest.jaxrs.reactor.FluxReactorTest failed for all JDKs (was: The

[jira] [Updated] (CXF-8081) The OutputStream in StreamingResponseProvider should be cached

[ https://issues.apache.org/jira/browse/CXF-8081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated CXF-8081: -- Summary: The OutputStream in StreamingResponseProvider should be cached (was:

[jira] [Assigned] (CXF-8081) org.apache.cxf.systest.jaxrs.reactor.FluxReactorTest failed for all JDKs

[ https://issues.apache.org/jira/browse/CXF-8081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-8081: - Assignee: Freeman Fang > org.apache.cxf.systest.jaxrs.reactor.FluxReactorTest failed for all JDKs

[jira] [Commented] (CXF-8081) org.apache.cxf.systest.jaxrs.reactor.FluxReactorTest failed for all JDKs

[ https://issues.apache.org/jira/browse/CXF-8081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16896467#comment-16896467 ] Freeman Fang commented on CXF-8081: --- The change for CXF-8032 exposes this issue but it's not the root

[jira] [Commented] (CXF-8081) org.apache.cxf.systest.jaxrs.reactor.FluxReactorTest failed for all JDKs

[ https://issues.apache.org/jira/browse/CXF-8081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16896354#comment-16896354 ] Freeman Fang commented on CXF-8081: --- Yes, the change in CXF-8032 caused this >

[jira] [Commented] (CXF-8081) org.apache.cxf.systest.jaxrs.reactor.FluxReactorTest failed for all JDKs

[ https://issues.apache.org/jira/browse/CXF-8081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16896239#comment-16896239 ] Freeman Fang commented on CXF-8081: --- https://builds.apache.org/job/CXF-Trunk-JDK18/4504/

[jira] [Created] (CXF-8081) org.apache.cxf.systest.jaxrs.reactor.FluxReactorTest failed for all JDKs

Freeman Fang created CXF-8081: - Summary: org.apache.cxf.systest.jaxrs.reactor.FluxReactorTest failed for all JDKs Key: CXF-8081 URL: https://issues.apache.org/jira/browse/CXF-8081 Project: CXF

[jira] [Resolved] (CXF-8072) Loggers logs request twice in case of Fault (CXF-7518 again)

[ https://issues.apache.org/jira/browse/CXF-8072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-8072. --- Resolution: Fixed Fix Version/s: 3.2.10 3.3.3 > Loggers logs request twice

[jira] [Assigned] (CXF-8072) Loggers logs request twice in case of Fault (CXF-7518 again)

[ https://issues.apache.org/jira/browse/CXF-8072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-8072: - Assignee: Freeman Fang > Loggers logs request twice in case of Fault (CXF-7518 again) >

[jira] [Resolved] (CXF-8064) OpenApiFeature(OpenAPI V3) should be able to work with camel-cxfrs endpoint

[ https://issues.apache.org/jira/browse/CXF-8064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-8064. --- Resolution: Fixed Fix Version/s: 3.2.10 3.3.3 > OpenApiFeature(OpenAPI V3)

[jira] [Commented] (CXF-8069) CXF does not allow to change default configuration of Jetty

[ https://issues.apache.org/jira/browse/CXF-8069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16877910#comment-16877910 ] Freeman Fang commented on CXF-8069: --- Hi [~naina.pati...@infobeans.com], FYI, the http-jetty transport in

[jira] [Resolved] (CXF-8062) MessageContext.HTTP_RESPONSE_CODE cannot be obtained if response code is not 4xx

[ https://issues.apache.org/jira/browse/CXF-8062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-8062. --- Resolution: Fixed Fix Version/s: 3.2.10 3.3.3 >

[jira] [Updated] (CXF-8062) MessageContext.HTTP_RESPONSE_CODE cannot be obtained if response code is not 4xx

[ https://issues.apache.org/jira/browse/CXF-8062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated CXF-8062: -- Summary: MessageContext.HTTP_RESPONSE_CODE cannot be obtained if response code is not 4xx (was:

[jira] [Commented] (CXF-8062) MessageContext.HTTP_RESPONSE_CODE cannot be obtained if response code is not 200

[ https://issues.apache.org/jira/browse/CXF-8062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16877244#comment-16877244 ] Freeman Fang commented on CXF-8062: --- OK, for 4xx return code(just like in your testcase), CXF client side

[jira] [Commented] (CXF-8062) MessageContext.HTTP_RESPONSE_CODE cannot be obtained if response code is not 200

[ https://issues.apache.org/jira/browse/CXF-8062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16877116#comment-16877116 ] Freeman Fang commented on CXF-8062: --- Thanks [~tomasedata] for the reproducer, I will take a close look.

[jira] [Commented] (CXF-8067) java 11(reproduced on openjdk/oracle/coretto/adopt): java.lang.VerifyError: Falling off the end of the code

[ https://issues.apache.org/jira/browse/CXF-8067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16877107#comment-16877107 ] Freeman Fang commented on CXF-8067: --- Hi [~rbelinsky], A reproducer would be a good way(sometimes even

[jira] [Created] (CXF-8064) OpenApiFeature(OpenAPI V3) should be able to work with camel-cxfrs endpoint

Freeman Fang created CXF-8064: - Summary: OpenApiFeature(OpenAPI V3) should be able to work with camel-cxfrs endpoint Key: CXF-8064 URL: https://issues.apache.org/jira/browse/CXF-8064 Project: CXF

[jira] [Assigned] (CXF-8064) OpenApiFeature(OpenAPI V3) should be able to work with camel-cxfrs endpoint

[ https://issues.apache.org/jira/browse/CXF-8064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-8064: - Assignee: Freeman Fang > OpenApiFeature(OpenAPI V3) should be able to work with camel-cxfrs

[jira] [Commented] (CXF-8062) MessageContext.HTTP_RESPONSE_CODE cannot be obtained if response code is not 200

[ https://issues.apache.org/jira/browse/CXF-8062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16875050#comment-16875050 ] Freeman Fang commented on CXF-8062: --- Hi [~tomasedata], I just committed to demonstrate that

[jira] [Assigned] (CXF-8062) MessageContext.HTTP_RESPONSE_CODE cannot be obtained if response code is not 200

[ https://issues.apache.org/jira/browse/CXF-8062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-8062: - Assignee: Freeman Fang > MessageContext.HTTP_RESPONSE_CODE cannot be obtained if response code is

[jira] [Updated] (CXF-8057) upgrade to use stax2-api and woodstox-core latest version

[ https://issues.apache.org/jira/browse/CXF-8057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated CXF-8057: -- Fix Version/s: (was: 3.3.3) 3.4.0 > upgrade to use stax2-api and woodstox-core

[jira] [Reopened] (CXF-8057) upgrade to use stax2-api and woodstox-core latest version

[ https://issues.apache.org/jira/browse/CXF-8057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reopened CXF-8057: --- will revert and defer this change to 3.4 to align with Camel 3.0 > upgrade to use stax2-api and

[jira] [Commented] (CXF-8057) upgrade to use stax2-api and woodstox-core latest version

[ https://issues.apache.org/jira/browse/CXF-8057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16867623#comment-16867623 ] Freeman Fang commented on CXF-8057: --- Hi Colm, OK, let's defer to 3.4. Camel 3.0 will upgrade stax2-api

[jira] [Created] (CXF-8058) OSGi tests broken for both JDK8 and JDK11

Freeman Fang created CXF-8058: - Summary: OSGi tests broken for both JDK8 and JDK11 Key: CXF-8058 URL: https://issues.apache.org/jira/browse/CXF-8058 Project: CXF Issue Type: Test

[jira] [Resolved] (CXF-8057) upgrade to use stax2-api and woodstox-core latest version

[ https://issues.apache.org/jira/browse/CXF-8057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-8057. --- Resolution: Fixed Fix Version/s: 3.3.3 > upgrade to use stax2-api and woodstox-core latest

[jira] [Updated] (CXF-8057) upgrade to use stax2-api and woodstox-core latest version

[ https://issues.apache.org/jira/browse/CXF-8057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated CXF-8057: -- Description: since stax2-api 3.1.4 was released 5 years ago. And also need t latest woodstox-core to

[jira] [Created] (CXF-8057) upgrade to use stax2-api and woodstox-core latest version

Freeman Fang created CXF-8057: - Summary: upgrade to use stax2-api and woodstox-core latest version Key: CXF-8057 URL: https://issues.apache.org/jira/browse/CXF-8057 Project: CXF Issue Type: Task

[jira] [Assigned] (CXF-8057) upgrade to use stax2-api and woodstox-core latest version

[ https://issues.apache.org/jira/browse/CXF-8057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-8057: - Assignee: Freeman Fang > upgrade to use stax2-api and woodstox-core latest version >

[jira] [Resolved] (CXFXJC-35) Maven-Plugin xsdtojava Task throws NullPointerException if project.build.sourceEncoding is not set

[ https://issues.apache.org/jira/browse/CXFXJC-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXFXJC-35. Resolution: Fixed Fix Version/s: 3.3.1 > Maven-Plugin xsdtojava Task throws

[jira] [Assigned] (CXFXJC-35) Maven-Plugin xsdtojava Task throws NullPointerException if project.build.sourceEncoding is not set

[ https://issues.apache.org/jira/browse/CXFXJC-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXFXJC-35: -- Assignee: Freeman Fang > Maven-Plugin xsdtojava Task throws NullPointerException if >

[jira] [Comment Edited] (CXF-7112) AsyncHTTPConduit ignore the ReceiveTimeout when use Async JAXWS api

[ https://issues.apache.org/jira/browse/CXF-7112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16863362#comment-16863362 ] Freeman Fang edited comment on CXF-7112 at 6/13/19 8:53 PM: Hi [~Aritz], No

[jira] [Resolved] (CXF-8055) AsyncHTTPConduit should also consider jaxws spec timeout properties

[ https://issues.apache.org/jira/browse/CXF-8055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-8055. --- Resolution: Fixed Fix Version/s: 3.2.10 3.3.3 > AsyncHTTPConduit should also

[jira] [Commented] (CXF-7112) AsyncHTTPConduit ignore the ReceiveTimeout when use Async JAXWS api

[ https://issues.apache.org/jira/browse/CXF-7112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16863395#comment-16863395 ] Freeman Fang commented on CXF-7112: --- created CXF-8055 to track it > AsyncHTTPConduit ignore the

[jira] [Assigned] (CXF-8055) AsyncHTTPConduit should also consider jaxws spec timeout properties

[ https://issues.apache.org/jira/browse/CXF-8055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-8055: - Assignee: Freeman Fang > AsyncHTTPConduit should also consider jaxws spec timeout properties >

[jira] [Created] (CXF-8055) AsyncHTTPConduit should also consider jaxws spec timeout properties

Freeman Fang created CXF-8055: - Summary: AsyncHTTPConduit should also consider jaxws spec timeout properties Key: CXF-8055 URL: https://issues.apache.org/jira/browse/CXF-8055 Project: CXF Issue

[jira] [Commented] (CXF-7112) AsyncHTTPConduit ignore the ReceiveTimeout when use Async JAXWS api

[ https://issues.apache.org/jira/browse/CXF-7112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16863362#comment-16863362 ] Freeman Fang commented on CXF-7112: --- Hi [~Aritz], No worries, I saw this problem, it's because you use

[jira] [Commented] (CXF-7112) AsyncHTTPConduit ignore the ReceiveTimeout when use Async JAXWS api

[ https://issues.apache.org/jira/browse/CXF-7112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16863293#comment-16863293 ] Freeman Fang commented on CXF-7112: --- Hi [~Aritz], For the test example, I think you can take a look at

[jira] [Commented] (CXF-7112) AsyncHTTPConduit ignore the ReceiveTimeout when use Async JAXWS api

[ https://issues.apache.org/jira/browse/CXF-7112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16863162#comment-16863162 ] Freeman Fang commented on CXF-7112: --- Hi [~Aritz], Which CXF version you are using? Could you please

[jira] [Resolved] (CXF-8052) Cannot set JAXB schema compiler options

[ https://issues.apache.org/jira/browse/CXF-8052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-8052. --- Resolution: Fixed Fix Version/s: 3.2.10 3.3.3 > Cannot set JAXB schema

[jira] [Commented] (CXF-8052) Cannot set JAXB schema compiler options

[ https://issues.apache.org/jira/browse/CXF-8052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16861096#comment-16861096 ] Freeman Fang commented on CXF-8052: --- patch applied on behalf of Ranjit Vadakkan with thanks! > Cannot

[jira] [Commented] (CXFXJC-23) jaxb dependancy warnings when compiling against java9

[ https://issues.apache.org/jira/browse/CXFXJC-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16861031#comment-16861031 ] Freeman Fang commented on CXFXJC-23: with CXFXJC-31, we've already upgraded to JAXB 2.3.2, so can

[jira] [Resolved] (CXFXJC-23) jaxb dependancy warnings when compiling against java9

[ https://issues.apache.org/jira/browse/CXFXJC-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXFXJC-23. Resolution: Fixed > jaxb dependancy warnings when compiling against java9 >

[jira] [Assigned] (CXF-8052) Cannot set JAXB schema compiler options

[ https://issues.apache.org/jira/browse/CXF-8052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-8052: - Assignee: Freeman Fang > Cannot set JAXB schema compiler options >

[jira] [Resolved] (CXF-8049) org.apache.cxf.common.util.Compiler fails to compile if a classpath entry contains spaces

[ https://issues.apache.org/jira/browse/CXF-8049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-8049. --- Resolution: Fixed Fix Version/s: 3.2.10 3.3.3 patch applied on behalf of

[jira] [Commented] (CXFXJC-34) Code generation breaks on boolean restricted to 0 or 1

[ https://issues.apache.org/jira/browse/CXFXJC-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16849741#comment-16849741 ] Freeman Fang commented on CXFXJC-34: I believe this is the same root cause as CXF-7998 And actually

[jira] [Assigned] (CXFXJC-34) Code generation breaks on boolean restricted to 0 or 1

[ https://issues.apache.org/jira/browse/CXFXJC-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXFXJC-34: -- Assignee: Freeman Fang > Code generation breaks on boolean restricted to 0 or 1 >

[jira] [Assigned] (CXF-8049) org.apache.cxf.common.util.Compiler fails to compile if a classpath entry contains spaces

[ https://issues.apache.org/jira/browse/CXF-8049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-8049: - Assignee: Freeman Fang > org.apache.cxf.common.util.Compiler fails to compile if a classpath

[jira] [Commented] (CXF-8049) org.apache.cxf.common.util.Compiler fails to compile if a classpath entry contains spaces

[ https://issues.apache.org/jira/browse/CXF-8049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16849192#comment-16849192 ] Freeman Fang commented on CXF-8049: --- Hi [~rvadakkan], Thanks for reporting this issue! Are you keen to

[jira] [Commented] (CXF-8041) Error resolving relative XSD Schema on Tomcat

[ https://issues.apache.org/jira/browse/CXF-8041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16846918#comment-16846918 ] Freeman Fang commented on CXF-8041: --- Hi [~netmikey], Thanks for the feedback! Please see latest commit

[jira] [Resolved] (CXF-8041) Error resolving relative XSD Schema on Tomcat

[ https://issues.apache.org/jira/browse/CXF-8041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-8041. --- Resolution: Fixed Fix Version/s: 3.2.10 3.3.3 > Error resolving relative XSD

[jira] [Assigned] (CXF-8041) Error resolving relative XSD Schema on Tomcat

[ https://issues.apache.org/jira/browse/CXF-8041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-8041: - Assignee: Freeman Fang > Error resolving relative XSD Schema on Tomcat >

[jira] [Resolved] (CXF-8045) Disable HTTP TRACE method on CXF http-undertow transport

[ https://issues.apache.org/jira/browse/CXF-8045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-8045. --- Resolution: Fixed Fix Version/s: 3.2.10 3.3.3 > Disable HTTP TRACE method on

[jira] [Created] (CXF-8045) Disable HTTP TRACE method on CXF http-undertow transport

Freeman Fang created CXF-8045: - Summary: Disable HTTP TRACE method on CXF http-undertow transport Key: CXF-8045 URL: https://issues.apache.org/jira/browse/CXF-8045 Project: CXF Issue Type:

[jira] [Assigned] (CXF-8045) Disable HTTP TRACE method on CXF http-undertow transport

[ https://issues.apache.org/jira/browse/CXF-8045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-8045: - Assignee: Freeman Fang > Disable HTTP TRACE method on CXF http-undertow transport >

[jira] [Assigned] (CXF-8013) Can't tell CXF to use a custom certstore for SSL certificate check

[ https://issues.apache.org/jira/browse/CXF-8013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-8013: - Assignee: Colm O hEigeartaigh (was: Freeman Fang) > Can't tell CXF to use a custom certstore for

[jira] [Commented] (CXF-8013) Can't tell CXF to use a custom certstore for SSL certificate check

[ https://issues.apache.org/jira/browse/CXF-8013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16821009#comment-16821009 ] Freeman Fang commented on CXF-8013: --- Ah, thanks [~coheigea]! > Can't tell CXF to use a custom certstore

[jira] [Commented] (CXF-8013) Can't tell CXF to use a custom certstore for SSL certificate check

[ https://issues.apache.org/jira/browse/CXF-8013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16814968#comment-16814968 ] Freeman Fang commented on CXF-8013: --- Hi [~michelsaumon] Could you please append a runnable testcase?

[jira] [Commented] (CXF-7953) make corba binding working with JDK11

[ https://issues.apache.org/jira/browse/CXF-7953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16814044#comment-16814044 ] Freeman Fang commented on CXF-7953: --- Hi [~zhfeng], We don't have to revert when maven with

[jira] [Commented] (CXF-7953) make corba binding working with JDK11

[ https://issues.apache.org/jira/browse/CXF-7953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16812979#comment-16812979 ] Freeman Fang commented on CXF-7953: --- Hi [~dkulp], Yup, your commit works perfectly. Now we don't need to

[jira] [Commented] (CXF-7953) make corba binding working with JDK11

[ https://issues.apache.org/jira/browse/CXF-7953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16812856#comment-16812856 ] Freeman Fang commented on CXF-7953: --- [~dkulp] Ah, good idea. I will try that way. Cheers Freeman > make

[jira] [Assigned] (CXF-8013) Can't tell CXF to use a custom certstore for SSL certificate check

[ https://issues.apache.org/jira/browse/CXF-8013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-8013: - Assignee: Freeman Fang > Can't tell CXF to use a custom certstore for SSL certificate check >

  1   2   3   4   5   6   7   8   9   10   >