[jira] [Resolved] (CXF-7741) ensure we can build CXF with JDK11

[ https://issues.apache.org/jira/browse/CXF-7741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-7741. --- Resolution: Fixed > ensure we can build CXF with JDK11 > -- > >

[jira] [Commented] (CXF-7741) ensure we can build CXF with JDK11

[ https://issues.apache.org/jira/browse/CXF-7741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16542702#comment-16542702 ] Freeman Fang commented on CXF-7741: --- [~reta] So far I still use jaxws 2.2/jaxb 2.2/activation 1.1. To

[jira] [Commented] (CXF-7741) ensure we can build CXF with JDK11

[ https://issues.apache.org/jira/browse/CXF-7741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16542697#comment-16542697 ] Freeman Fang commented on CXF-7741: --- I just commit the change, so now we can build CXF master with JAVA8,

[jira] [Resolved] (CXFXJC-27) ensure xjc plugin can work with java11

[ https://issues.apache.org/jira/browse/CXFXJC-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXFXJC-27. Resolution: Fixed Fix Version/s: 3.2.3 > ensure xjc plugin can work with java11 >

[jira] [Assigned] (CXFXJC-27) ensure xjc plugin can work with java11

[ https://issues.apache.org/jira/browse/CXFXJC-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXFXJC-27: -- Assignee: Freeman Fang > ensure xjc plugin can work with java11 >

[jira] [Created] (CXFXJC-27) ensure xjc plugin can work with java11

Freeman Fang created CXFXJC-27: -- Summary: ensure xjc plugin can work with java11 Key: CXFXJC-27 URL: https://issues.apache.org/jira/browse/CXFXJC-27 Project: CXF XJC Utils Issue Type:

[jira] [Commented] (CXF-7741) ensure we can build CXF with JDK11

[ https://issues.apache.org/jira/browse/CXF-7741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16541025#comment-16541025 ] Freeman Fang commented on CXF-7741: --- Thanks [~reta]! > ensure we can build CXF with JDK11 >

[jira] [Comment Edited] (CXF-7741) ensure we can build CXF with JDK11

[ https://issues.apache.org/jira/browse/CXF-7741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16540998#comment-16540998 ] Freeman Fang edited comment on CXF-7741 at 7/12/18 1:42 AM: Yes, in theory it

[jira] [Commented] (CXF-7741) ensure we can build CXF with JDK11

[ https://issues.apache.org/jira/browse/CXF-7741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16540998#comment-16540998 ] Freeman Fang commented on CXF-7741: --- Yes, in theory it should work with java9, 10, 11, but I do need more

[jira] [Commented] (CXF-7774) JMS Reply Queue handles leaking on IBM MQ.

[ https://issues.apache.org/jira/browse/CXF-7774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1654#comment-1654 ] Freeman Fang commented on CXF-7774: --- So the fix for CXF-7768 also works in your case?   And next CXF

[jira] [Commented] (CXF-7781) cannot parse jdk version 11 early access

[ https://issues.apache.org/jira/browse/CXF-7781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16532781#comment-16532781 ] Freeman Fang commented on CXF-7781: --- The patch attached for CXF-7741 can get this resolved.   I will

[jira] [Assigned] (CXF-7781) cannot parse jdk version 11 early access

[ https://issues.apache.org/jira/browse/CXF-7781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-7781: - Assignee: Freeman Fang > cannot parse jdk version 11 early access >

[jira] [Comment Edited] (CXF-7774) JMS Reply Queue handles leaking on IBM MQ.

[ https://issues.apache.org/jira/browse/CXF-7774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16531077#comment-16531077 ] Freeman Fang edited comment on CXF-7774 at 7/3/18 9:22 AM: --- Yes, at least it's

[jira] [Commented] (CXF-7774) JMS Reply Queue handles leaking on IBM MQ.

[ https://issues.apache.org/jira/browse/CXF-7774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16531077#comment-16531077 ] Freeman Fang commented on CXF-7774: --- Yes, at least it's the Activemq way, thought not sure IBM

[jira] [Commented] (CXF-7774) JMS Reply Queue handles leaking on IBM MQ.

[ https://issues.apache.org/jira/browse/CXF-7774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16530656#comment-16530656 ] Freeman Fang commented on CXF-7774: --- The reason because there is still a  consumer registered on this

[jira] [Resolved] (CXF-7767) Support 100-Continue in Undertow transport

[ https://issues.apache.org/jira/browse/CXF-7767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-7767. --- Resolution: Fixed > Support 100-Continue in Undertow transport >

[jira] [Commented] (CXF-7767) Support 100-Continue in Undertow transport

[ https://issues.apache.org/jira/browse/CXF-7767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16529577#comment-16529577 ] Freeman Fang commented on CXF-7767: --- wrapped HttpContinueReadHandler around PathHandler > Support

[jira] [Resolved] (CXF-7767) Support 100-Continue in Undertow transport

[ https://issues.apache.org/jira/browse/CXF-7767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-7767. --- Resolution: Fixed Fix Version/s: 3.2.6 > Support 100-Continue in Undertow transport >

[jira] [Commented] (CXF-7725) ensure all tests on master can pass with java10

[ https://issues.apache.org/jira/browse/CXF-7725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16525696#comment-16525696 ] Freeman Fang commented on CXF-7725: --- Hi [~coheigea],   We still need PAX-EXAM 4.12 out.   Freeman >

[jira] [Resolved] (CXF-7768) ensure we close all temp queue/topic before we close a JMS connection

[ https://issues.apache.org/jira/browse/CXF-7768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-7768. --- Resolution: Fixed Fix Version/s: 3.2.6 > ensure we close all temp queue/topic before we close a

[jira] [Assigned] (CXF-7767) Support 100-Continue in Undertow transport

[ https://issues.apache.org/jira/browse/CXF-7767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-7767: - Assignee: Freeman Fang > Support 100-Continue in Undertow transport >

[jira] [Assigned] (CXF-7768) ensure we close all temp queue/topic before we close a JMS connection

[ https://issues.apache.org/jira/browse/CXF-7768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-7768: - Assignee: Freeman Fang > ensure we close all temp queue/topic before we close a JMS connection >

[jira] [Created] (CXF-7768) ensure we close all temp queue/topic before we close a JMS connection

Freeman Fang created CXF-7768: - Summary: ensure we close all temp queue/topic before we close a JMS connection Key: CXF-7768 URL: https://issues.apache.org/jira/browse/CXF-7768 Project: CXF

[jira] [Commented] (CXF-7761) Soap Header contents getting mixed up

[ https://issues.apache.org/jira/browse/CXF-7761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16519899#comment-16519899 ] Freeman Fang commented on CXF-7761: --- Hi [~glever],   Could you please attach a testcase? Somehow I

[jira] [Resolved] (CXF-7764) java2swagger doesn't use correct filenames when attaching output files to maven repository

[ https://issues.apache.org/jira/browse/CXF-7764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-7764. --- Resolution: Not A Problem > java2swagger doesn't use correct filenames when attaching output files to

[jira] [Commented] (CXF-7764) java2swagger doesn't use correct filenames when attaching output files to maven repository

[ https://issues.apache.org/jira/browse/CXF-7764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16518771#comment-16518771 ] Freeman Fang commented on CXF-7764: --- Hi [~rune.vikestad], This is by design, you can add *payments*

[jira] [Assigned] (CXF-7764) java2swagger doesn't use correct filenames when attaching output files to maven repository

[ https://issues.apache.org/jira/browse/CXF-7764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-7764: - Assignee: Freeman Fang > java2swagger doesn't use correct filenames when attaching output files

[jira] [Resolved] (CXF-7756) JAASLoginInterceptor with server continuation enabled will cause the interceptor before ServiceInvokerInterceptor get invoked twice

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

[jira] [Created] (CXF-7756) JAASLoginInterceptor with server continuation enabled will cause the interceptor before ServiceInvokerInterceptor get invoked twice

Freeman Fang created CXF-7756: - Summary: JAASLoginInterceptor with server continuation enabled will cause the interceptor before ServiceInvokerInterceptor get invoked twice Key: CXF-7756 URL:

[jira] [Assigned] (CXF-7756) JAASLoginInterceptor with server continuation enabled will cause the interceptor before ServiceInvokerInterceptor get invoked twice

[ https://issues.apache.org/jira/browse/CXF-7756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-7756: - Assignee: Freeman Fang > JAASLoginInterceptor with server continuation enabled will cause the >

[jira] [Commented] (CXF-7741) ensure we can build CXF with JDK11

[ https://issues.apache.org/jira/browse/CXF-7741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16506578#comment-16506578 ] Freeman Fang commented on CXF-7741: --- yep, let's target it for 3.3 > ensure we can build CXF with JDK11 >

[jira] [Comment Edited] (CXF-7741) ensure we can build CXF with JDK11

[ https://issues.apache.org/jira/browse/CXF-7741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16505790#comment-16505790 ] Freeman Fang edited comment on CXF-7741 at 6/8/18 7:26 AM: --- A quick update of

[jira] [Commented] (CXF-7741) ensure we can build CXF with JDK11

[ https://issues.apache.org/jira/browse/CXF-7741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16505790#comment-16505790 ] Freeman Fang commented on CXF-7741: --- A quick update of this issue. Just appended a patch. Since JDK11,

[jira] [Updated] (CXF-7741) ensure we can build CXF with JDK11

[ https://issues.apache.org/jira/browse/CXF-7741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated CXF-7741: -- Attachment: CXF-7741.patch > ensure we can build CXF with JDK11 > -- > >

[jira] [Resolved] (CXF-7750) cxf parent pom should have dependencyManagement entries for cxf artifacts

[ https://issues.apache.org/jira/browse/CXF-7750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-7750. --- Resolution: Fixed Fix Version/s: 3.2.5 > cxf parent pom should have dependencyManagement

[jira] [Commented] (CXF-7750) cxf parent pom should have dependencyManagement entries for cxf artifacts

[ https://issues.apache.org/jira/browse/CXF-7750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16499810#comment-16499810 ] Freeman Fang commented on CXF-7750: --- patch applied on behalf of Tom Cunningham with thanks > cxf parent

[jira] [Assigned] (CXF-7750) cxf parent pom should have dependencyManagement entries for cxf artifacts

[ https://issues.apache.org/jira/browse/CXF-7750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-7750: - Assignee: Freeman Fang > cxf parent pom should have dependencyManagement entries for cxf

[jira] [Assigned] (CXF-7741) ensure we can build CXF with JDK11

[ https://issues.apache.org/jira/browse/CXF-7741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-7741: - Assignee: Freeman Fang > ensure we can build CXF with JDK11 > -- >

[jira] [Created] (CXF-7741) ensure we can build CXF with JDK11

Freeman Fang created CXF-7741: - Summary: ensure we can build CXF with JDK11 Key: CXF-7741 URL: https://issues.apache.org/jira/browse/CXF-7741 Project: CXF Issue Type: Task Reporter:

[jira] [Commented] (CXF-7725) ensure all tests on master can pass with java10

[ https://issues.apache.org/jira/browse/CXF-7725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16480520#comment-16480520 ] Freeman Fang commented on CXF-7725: --- [~shadow] yep, good catch. Will revise accordingly.   Thanks! >

[jira] [Updated] (CXF-7725) ensure all tests on master can pass with java10

[ https://issues.apache.org/jira/browse/CXF-7725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated CXF-7725: -- Attachment: CXF-7725.patch > ensure all tests on master can pass with java10 >

[jira] [Commented] (CXF-7725) ensure all tests on master can pass with java10

[ https://issues.apache.org/jira/browse/CXF-7725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16480291#comment-16480291 ] Freeman Fang commented on CXF-7725: --- With CXF-7725.patch I just attached, all tests passed with java10.

[jira] [Resolved] (CXF-7740) add NPE guard for SAAJStreamWriter

[ https://issues.apache.org/jira/browse/CXF-7740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-7740. --- Resolution: Fixed Fix Version/s: 3.2.5 3.1.16 > add NPE guard for

[jira] [Assigned] (CXF-7740) add NPE guard for SAAJStreamWriter

[ https://issues.apache.org/jira/browse/CXF-7740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-7740: - Assignee: Freeman Fang > add NPE guard for SAAJStreamWriter > -- >

[jira] [Created] (CXF-7740) add NPE guard for SAAJStreamWriter

Freeman Fang created CXF-7740: - Summary: add NPE guard for SAAJStreamWriter Key: CXF-7740 URL: https://issues.apache.org/jira/browse/CXF-7740 Project: CXF Issue Type: Bug Reporter:

[jira] [Comment Edited] (CXF-7725) ensure all tests on master can pass with java10

[ https://issues.apache.org/jira/browse/CXF-7725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471489#comment-16471489 ] Freeman Fang edited comment on CXF-7725 at 5/11/18 4:48 AM: With the necessary

[jira] [Commented] (CXF-7725) ensure all tests on master can pass with java10

[ https://issues.apache.org/jira/browse/CXF-7725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471489#comment-16471489 ] Freeman Fang commented on CXF-7725: --- With the necessary change for KARAF-5707, all OSGi related system

[jira] [Resolved] (CXF-7727) apache cxf 3.x with jetty 9.2 issues

[ https://issues.apache.org/jira/browse/CXF-7727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-7727. --- Resolution: Duplicate > apache cxf 3.x with jetty 9.2 issues > > >

[jira] [Commented] (CXF-7727) apache cxf 3.x with jetty 9.2 issues

[ https://issues.apache.org/jira/browse/CXF-7727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16451465#comment-16451465 ] Freeman Fang commented on CXF-7727: --- And here is an example how to configure HttpConfiguration with jetty

[jira] [Commented] (CXF-7727) apache cxf 3.x with jetty 9.2 issues

[ https://issues.apache.org/jira/browse/CXF-7727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16451461#comment-16451461 ] Freeman Fang commented on CXF-7727: --- I think this is already fixed by CXF-7179 and in CXF 3.1.10

[jira] [Assigned] (CXF-7727) apache cxf 3.x with jetty 9.2 issues

[ https://issues.apache.org/jira/browse/CXF-7727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-7727: - Assignee: Freeman Fang > apache cxf 3.x with jetty 9.2 issues >

[jira] [Commented] (CXF-7725) ensure all tests on master can pass with java10

[ https://issues.apache.org/jira/browse/CXF-7725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16449508#comment-16449508 ] Freeman Fang commented on CXF-7725: --- Thanks Colm! Yes, that's pretty much what I found so far. For b)

[jira] [Assigned] (CXF-7725) ensure all tests on master can pass with java10

[ https://issues.apache.org/jira/browse/CXF-7725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-7725: - Assignee: Freeman Fang > ensure all tests on master can pass with java10 >

[jira] [Created] (CXF-7725) ensure all tests on master can pass with java10

Freeman Fang created CXF-7725: - Summary: ensure all tests on master can pass with java10 Key: CXF-7725 URL: https://issues.apache.org/jira/browse/CXF-7725 Project: CXF Issue Type: Task

[jira] [Resolved] (CXF-7715) EmptySOAPBodyTest fails on master with Java 9

[ https://issues.apache.org/jira/browse/CXF-7715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-7715. --- Resolution: Fixed > EmptySOAPBodyTest fails on master with Java 9 >

[jira] [Assigned] (CXF-7715) EmptySOAPBodyTest fails on master with Java 9

[ https://issues.apache.org/jira/browse/CXF-7715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-7715: - Assignee: Freeman Fang > EmptySOAPBodyTest fails on master with Java 9 >

[jira] [Resolved] (CXFXJC-25) cxf-xjc-plugin can't load xjc plugin extensions which is already on the classpath with jax-xjc 2.3.0

[ https://issues.apache.org/jira/browse/CXFXJC-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXFXJC-25. Resolution: Fixed Fix Version/s: 3.2.2 > cxf-xjc-plugin can't load xjc plugin extensions

[jira] [Comment Edited] (CXFXJC-25) cxf-xjc-plugin can't load xjc plugin extensions which is already on the classpath with jax-xjc 2.3.0

[ https://issues.apache.org/jira/browse/CXFXJC-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442053#comment-16442053 ] Freeman Fang edited comment on CXFXJC-25 at 4/18/18 7:35 AM: - This is caused by

[jira] [Commented] (CXFXJC-25) cxf-xjc-plugin can't load xjc plugin extensions which is already on the classpath with jax-xjc 2.3.0

[ https://issues.apache.org/jira/browse/CXFXJC-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442053#comment-16442053 ] Freeman Fang commented on CXFXJC-25: This is caused by that the getAllPlugins() method in 

[jira] [Created] (CXFXJC-25) cxf-xjc-plugin can't load xjc plugin extensions which is already on the classpath with jax-xjc 2.3.0

Freeman Fang created CXFXJC-25: -- Summary: cxf-xjc-plugin can't load xjc plugin extensions which is already on the classpath with jax-xjc 2.3.0 Key: CXFXJC-25 URL: https://issues.apache.org/jira/browse/CXFXJC-25

[jira] [Assigned] (CXFXJC-25) cxf-xjc-plugin can't load xjc plugin extensions which is already on the classpath with jax-xjc 2.3.0

[ https://issues.apache.org/jira/browse/CXFXJC-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXFXJC-25: -- Assignee: Freeman Fang > cxf-xjc-plugin can't load xjc plugin extensions which is already on

[jira] [Resolved] (CXFXJC-24) Cant compile against java10

[ https://issues.apache.org/jira/browse/CXFXJC-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXFXJC-24. Resolution: Fixed Fix Version/s: 3.2.2 > Cant compile against java10 >

[jira] [Commented] (CXFXJC-24) Cant compile against java10

[ https://issues.apache.org/jira/browse/CXFXJC-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16439096#comment-16439096 ] Freeman Fang commented on CXFXJC-24: I think commit[1] fixed this

[jira] [Issue Comment Deleted] (CXFXJC-24) Cant compile against java10

[ https://issues.apache.org/jira/browse/CXFXJC-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated CXFXJC-24: --- Comment: was deleted (was: I think [this|I think[ this commit

[jira] [Comment Edited] (CXFXJC-24) Cant compile against java10

[ https://issues.apache.org/jira/browse/CXFXJC-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16439090#comment-16439090 ] Freeman Fang edited comment on CXFXJC-24 at 4/16/18 8:04 AM: - I think [this|I

[jira] [Comment Edited] (CXFXJC-24) Cant compile against java10

[ https://issues.apache.org/jira/browse/CXFXJC-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16439090#comment-16439090 ] Freeman Fang edited comment on CXFXJC-24 at 4/16/18 8:04 AM: - I think[ this

[jira] [Commented] (CXFXJC-24) Cant compile against java10

[ https://issues.apache.org/jira/browse/CXFXJC-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16439090#comment-16439090 ] Freeman Fang commented on CXFXJC-24: I think[ this commit

[jira] [Assigned] (CXFXJC-24) Cant compile against java10

[ https://issues.apache.org/jira/browse/CXFXJC-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXFXJC-24: -- Assignee: Freeman Fang > Cant compile against java10 > --- > >

[jira] [Assigned] (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 reassigned CXFXJC-23: -- Assignee: Freeman Fang > jaxb dependancy warnings when compiling against java9 >

[jira] [Resolved] (CXF-7705) Use Java EL api and impl bundle from Servicemix for cxf-bean-validation feature

[ https://issues.apache.org/jira/browse/CXF-7705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-7705. --- Resolution: Fixed Fix Version/s: 3.2.5 3.1.16 > Use Java EL api and impl

[jira] [Assigned] (CXF-7705) Use Java EL api and impl bundle from Servicemix for cxf-bean-validation feature

[ https://issues.apache.org/jira/browse/CXF-7705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-7705: - Assignee: Freeman Fang > Use Java EL api and impl bundle from Servicemix for cxf-bean-validation

[jira] [Created] (CXF-7705) Use Java EL api and impl bundle from Servicemix for cxf-bean-validation feature

Freeman Fang created CXF-7705: - Summary: Use Java EL api and impl bundle from Servicemix for cxf-bean-validation feature Key: CXF-7705 URL: https://issues.apache.org/jira/browse/CXF-7705 Project: CXF

[jira] [Updated] (CXF-7705) Use Java EL api and impl bundle from Servicemix for cxf-bean-validation feature

[ https://issues.apache.org/jira/browse/CXF-7705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated CXF-7705: -- Component/s: OSGi > Use Java EL api and impl bundle from Servicemix for cxf-bean-validation > feature >

[jira] [Resolved] (CXF-6324) cxf-codegen-plugin|cxf-java2ws-plugin: classifier ignored when there are more then one wsdl with different classifier is involved

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

[jira] [Commented] (CXF-6324) cxf-codegen-plugin|cxf-java2ws-plugin: classifier ignored when there are more then one wsdl with different classifier is involved

[ https://issues.apache.org/jira/browse/CXF-6324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16431857#comment-16431857 ] Freeman Fang commented on CXF-6324: --- Both cxf-codegen-plugin and cxf-java2ws-plugin have problem when

[jira] [Updated] (CXF-6324) cxf-codegen-plugin|cxf-java2ws-plugin: classifier ignored when there are more then one wsdl with different classifier is involved

[ https://issues.apache.org/jira/browse/CXF-6324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated CXF-6324: -- Summary: cxf-codegen-plugin|cxf-java2ws-plugin: classifier ignored when there are more then one wsdl with

[jira] [Assigned] (CXF-6324) cxf-codegen-plugin: classifier ignored when there are more then one client project with the same parent

[ https://issues.apache.org/jira/browse/CXF-6324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-6324: - Assignee: Freeman Fang > cxf-codegen-plugin: classifier ignored when there are more then one

[jira] [Resolved] (CXF-7683) Codegen fails when using JDK10 with maven and cxf-plugin

[ https://issues.apache.org/jira/browse/CXF-7683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-7683. --- Resolution: Fixed Fix Version/s: 3.2.5 > Codegen fails when using JDK10 with maven and

[jira] [Assigned] (CXF-7690) codegen not java10 compat

[ https://issues.apache.org/jira/browse/CXF-7690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-7690: - Assignee: Freeman Fang > codegen not java10 compat > - > >

[jira] [Updated] (CXF-7689) ensure don't have content-type|content-length as jms message headers when use REST on JMS Transport

[ https://issues.apache.org/jira/browse/CXF-7689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated CXF-7689: -- Fix Version/s: 3.2.5 Component/s: Transports > ensure don't have content-type|content-length as jms

[jira] [Resolved] (CXF-7689) ensure don't have content-type|content-length as jms message headers when use REST on JMS Transport

[ https://issues.apache.org/jira/browse/CXF-7689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-7689. --- Resolution: Fixed > ensure don't have content-type|content-length as jms message headers when use >

[jira] [Assigned] (CXF-7689) ensure don't have content-type|content-length as jms message headers when use REST on JMS Transport

[ https://issues.apache.org/jira/browse/CXF-7689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-7689: - Assignee: Freeman Fang > ensure don't have content-type|content-length as jms message headers when

[jira] [Created] (CXF-7689) ensure don't have content-type|content-length as jms message headers when use REST on JMS Transport

Freeman Fang created CXF-7689: - Summary: ensure don't have content-type|content-length as jms message headers when use REST on JMS Transport Key: CXF-7689 URL: https://issues.apache.org/jira/browse/CXF-7689

[jira] [Assigned] (CXF-7683) Codegen fails when using JDK10 with maven and cxf-plugin

[ https://issues.apache.org/jira/browse/CXF-7683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-7683: - Assignee: Freeman Fang > Codegen fails when using JDK10 with maven and cxf-plugin >

[jira] [Resolved] (CXF-7669) Cxf encodes escape caracters twice in JDK9.0.5 and JDK8_161

[ https://issues.apache.org/jira/browse/CXF-7669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-7669. --- Resolution: Fixed Fix Version/s: NeedMoreInfo > Cxf encodes escape caracters twice in JDK9.0.5

[jira] [Resolved] (CXF-7675) Extra dot required when specifying base packages to scan in Java2Wadl Maven plugins

[ https://issues.apache.org/jira/browse/CXF-7675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-7675. --- Resolution: Fixed Fix Version/s: 3.2.3 > Extra dot required when specifying base packages to

[jira] [Assigned] (CXF-7675) Extra dot required when specifying base packages to scan in Java2Wadl Maven plugins

[ https://issues.apache.org/jira/browse/CXF-7675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-7675: - Assignee: Freeman Fang > Extra dot required when specifying base packages to scan in Java2Wadl

[jira] [Resolved] (CXF-7674) Java2Wadl maven plugin requires explicit element - even if base packages specified

[ https://issues.apache.org/jira/browse/CXF-7674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-7674. --- Resolution: Fixed Fix Version/s: 3.2.3 > Java2Wadl maven plugin requires explicit element -

[jira] [Updated] (CXF-7674) Java2Wadl maven plugin requires explicit element - even if base packages specified

[ https://issues.apache.org/jira/browse/CXF-7674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated CXF-7674: -- Issue Type: Improvement (was: Bug) > Java2Wadl maven plugin requires explicit element - even > if base

[jira] [Assigned] (CXF-7674) Java2Wadl maven plugin requires explicit element - even if base packages specified

[ https://issues.apache.org/jira/browse/CXF-7674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-7674: - Assignee: Freeman Fang > Java2Wadl maven plugin requires explicit element - even > if base

[jira] [Commented] (CXF-7669) Cxf encodes escape caracters twice in JDK9.0.5 and JDK8_161

[ https://issues.apache.org/jira/browse/CXF-7669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16394876#comment-16394876 ] Freeman Fang commented on CXF-7669: --- Hi Mark, Please ensure the way you create JAXBDatabinding in your

[jira] [Resolved] (CXF-7671) should avoid reverse dns resolution in AsyncHTTPConduit for the proxy host address

[ https://issues.apache.org/jira/browse/CXF-7671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-7671. --- Resolution: Fixed Fix Version/s: 3.2.3 > should avoid reverse dns resolution in AsyncHTTPConduit

[jira] [Created] (CXF-7671) should avoid reverse dns resolution in AsyncHTTPConduit for the proxy host address

Freeman Fang created CXF-7671: - Summary: should avoid reverse dns resolution in AsyncHTTPConduit for the proxy host address Key: CXF-7671 URL: https://issues.apache.org/jira/browse/CXF-7671 Project: CXF

[jira] [Assigned] (CXF-7671) should avoid reverse dns resolution in AsyncHTTPConduit for the proxy host address

[ https://issues.apache.org/jira/browse/CXF-7671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-7671: - Assignee: Freeman Fang > should avoid reverse dns resolution in AsyncHTTPConduit for the proxy

[jira] [Commented] (CXF-7653) Null pointer in JaxwsResponseCallback

[ https://issues.apache.org/jira/browse/CXF-7653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16389022#comment-16389022 ] Freeman Fang commented on CXF-7653: --- Ah, great. Thanks Dan! > Null pointer in JaxwsResponseCallback >

[jira] [Commented] (CXF-7653) Null pointer in JaxwsResponseCallback

[ https://issues.apache.org/jira/browse/CXF-7653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16387750#comment-16387750 ] Freeman Fang commented on CXF-7653: --- Hi Dan, I think this fix may introduce a problem. I just committed

[jira] [Resolved] (CXF-7661) add isTimeout flag for Continutation so that we can easily know when the timeout happen outside CXF

[ https://issues.apache.org/jira/browse/CXF-7661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-7661. --- Resolution: Fixed Fix Version/s: 3.2.3 3.1.15 > add isTimeout flag for

[jira] [Assigned] (CXF-7661) add isTimeout flag for Continutation so that we can easily know when the timeout happen outside CXF

[ https://issues.apache.org/jira/browse/CXF-7661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-7661: - Assignee: Freeman Fang > add isTimeout flag for Continutation so that we can easily know when the

[jira] [Created] (CXF-7661) add isTimeout flag for Continutation so that we can easily know when the timeout happen outside CXF

Freeman Fang created CXF-7661: - Summary: add isTimeout flag for Continutation so that we can easily know when the timeout happen outside CXF Key: CXF-7661 URL: https://issues.apache.org/jira/browse/CXF-7661

[jira] [Resolved] (CXF-7655) java2swagger maven plugin not java9 compat

[ https://issues.apache.org/jira/browse/CXF-7655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-7655. --- Resolution: Fixed Fix Version/s: 3.2.3 added java9 profile for this module and added necessary

<    1   2   3   4   5   6   7   8   9   10   >