[jira] [Commented] (CXF-7996) Jakarta EE TCKs and compatibility

[Dennis Kieselhorst (Jira)]

[ 
https://issues.apache.org/jira/browse/CXF-7996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17552412#comment-17552412
 ] 

Dennis Kieselhorst commented on CXF-7996:
-

Great work, [~reta] - thanks a lot!

> Jakarta EE TCKs and compatibility
> -
>
> Key: CXF-7996
> URL: https://issues.apache.org/jira/browse/CXF-7996
> Project: CXF
>  Issue Type: Task
>Affects Versions: 3.4.7
>Reporter: Andriy Redko
>Assignee: Andriy Redko
>Priority: Major
> Fix For: 3.4.8
>
> Attachments: JTreport-11-January-2020.zip, 
> JTreport-26-December-2019.zip, JTwork- 26-December-2019.zip, 
> JTwork-11-January-2020.zip
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Mail thread: 
> [https://mail-archives.apache.org/mod_mbox/cxf-dev/201901.mbox/%3C6edd1da6-d651-]
>  e2a3-8092-59bdc7a54...@apache.org%3E
> Jakarta EE TCK: 
> [https://projects.eclipse.org/proposals/eclipse-jakarta-ee-tck]
>  Github Repo: [https://github.com/eclipse-ee4j/jakartaee-tck]
> Latest updates from [jakarta.ee-spec] TCK information, June 2019, the 
> excerpts: 
>  * {color:#00}We have summed up some information about how the TCK can be 
> built (or {color}
>  {color:#00}grabbed pre-built), configured, and run [1].{color}
>  * {color:#00}This is assumed to be run against a Glassfish with the 
> latest API {color}
>  {color:#00}integrated (replacing the original API in the 
> Glassfish).{color}
>  * {color:#00}We have created a recording of a presentation of the 
> Jenkins jobs that {color}
>  {color:#00}manage all that [2].{color}
>  * {color:#00}We have created 3 Jenkins files for pipeline job (as an 
> example for {color}
>  {color:#00}JSON-B TCK) to a) properly set the ts.jte configuration file, 
> b) to grab {color}
>  {color:#00}the API artifact built by a Jenkins build job and integrate 
> it to a {color}
>  {color:#00}Glassfish and c) to grab the pre-built TCK bundle from 
> Eclipse Download, {color}
>  {color:#00}grab the configured ts.jte file, grab the Glassfish with new 
> API {color}
>  {color:#00}integrated, and run the TCK [3].{color}
> {color:#00}For the complete information, please allow me to mention the 
> list of the {color}
>  {color:#00}TCK tasks needed to be done before the Jakarta EE release can 
> be {color}
>  {color:#00}finished [4].{color}
> {color:#00}The [5] is the example how to run Jakarta EE TCKs with 
> Tomcat.{color}
> {color:#00}The{color} [6] is the official list of the instructions.
> {color:#00}The{color} [7] is the list of the instructions from TomEE TCK .
>  
> [1] +[https://wiki.eclipse.org/TCK:Build_From_Jakarta_EE_TCK_Repo_And_Run]+
> {color:#00}[2] {color}+[https://youtu.be/nnD1KMvh0to]+
> {color:#00}[3] {color}
>  
> +[https://wiki.eclipse.org/TCK:Build_From_Jakarta_EE_TCK_Repo_And_Run#Jenkins_Pipelines]+
> {color:#00}[4] {color}+[https://github.com/orgs/eclipse-ee4j/projects/14]+
> [5] [https://cwiki.apache.org/confluence/display/TOMCAT/Jakarta+EE+TCKs]
> [6]
>  
> +[https://github.com/eclipse-ee4j/jakartaee-tck/wiki/Instructions-for-building-and-running-JakartaEE-TCK-bundle]+
> [7] [https://github.com/apache/tomee-tck]
>  
> *Summary:*
>  - job location: 
> [https://builds.apache.org/view/C/view/Apache%20CXF/job/CXF-JAXRS-TCK/60/console]
>  - the Jenkins pipeline and TCK configuration: 
> [https://github.com/apache/cxf/tree/master/tck|https://github.com/apache/cxf/tree/master/tck*]
>  - the builds are against JakartaEE TCK master branch
>     - the JAX-RS TCK is build first
>     - than all JAX-RS tests are run against this JAX-RS TCK 



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

[jira] [Commented] (CXF-8221) Upgrade Http Components Core and Client to 5.0

[Dennis Kieselhorst (Jira)]

[ 
https://issues.apache.org/jira/browse/CXF-8221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17428985#comment-17428985
 ] 

Dennis Kieselhorst commented on CXF-8221:
-

Sure, please go ahead. 

> Upgrade Http Components Core and Client to 5.0
> --
>
> Key: CXF-8221
> URL: https://issues.apache.org/jira/browse/CXF-8221
> Project: CXF
>  Issue Type: Improvement
>Reporter: Dennis Kieselhorst
>Priority: Major
> Fix For: 3.5.0
>
>
> Notable changes and features included in the 5.0 series are:
> * Support for the HTTP/2 protocol and conformance to requirements and
> recommendations of the latest HTTP/2 protocol specification documents
> (RFC 7540, RFC 7541.)
>   Supported features:
> ** HPACK header compression
> ** Stream multiplexing (client and server)
> ** Flow control
> ** Response push
> ** Message trailers
> ** Expect-continue handshake
> ** Connection validation (ping)
> ** Application-layer protocol negotiation (ALPN)
> ** TLS 1.2 security features
> * Improved conformance to requirements and recommendations of the
> latest HTTP/1.1 protocol specification documents (RFC 7230, RFC 7231)
> * New connection pool implementation with lax connection limit
> guarantees and better performance under higher concurrency due to
> absence of a global pool lock.
> * Support for Reactive Streams API [http://www.reactive-streams.org/]
> * Package name space changed to 'org.apache.hc.client5'.
> * Maven group id changed to 'org.apache.httpcomponents.client5'.
> HttpClient 5.0 releases can be co-located with earlier major versions
> on the same classpath due to the change in package names and Maven
> module coordinates.
> Download - 
> Release notes - <
> https://www.apache.org/dist/httpcomponents/httpclient/RELEASE_NOTES-5.0.x.txt



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

[jira] [Commented] (CXF-6349) Introduce HTTP/2 Transport

[Dennis Kieselhorst (Jira)]

[ 
https://issues.apache.org/jira/browse/CXF-6349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17240004#comment-17240004
 ] 

Dennis Kieselhorst commented on CXF-6349:
-

Link to the spec discussion: 
https://github.com/eclipse-ee4j/jaxrs-api/issues/923

> Introduce HTTP/2 Transport 
> ---
>
> Key: CXF-6349
> URL: https://issues.apache.org/jira/browse/CXF-6349
> Project: CXF
>  Issue Type: New Feature
>  Components: Transports
>Reporter: Sergey Beryozkin
>Assignee: Andriy Redko
>Priority: Major
>
> https://http2.github.io/
> Can be complementary to what Aki has done with WebSockets. 



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

[jira] [Resolved] (CXF-8301) Upgrade to Spring Boot 2.3.x

[Dennis Kieselhorst (Jira)]

 [ 
https://issues.apache.org/jira/browse/CXF-8301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Kieselhorst resolved CXF-8301.
-
Fix Version/s: (was: 3.5.0)
   3.4.0
   Resolution: Fixed

upgrade as discussed on dev list

> Upgrade to Spring Boot 2.3.x
> 
>
> Key: CXF-8301
> URL: https://issues.apache.org/jira/browse/CXF-8301
> Project: CXF
>  Issue Type: Task
>Reporter: Andriy Redko
>Assignee: Dennis Kieselhorst
>Priority: Major
> Fix For: 3.4.0
>
>




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

[jira] [Assigned] (CXF-8301) Upgrade to Spring Boot 2.3.x

[Dennis Kieselhorst (Jira)]

 [ 
https://issues.apache.org/jira/browse/CXF-8301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Kieselhorst reassigned CXF-8301:
---

Assignee: Dennis Kieselhorst  (was: Andriy Redko)

> Upgrade to Spring Boot 2.3.x
> 
>
> Key: CXF-8301
> URL: https://issues.apache.org/jira/browse/CXF-8301
> Project: CXF
>  Issue Type: Task
>Reporter: Andriy Redko
>Assignee: Dennis Kieselhorst
>Priority: Major
> Fix For: 3.5.0
>
>




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

[jira] [Commented] (CXF-8301) Upgrade to Spring Boot 2.3.x

[Dennis Kieselhorst (Jira)]

[ 
https://issues.apache.org/jira/browse/CXF-8301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17162505#comment-17162505
 ] 

Dennis Kieselhorst commented on CXF-8301:
-

Just wondering why don't we upgrade it for CXF 3.4.0?

Looking at 
https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-2.3-Release-Notes#upgrading-from-spring-boot-22
 there is nothing conflicting or am I missing something?

> Upgrade to Spring Boot 2.3.x
> 
>
> Key: CXF-8301
> URL: https://issues.apache.org/jira/browse/CXF-8301
> Project: CXF
>  Issue Type: Task
>Reporter: Andriy Redko
>Assignee: Andriy Redko
>Priority: Major
> Fix For: 3.5.0
>
>




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

[jira] [Commented] (CXF-8302) Support JAX-RS 3.0, snapshots already available

[Dennis Kieselhorst (Jira)]

[ 
https://issues.apache.org/jira/browse/CXF-8302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17144208#comment-17144208
 ] 

Dennis Kieselhorst commented on CXF-8302:
-

I've changed the title as the JAX-RS community is now targeting 3.0.

> Support JAX-RS 3.0, snapshots already available
> ---
>
> Key: CXF-8302
> URL: https://issues.apache.org/jira/browse/CXF-8302
> Project: CXF
>  Issue Type: Task
>Reporter: Andriy Redko
>Assignee: Andriy Redko
>Priority: Major
> Fix For: 3.5.0
>
>
> https://headcrashing.wordpress.com/2019/06/25/jax-rs-2-2-nightly-builds-available/



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

[jira] [Updated] (CXF-8302) Support JAX-RS 3.0, snapshots already available

[Dennis Kieselhorst (Jira)]

 [ 
https://issues.apache.org/jira/browse/CXF-8302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Kieselhorst updated CXF-8302:

Summary: Support JAX-RS 3.0, snapshots already available  (was: Support 
JAX-RS 2.2, snapshots already available)

> Support JAX-RS 3.0, snapshots already available
> ---
>
> Key: CXF-8302
> URL: https://issues.apache.org/jira/browse/CXF-8302
> Project: CXF
>  Issue Type: Task
>Reporter: Andriy Redko
>Assignee: Andriy Redko
>Priority: Major
> Fix For: 3.5.0
>
>
> https://headcrashing.wordpress.com/2019/06/25/jax-rs-2-2-nightly-builds-available/



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

[jira] [Updated] (CXF-8206) Update to saaj-impl 1.5.2

[Dennis Kieselhorst (Jira)]

 [ 
https://issues.apache.org/jira/browse/CXF-8206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Kieselhorst updated CXF-8206:

Fix Version/s: 3.4.0

> Update to saaj-impl 1.5.2
> -
>
> Key: CXF-8206
> URL: https://issues.apache.org/jira/browse/CXF-8206
> Project: CXF
>  Issue Type: Task
>  Components: JAX-WS Runtime
>Reporter: Alexey Markevich
>Priority: Major
> Fix For: 3.4.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>




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

[jira] [Resolved] (CXF-8198) Update CDI module to use Jakarta CDI and Inject API dependencies

[Dennis Kieselhorst (Jira)]

 [ 
https://issues.apache.org/jira/browse/CXF-8198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Kieselhorst resolved CXF-8198.
-
Resolution: Fixed

> Update CDI module to use Jakarta CDI and Inject API dependencies
> 
>
> Key: CXF-8198
> URL: https://issues.apache.org/jira/browse/CXF-8198
> Project: CXF
>  Issue Type: Task
>Reporter: Dennis Kieselhorst
>Assignee: Dennis Kieselhorst
>Priority: Major
> Fix For: 3.4.0
>
>
> <{color:#80}dependency{color}>
>  
> <{color:#80}groupId{color}>jakarta.enterprise
>  
> <{color:#80}artifactId{color}>jakarta.enterprise.cdi-api
>  <{color:#80}version{color}>2.0.2
>  
> <{color:#80}dependency{color}>
>  <{color:#80}groupId{color}>jakarta.inject
>  
> <{color:#80}artifactId{color}>jakarta.inject-api
>  <{color:#80}version{color}>1.0
> 



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

[jira] [Assigned] (CXF-8198) Update CDI module to use Jakarta CDI and Inject API dependencies

[Dennis Kieselhorst (Jira)]

 [ 
https://issues.apache.org/jira/browse/CXF-8198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Kieselhorst reassigned CXF-8198:
---

Assignee: Dennis Kieselhorst

> Update CDI module to use Jakarta CDI and Inject API dependencies
> 
>
> Key: CXF-8198
> URL: https://issues.apache.org/jira/browse/CXF-8198
> Project: CXF
>  Issue Type: Task
>Reporter: Dennis Kieselhorst
>Assignee: Dennis Kieselhorst
>Priority: Major
> Fix For: 3.4.0
>
>
> <{color:#80}dependency{color}>
>  
> <{color:#80}groupId{color}>jakarta.enterprise
>  
> <{color:#80}artifactId{color}>jakarta.enterprise.cdi-api
>  <{color:#80}version{color}>2.0.2
>  
> <{color:#80}dependency{color}>
>  <{color:#80}groupId{color}>jakarta.inject
>  
> <{color:#80}artifactId{color}>jakarta.inject-api
>  <{color:#80}version{color}>1.0
> 



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

[jira] [Commented] (CXF-8075) Plan for CXF 3.4.0 release

[Dennis Kieselhorst (Jira)]

[ 
https://issues.apache.org/jira/browse/CXF-8075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17132592#comment-17132592
 ] 

Dennis Kieselhorst commented on CXF-8075:
-

Well actually we can create a 3.5.0 version and add separate issues for these 
topics. JIRA then will display us the plan like this: 
https://issues.apache.org/jira/projects/CXF/versions/12344852

> Plan for CXF 3.4.0 release
> --
>
> Key: CXF-8075
> URL: https://issues.apache.org/jira/browse/CXF-8075
> Project: CXF
>  Issue Type: Task
>Reporter: Andriy Redko
>Priority: Major
> Fix For: 3.4.0
>
>
> There are multiple goals targeted for 3.4.0:
>  - align with Jakarta EE (switch to new artifacts / packages)
>  - JAX-RS 2.2, snapshots already available 
> (https://headcrashing.wordpress.com/2019/06/25/jax-rs-2-2-nightly-builds-available/)



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

[jira] [Resolved] (CXF-8151) Upgrade to Bean Validation 2.x

[Dennis Kieselhorst (Jira)]

 [ 
https://issues.apache.org/jira/browse/CXF-8151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Kieselhorst resolved CXF-8151.
-
Resolution: Fixed

> Upgrade to Bean Validation 2.x 
> ---
>
> Key: CXF-8151
> URL: https://issues.apache.org/jira/browse/CXF-8151
> Project: CXF
>  Issue Type: Task
>Reporter: Andriy Redko
>Assignee: Andriy Redko
>Priority: Major
> Fix For: 3.4.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> CXF is still using the Bean Validation 1.x API whereas all modern 
> implementations support 2.x mostly exlusively (Hibernate Validator 6.x, ...). 
> We probably should consider moving the baseline to 2.x at least with CXF 
> 3.4.0.



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

[jira] [Commented] (CXF-7949) Update Servlet dependency to 4.x and Tomcat to 9.x

[Dennis Kieselhorst (Jira)]

[ 
https://issues.apache.org/jira/browse/CXF-7949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17074420#comment-17074420
 ] 

Dennis Kieselhorst commented on CXF-7949:
-

Definitely, Confluence page is already open in edit mode :-)

> Update Servlet dependency to 4.x and Tomcat to 9.x
> --
>
> Key: CXF-7949
> URL: https://issues.apache.org/jira/browse/CXF-7949
> Project: CXF
>  Issue Type: Task
>Reporter: Dennis Kieselhorst
>Assignee: Dennis Kieselhorst
>Priority: Minor
> Fix For: 3.4.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Use Jakarta Servlet release https://github.com/eclipse-ee4j/servlet-api



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

[jira] [Assigned] (CXF-7949) Update Servlet dependency to 4.x and Tomcat to 9.x

[Dennis Kieselhorst (Jira)]

 [ 
https://issues.apache.org/jira/browse/CXF-7949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Kieselhorst reassigned CXF-7949:
---

Assignee: Dennis Kieselhorst

> Update Servlet dependency to 4.x and Tomcat to 9.x
> --
>
> Key: CXF-7949
> URL: https://issues.apache.org/jira/browse/CXF-7949
> Project: CXF
>  Issue Type: Task
>Reporter: Dennis Kieselhorst
>Assignee: Dennis Kieselhorst
>Priority: Minor
> Fix For: 3.4.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Use Jakarta Servlet release https://github.com/eclipse-ee4j/servlet-api



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

[jira] [Resolved] (CXF-7949) Update Servlet dependency to 4.x and Tomcat to 9.x

[Dennis Kieselhorst (Jira)]

 [ 
https://issues.apache.org/jira/browse/CXF-7949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Kieselhorst resolved CXF-7949.
-
Resolution: Fixed

> Update Servlet dependency to 4.x and Tomcat to 9.x
> --
>
> Key: CXF-7949
> URL: https://issues.apache.org/jira/browse/CXF-7949
> Project: CXF
>  Issue Type: Task
>Reporter: Dennis Kieselhorst
>Priority: Minor
> Fix For: 3.4.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Use Jakarta Servlet release https://github.com/eclipse-ee4j/servlet-api



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

[jira] [Updated] (CXF-7949) Update Servlet dependency to 4.x and Tomcat to 9.x

[Dennis Kieselhorst (Jira)]

 [ 
https://issues.apache.org/jira/browse/CXF-7949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Kieselhorst updated CXF-7949:

Summary: Update Servlet dependency to 4.x and Tomcat to 9.x  (was: Update 
Servlet dependency to 4.x, Tomcat to 9.x and Jetty to 10.x)

> Update Servlet dependency to 4.x and Tomcat to 9.x
> --
>
> Key: CXF-7949
> URL: https://issues.apache.org/jira/browse/CXF-7949
> Project: CXF
>  Issue Type: Task
>Reporter: Dennis Kieselhorst
>Priority: Minor
> Fix For: 3.4.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Use Jakarta Servlet release https://github.com/eclipse-ee4j/servlet-api



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

[jira] [Commented] (CXF-8151) Upgrade to Bean Validation 2.x

[Dennis Kieselhorst (Jira)]

[ 
https://issues.apache.org/jira/browse/CXF-8151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17074297#comment-17074297
 ] 

Dennis Kieselhorst commented on CXF-8151:
-

Thanks [~reta], we still have an issue with Swagger Core 1.x, even with the 
latest 1.6.1 version:
{noformat}
[ERROR] Feature resolution failed for 
[cxf-rs-description-swagger2/3.4.0.SNAPSHOT]
[ERROR] Message: Unable to resolve root: missing requirement [root] 
osgi.identity; osgi.identity=cxf-rs-description-swagger2; type=karaf.feature; 
version=3.4.0.SNAPSHOT; 
filter:="(&(osgi.identity=cxf-rs-description-swagger2)(type=karaf.feature)(version>=3.4.0.SNAPSHOT))"
 [caused by: Unable to resolve cxf-rs-description-swagger2/3.4.0.SNAPSHOT: 
missing requirement [cxf-rs-description-swagger2/3.4.0.SNAPSHOT] osgi.identity; 
osgi.identity=org.apache.cxf.cxf-rt-rs-service-description-swagger; 
type=osgi.bundle; version="[3.4.0.SNAPSHOT,3.4.0.SNAPSHOT]"; 
resolution:=mandatory [caused by: Unable to resolve 
org.apache.cxf.cxf-rt-rs-service-description-swagger/3.4.0.SNAPSHOT: missing 
requirement 
[org.apache.cxf.cxf-rt-rs-service-description-swagger/3.4.0.SNAPSHOT] 
osgi.wiring.package; 
filter:="(&(osgi.wiring.package=io.swagger.jaxrs.config)(version>=1.6.0)(!(version>=2.0.0)))"
 [caused by: Unable to resolve io.swagger.jaxrs/1.6.1: missing requirement 
[io.swagger.jaxrs/1.6.1] osgi.wiring.package; 
filter:="(&(osgi.wiring.package=io.swagger.config)(version>=1.6.0)(!(version>=2.0.0)))"
 [caused by: Unable to resolve io.swagger.core/1.6.1: missing requirement 
[io.swagger.core/1.6.1] osgi.wiring.package; 
filter:="(&(osgi.wiring.package=javax.validation.constraints)(version>=1.1.0)(!(version>=2.0.0)))"
{noformat}

Any idea how to solve this? Maybe we should discontinue support for 1.x for CXF 
3.4? What do you think?

> Upgrade to Bean Validation 2.x 
> ---
>
> Key: CXF-8151
> URL: https://issues.apache.org/jira/browse/CXF-8151
> Project: CXF
>  Issue Type: Task
>Reporter: Andriy Redko
>Assignee: Andriy Redko
>Priority: Major
> Fix For: 3.4.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> CXF is still using the Bean Validation 1.x API whereas all modern 
> implementations support 2.x mostly exlusively (Hibernate Validator 6.x, ...). 
> We probably should consider moving the baseline to 2.x at least with CXF 
> 3.4.0.



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

[jira] [Created] (CXF-8221) Upgrade Http Components Core and Client to 5.0

[Dennis Kieselhorst (Jira)]

Dennis Kieselhorst created CXF-8221:
---

 Summary: Upgrade Http Components Core and Client to 5.0
 Key: CXF-8221
 URL: https://issues.apache.org/jira/browse/CXF-8221
 Project: CXF
  Issue Type: Improvement
Reporter: Dennis Kieselhorst
 Fix For: 3.4.0


Notable changes and features included in the 5.0 series are:

* Support for the HTTP/2 protocol and conformance to requirements and
recommendations of the latest HTTP/2 protocol specification documents
(RFC 7540, RFC 7541.)

  Supported features:

** HPACK header compression
** Stream multiplexing (client and server)
** Flow control
** Response push
** Message trailers
** Expect-continue handshake
** Connection validation (ping)
** Application-layer protocol negotiation (ALPN)
** TLS 1.2 security features

* Improved conformance to requirements and recommendations of the
latest HTTP/1.1 protocol specification documents (RFC 7230, RFC 7231)

* New connection pool implementation with lax connection limit
guarantees and better performance under higher concurrency due to
absence of a global pool lock.

* Support for Reactive Streams API [http://www.reactive-streams.org/]

* Package name space changed to 'org.apache.hc.client5'.

* Maven group id changed to 'org.apache.httpcomponents.client5'.

HttpClient 5.0 releases can be co-located with earlier major versions
on the same classpath due to the change in package names and Maven
module coordinates.

Download - 
Release notes - <
https://www.apache.org/dist/httpcomponents/httpclient/RELEASE_NOTES-5.0.x.txt



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

[jira] [Commented] (CXF-7949) Update Servlet dependency to 4.x, Tomcat to 9.x and Jetty to 10.x

[Dennis Kieselhorst (Jira)]

[ 
https://issues.apache.org/jira/browse/CXF-7949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17018974#comment-17018974
 ] 

Dennis Kieselhorst commented on CXF-7949:
-

Depends on which changes you mean.

Still works without {{cxf.servlet-api-2.5.artifact}} and 
{{cxf.servlet-api-2.5.version}} (the only usage is in 
cxf-rt-transports-http-netty-server, we can set a version there, seems that 
this servlet bridge wasn't update to more recent servlet spec versions in the 
past).

Jakarta Servlet API 4.0.3 ThreadLocalServletContext requires some new methods 
to be added, apart from that it seems to work. Same for Tomcat 9.0.30.

With Jetty 10.0.0.alpha1 CXF doesn't compile as jetty-continuation no longer 
exists.

So maybe we use Servlet 4.x for now and do Jetty 10 with Servlet 5.x later. 
I've created a branch for it: 
[https://github.com/apache/cxf/tree/CXF-7949_jakarta-servlet]

> Update Servlet dependency to 4.x, Tomcat to 9.x and Jetty to 10.x
> -
>
> Key: CXF-7949
> URL: https://issues.apache.org/jira/browse/CXF-7949
> Project: CXF
>  Issue Type: Task
>Reporter: Dennis Kieselhorst
>Priority: Minor
> Fix For: 3.4.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Use Jakarta Servlet release https://github.com/eclipse-ee4j/servlet-api



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

[jira] [Created] (CXF-8199) Upgrade to Jakarta EL

[Dennis Kieselhorst (Jira)]

Dennis Kieselhorst created CXF-8199:
---

 Summary: Upgrade to Jakarta EL
 Key: CXF-8199
 URL: https://issues.apache.org/jira/browse/CXF-8199
 Project: CXF
  Issue Type: Task
Reporter: Dennis Kieselhorst
 Fix For: 3.4.0






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

[jira] [Created] (CXF-8198) Update CDI module to use Jakarta CDI and Inject API dependencies

[Dennis Kieselhorst (Jira)]

Dennis Kieselhorst created CXF-8198:
---

 Summary: Update CDI module to use Jakarta CDI and Inject API 
dependencies
 Key: CXF-8198
 URL: https://issues.apache.org/jira/browse/CXF-8198
 Project: CXF
  Issue Type: Task
Reporter: Dennis Kieselhorst
 Fix For: 3.4.0


<{color:#80}dependency{color}>
 
<{color:#80}groupId{color}>jakarta.enterprise
 
<{color:#80}artifactId{color}>jakarta.enterprise.cdi-api
 <{color:#80}version{color}>2.0.2
 
<{color:#80}dependency{color}>
 <{color:#80}groupId{color}>jakarta.inject
 
<{color:#80}artifactId{color}>jakarta.inject-api
 <{color:#80}version{color}>1.0




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

[jira] [Commented] (CXF-8151) Upgrade to Bean Validation 2.x

[Dennis Kieselhorst (Jira)]

[ 
https://issues.apache.org/jira/browse/CXF-8151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17018862#comment-17018862
 ] 

Dennis Kieselhorst commented on CXF-8151:
-

As far as I can see only Swagger 1.x is affected. An exclude is probably not 
enough to fix the OSGi issue:

{{[ERROR] Failed to execute goal 
org.apache.karaf.tooling:karaf-maven-plugin:4.2.7:verify (verify) on project 
apache-cxf: Verification failures: Verification failures:}}
{{[ERROR] Feature resolution failed for 
[cxf-rs-description-swagger2/3.4.0.SNAPSHOT]}}
{{[ERROR] Message: Unable to resolve root: missing requirement [root] 
osgi.identity; osgi.identity=cxf-rs-description-swagger2; type=karaf.feature; 
version=3.4.0.SNAPSHOT; 
filter:="(&(osgi.identity=cxf-rs-description-swagger2)(type=karaf.feature)(version>=3.4.0.SNAPSHOT))"
 [caused by: Unable to resolve cxf-rs-description-swagger2/3.4.0.SNAPSHOT: 
missing requirement [cxf-rs-description-swagger2/3.4.0.SNAPSHOT] osgi.identity; 
osgi.identity=org.apache.cxf.cxf-rt-rs-service-description-swagger; 
type=osgi.bundle; version="[3.4.0.SNAPSHOT,3.4.0.SNAPSHOT]"; 
resolution:=mandatory [caused by: Unable to resolve 
org.apache.cxf.cxf-rt-rs-service-description-swagger/3.4.0.SNAPSHOT: missing 
requirement 
[org.apache.cxf.cxf-rt-rs-service-description-swagger/3.4.0.SNAPSHOT] 
osgi.wiring.package; 
filter:="(&(osgi.wiring.package=io.swagger.jaxrs.config)(version>=1.6.0)(!(version>=2.0.0)))"
 [caused by: Unable to resolve io.swagger.jaxrs/1.6.0: missing requirement 
[io.swagger.jaxrs/1.6.0] osgi.wiring.package; 
filter:="(&(osgi.wiring.package=io.swagger.config)(version>=1.6.0)(!(version>=2.0.0)))"
 [caused by: Unable to resolve io.swagger.core/1.6.0: missing requirement 
[io.swagger.core/1.6.0] osgi.wiring.package; 
filter:="(&(osgi.wiring.package=javax.validation.constraints)(version>=1.1.0)(!(version>=2.0.0)))"}}

We can also think about no longer supporting Swagger 1.x with CXF 3.4. But as 
many users still haven't migrated to OpenAPI v3 it's probably to early for 
that...

> Upgrade to Bean Validation 2.x 
> ---
>
> Key: CXF-8151
> URL: https://issues.apache.org/jira/browse/CXF-8151
> Project: CXF
>  Issue Type: Task
>Reporter: Andriy Redko
>Assignee: Andriy Redko
>Priority: Major
> Fix For: 3.4.0
>
>
> CXF is still using the Bean Validation 1.x API whereas all modern 
> implementations support 2.x mostly exlusively (Hibernate Validator 6.x, ...). 
> We probably should consider moving the baseline to 2.x at least with CXF 
> 3.4.0.



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

[jira] [Commented] (CXF-7949) Update Servlet dependency to 4.x, Tomcat to 9.x and Jetty to 10.x

[Dennis Kieselhorst (Jira)]

[ 
https://issues.apache.org/jira/browse/CXF-7949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17015864#comment-17015864
 ] 

Dennis Kieselhorst commented on CXF-7949:
-

Do we still need {{cxf.servlet-api-2.5.artifact}} and 
{{cxf.servlet-api-2.5.version}} or can we get rid of it?

> Update Servlet dependency to 4.x, Tomcat to 9.x and Jetty to 10.x
> -
>
> Key: CXF-7949
> URL: https://issues.apache.org/jira/browse/CXF-7949
> Project: CXF
>  Issue Type: Task
>Reporter: Dennis Kieselhorst
>Priority: Minor
> Fix For: 3.4.0
>
>
> Use Jakarta Servlet release https://github.com/eclipse-ee4j/servlet-api



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

[jira] [Resolved] (CXF-8159) Update to Swagger 2.1.1 / 1.6.0

[Dennis Kieselhorst (Jira)]

 [ 
https://issues.apache.org/jira/browse/CXF-8159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Kieselhorst resolved CXF-8159.
-
Resolution: Fixed

> Update to Swagger 2.1.1 / 1.6.0
> ---
>
> Key: CXF-8159
> URL: https://issues.apache.org/jira/browse/CXF-8159
> Project: CXF
>  Issue Type: Task
>Affects Versions: 3.2.11, 3.3.4
>Reporter: Andriy Redko
>Assignee: Dennis Kieselhorst
>Priority: Major
> Fix For: 3.4.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>




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

[jira] [Updated] (CXF-8159) Update to Swagger 2.1.1 / 1.6.0

[Dennis Kieselhorst (Jira)]

 [ 
https://issues.apache.org/jira/browse/CXF-8159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Kieselhorst updated CXF-8159:

Summary: Update to Swagger 2.1.1 / 1.6.0  (was: Update to Swagger 2.1.0 / 
1.6.0)

> Update to Swagger 2.1.1 / 1.6.0
> ---
>
> Key: CXF-8159
> URL: https://issues.apache.org/jira/browse/CXF-8159
> Project: CXF
>  Issue Type: Task
>Affects Versions: 3.2.11, 3.3.4
>Reporter: Andriy Redko
>Assignee: Andriy Redko
>Priority: Major
> Fix For: 3.4.0
>
>




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

[jira] [Resolved] (CXF-8134) Upgrade to Spring Boot 2.2

[Dennis Kieselhorst (Jira)]

 [ 
https://issues.apache.org/jira/browse/CXF-8134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Kieselhorst resolved CXF-8134.
-
Resolution: Fixed

Bean validation stuff needs to be solved in CXF-8151

> Upgrade to Spring Boot 2.2
> --
>
> Key: CXF-8134
> URL: https://issues.apache.org/jira/browse/CXF-8134
> Project: CXF
>  Issue Type: Improvement
>Affects Versions: 3.4.0
>Reporter: Andriy Redko
>Assignee: Andriy Redko
>Priority: Major
> Fix For: 3.4.0
>
> Attachments: image-2019-12-22-16-34-24-327.png, 
> image-2019-12-22-16-34-31-499.png, image-2019-12-22-16-34-44-435.png
>
>
> Spring Boot 2.2 has just been released:
>  * [https://spring.io/blog/2019/10/16/spring-boot-2-2-0]
>  * 
> [https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-2.2-Release-Notes]
> One of the most important and impactful changes are related to *Jakarta EE 
> dependencies*:
>  
> {quote}Where possible, we have moved from Java EE dependencies with a 
> {{javax.**}} group ID to the equivalent Jakarta EE dependencies with a 
> {{jakarta.}} group ID in Spring Boot’s starters. Dependency management for 
> the Jakarta EE API dependencies has been added alongside the existing 
> dependency management for the Java EE API dependencies. The dependency 
> management for the Java EE API dependencies will be removed in the future and 
> all users are encouraged to move to the Jakarta EE API dependencies.
> As part of the Java EE to Jakarta EE migration, two dependencies have changed 
> artifact ID in their latest maintenance releases. {{com.sun.mail:javax.mail}} 
> is now {{com.sun.mail:jakarta.mail}} and {{org.glassfish:javax.el}} is now 
> {{org.glassfish:jakarta.el}}. In the unlikely event that you were using 
> either of these dependencies directly, please update your {{pom.xml}} or 
> {{build.gradle}} accordingly.
> {quote}
>  
>  



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

[jira] [Resolved] (CXF-8165) Upgrade to Spring Framework 5.2.x and Spring Security 5.2.x

[Dennis Kieselhorst (Jira)]

 [ 
https://issues.apache.org/jira/browse/CXF-8165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Kieselhorst resolved CXF-8165.
-
Resolution: Fixed

> Upgrade to Spring Framework 5.2.x and Spring Security 5.2.x
> ---
>
> Key: CXF-8165
> URL: https://issues.apache.org/jira/browse/CXF-8165
> Project: CXF
>  Issue Type: Task
>Affects Versions: 3.4.0
>Reporter: Andriy Redko
>Assignee: Andriy Redko
>Priority: Major
> Fix For: 3.4.0
>
>




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

[jira] [Commented] (CXF-8151) Upgrade to Bean Validation 2.x

[Dennis Kieselhorst (Jira)]

[ 
https://issues.apache.org/jira/browse/CXF-8151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17012524#comment-17012524
 ] 

Dennis Kieselhorst commented on CXF-8151:
-

Created branch CXF-8151_bean-validation for it. Again OSGi issues, looks like 
we need to combine it with CXF-8159.

> Upgrade to Bean Validation 2.x 
> ---
>
> Key: CXF-8151
> URL: https://issues.apache.org/jira/browse/CXF-8151
> Project: CXF
>  Issue Type: Task
>Reporter: Andriy Redko
>Assignee: Andriy Redko
>Priority: Major
> Fix For: 3.4.0
>
>
> CXF is still using the Bean Validation 1.x API whereas all modern 
> implementations support 2.x mostly exlusively (Hibernate Validator 6.x, ...). 
> We probably should consider moving the baseline to 2.x at least with CXF 
> 3.4.0.



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

[jira] [Updated] (CXF-8159) Update to Swagger 2.1.0 / 1.6.0

[Dennis Kieselhorst (Jira)]

 [ 
https://issues.apache.org/jira/browse/CXF-8159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Kieselhorst updated CXF-8159:

Fix Version/s: 3.4.0

> Update to Swagger 2.1.0 / 1.6.0
> ---
>
> Key: CXF-8159
> URL: https://issues.apache.org/jira/browse/CXF-8159
> Project: CXF
>  Issue Type: Task
>Affects Versions: 3.2.11, 3.3.4
>Reporter: Andriy Redko
>Assignee: Andriy Redko
>Priority: Major
> Fix For: 3.4.0
>
>




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

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

[Dennis Kieselhorst (Jira)]

 [ 
https://issues.apache.org/jira/browse/CXF-7910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Kieselhorst resolved CXF-7910.
-
  Assignee: Dennis Kieselhorst
Resolution: Fixed

> Change JAX-WS javax to jakarta artifact dependencies
> 
>
> Key: CXF-7910
> URL: https://issues.apache.org/jira/browse/CXF-7910
> Project: CXF
>  Issue Type: Task
>  Components: JAX-WS Runtime
>Reporter: Dennis Kieselhorst
>Assignee: Dennis Kieselhorst
>Priority: Minor
> Fix For: 3.4.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> See https://github.com/eclipse-ee4j/jax-ws-api/issues/46
> According to https://projects.eclipse.org/projects/ee4j.jaxws/ will be 
> released on 2018-12-14.



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

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

[Dennis Kieselhorst (Jira)]

[ 
https://issues.apache.org/jira/browse/CXF-7910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17009690#comment-17009690
 ] 

Dennis Kieselhorst commented on CXF-7910:
-

I've integrated the servicemix release. Looks good now...

> Change JAX-WS javax to jakarta artifact dependencies
> 
>
> Key: CXF-7910
> URL: https://issues.apache.org/jira/browse/CXF-7910
> Project: CXF
>  Issue Type: Task
>  Components: JAX-WS Runtime
>Reporter: Dennis Kieselhorst
>Priority: Minor
> Fix For: 3.4.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> See https://github.com/eclipse-ee4j/jax-ws-api/issues/46
> According to https://projects.eclipse.org/projects/ee4j.jaxws/ will be 
> released on 2018-12-14.



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

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

[Dennis Kieselhorst (Jira)]

[ 
https://issues.apache.org/jira/browse/CXF-7910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17007262#comment-17007262
 ] 

Dennis Kieselhorst commented on CXF-7910:
-

[~mohanaraosv] you can already use 3.3.4 with the new Jakarta dependencies by 
excluding the javax ones and adding the new ones manually.

We will provide updated POMs with 3.4.0.

> Change JAX-WS javax to jakarta artifact dependencies
> 
>
> Key: CXF-7910
> URL: https://issues.apache.org/jira/browse/CXF-7910
> Project: CXF
>  Issue Type: Task
>  Components: JAX-WS Runtime
>Reporter: Dennis Kieselhorst
>Priority: Minor
> Fix For: 3.4.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> See https://github.com/eclipse-ee4j/jax-ws-api/issues/46
> According to https://projects.eclipse.org/projects/ee4j.jaxws/ will be 
> released on 2018-12-14.



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

[jira] [Commented] (CXF-7996) Jakarta EE TCKs and compatibility

[Dennis Kieselhorst (Jira)]

[ 
https://issues.apache.org/jira/browse/CXF-7996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17004252#comment-17004252
 ] 

Dennis Kieselhorst commented on CXF-7996:
-

Thanks [~reta]! Looks as if we need to take a look at 106 tests one by one. But 
before trying to improve the results, it makes sense to have a Jenkins build 
job for it. Do you have a script or a list of commands to produce this? Happy 
to support with setting up the job...

> Jakarta EE TCKs and compatibility
> -
>
> Key: CXF-7996
> URL: https://issues.apache.org/jira/browse/CXF-7996
> Project: CXF
>  Issue Type: Task
>Reporter: Andriy Redko
>Assignee: Andriy Redko
>Priority: Major
> Attachments: JTreport-26-December-2019.zip, JTwork- 
> 26-December-2019.zip
>
>
> Mail thread: 
> [https://mail-archives.apache.org/mod_mbox/cxf-dev/201901.mbox/%3C6edd1da6-d651-]
>  e2a3-8092-59bdc7a54...@apache.org%3E
> Jakarta EE TCK: 
> [https://projects.eclipse.org/proposals/eclipse-jakarta-ee-tck]
>  Github Repo: [https://github.com/eclipse-ee4j/jakartaee-tck]
> Latest updates from [jakarta.ee-spec] TCK information, June 2019, the 
> excerpts: 
>  * {color:#00}We have summed up some information about how the TCK can be 
> built (or {color}
>  {color:#00}grabbed pre-built), configured, and run [1].{color}
>  * {color:#00}This is assumed to be run against a Glassfish with the 
> latest API {color}
>  {color:#00}integrated (replacing the original API in the 
> Glassfish).{color}
>  * {color:#00}We have created a recording of a presentation of the 
> Jenkins jobs that {color}
>  {color:#00}manage all that [2].{color}
>  * {color:#00}We have created 3 Jenkins files for pipeline job (as an 
> example for {color}
>  {color:#00}JSON-B TCK) to a) properly set the ts.jte configuration file, 
> b) to grab {color}
>  {color:#00}the API artifact built by a Jenkins build job and integrate 
> it to a {color}
>  {color:#00}Glassfish and c) to grab the pre-built TCK bundle from 
> Eclipse Download, {color}
>  {color:#00}grab the configured ts.jte file, grab the Glassfish with new 
> API {color}
>  {color:#00}integrated, and run the TCK [3].{color}
> {color:#00}For the complete information, please allow me to mention the 
> list of the {color}
>  {color:#00}TCK tasks needed to be done before the Jakarta EE release can 
> be {color}
>  {color:#00}finished [4].{color}
> {color:#00}The [5] is the example how to run Jakarta EE TCKs with 
> Tomcat.{color}
> {color:#00}{color:#00}The{color} [6] is the official list of the 
> instructions.{color}
>  
> {color:#00}[1] 
> {color}+[https://wiki.eclipse.org/TCK:Build_From_Jakarta_EE_TCK_Repo_And_Run]+
> {color:#00}[2] {color}+[https://youtu.be/nnD1KMvh0to]+
> {color:#00}[3] {color}
>  
> +[https://wiki.eclipse.org/TCK:Build_From_Jakarta_EE_TCK_Repo_And_Run#Jenkins_Pipelines]+
> {color:#00}[4] {color}+[https://github.com/orgs/eclipse-ee4j/projects/14]+
> [5] [https://cwiki.apache.org/confluence/display/TOMCAT/Jakarta+EE+TCKs]
> [6]
> +[https://github.com/eclipse-ee4j/jakartaee-tck/wiki/Instructions-for-building-and-running-JakartaEE-TCK-bundle]+



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

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

[Dennis Kieselhorst (Jira)]

[ 
https://issues.apache.org/jira/browse/CXF-7910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17002171#comment-17002171
 ] 

Dennis Kieselhorst commented on CXF-7910:
-

Asked on Servicemix list for a release: 
https://lists.apache.org/thread.html/bb33b53573d3bc94510763c70e282c4de167f823dddaf1eb43c29219%40%3Cdev.servicemix.apache.org%3E

> Change JAX-WS javax to jakarta artifact dependencies
> 
>
> Key: CXF-7910
> URL: https://issues.apache.org/jira/browse/CXF-7910
> Project: CXF
>  Issue Type: Task
>  Components: JAX-WS Runtime
>Reporter: Dennis Kieselhorst
>Priority: Minor
> Fix For: 3.4.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> See https://github.com/eclipse-ee4j/jax-ws-api/issues/46
> According to https://projects.eclipse.org/projects/ee4j.jaxws/ will be 
> released on 2018-12-14.



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

[jira] [Commented] (CXF-8134) Upgrade to Spring Boot 2.2

[Dennis Kieselhorst (Jira)]

[ 
https://issues.apache.org/jira/browse/CXF-8134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17002168#comment-17002168
 ] 

Dennis Kieselhorst commented on CXF-8134:
-

Reverted on master and moved to 
https://github.com/apache/cxf/tree/CXF-8134_CXF-8165_spring-dep-upgrade

> Upgrade to Spring Boot 2.2
> --
>
> Key: CXF-8134
> URL: https://issues.apache.org/jira/browse/CXF-8134
> Project: CXF
>  Issue Type: Improvement
>Affects Versions: 3.4.0
>Reporter: Andriy Redko
>Assignee: Andriy Redko
>Priority: Major
> Fix For: 3.4.0
>
> Attachments: image-2019-12-22-16-34-24-327.png, 
> image-2019-12-22-16-34-31-499.png, image-2019-12-22-16-34-44-435.png
>
>
> Spring Boot 2.2 has just been released:
>  * [https://spring.io/blog/2019/10/16/spring-boot-2-2-0]
>  * 
> [https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-2.2-Release-Notes]
> One of the most important and impactful changes are related to *Jakarta EE 
> dependencies*:
>  
> {quote}Where possible, we have moved from Java EE dependencies with a 
> {{javax.**}} group ID to the equivalent Jakarta EE dependencies with a 
> {{jakarta.}} group ID in Spring Boot’s starters. Dependency management for 
> the Jakarta EE API dependencies has been added alongside the existing 
> dependency management for the Java EE API dependencies. The dependency 
> management for the Java EE API dependencies will be removed in the future and 
> all users are encouraged to move to the Jakarta EE API dependencies.
> As part of the Java EE to Jakarta EE migration, two dependencies have changed 
> artifact ID in their latest maintenance releases. {{com.sun.mail:javax.mail}} 
> is now {{com.sun.mail:jakarta.mail}} and {{org.glassfish:javax.el}} is now 
> {{org.glassfish:jakarta.el}}. In the unlikely event that you were using 
> either of these dependencies directly, please update your {{pom.xml}} or 
> {{build.gradle}} accordingly.
> {quote}
>  
>  



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

[jira] [Commented] (CXF-8165) Upgrade to Spring Framework 5.2.x and Spring Security 5.2.x

[Dennis Kieselhorst (Jira)]

[ 
https://issues.apache.org/jira/browse/CXF-8165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17002169#comment-17002169
 ] 

Dennis Kieselhorst commented on CXF-8165:
-

Reverted on master and moved to 
[https://github.com/apache/cxf/tree/CXF-8134_CXF-8165_spring-dep-upgrade] for 
now as discussed in CXF-8134.

> Upgrade to Spring Framework 5.2.x and Spring Security 5.2.x
> ---
>
> Key: CXF-8165
> URL: https://issues.apache.org/jira/browse/CXF-8165
> Project: CXF
>  Issue Type: Task
>Affects Versions: 3.4.0
>Reporter: Andriy Redko
>Assignee: Andriy Redko
>Priority: Major
> Fix For: 3.4.0
>
>




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

[jira] [Reopened] (CXF-8165) Upgrade to Spring Framework 5.2.x and Spring Security 5.2.x

[Dennis Kieselhorst (Jira)]

 [ 
https://issues.apache.org/jira/browse/CXF-8165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Kieselhorst reopened CXF-8165:
-

> Upgrade to Spring Framework 5.2.x and Spring Security 5.2.x
> ---
>
> Key: CXF-8165
> URL: https://issues.apache.org/jira/browse/CXF-8165
> Project: CXF
>  Issue Type: Task
>Affects Versions: 3.4.0
>Reporter: Andriy Redko
>Assignee: Andriy Redko
>Priority: Major
> Fix For: 3.4.0
>
>




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

[jira] [Reopened] (CXF-8134) Upgrade to Spring Boot 2.2

[Dennis Kieselhorst (Jira)]

 [ 
https://issues.apache.org/jira/browse/CXF-8134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Kieselhorst reopened CXF-8134:
-

> Upgrade to Spring Boot 2.2
> --
>
> Key: CXF-8134
> URL: https://issues.apache.org/jira/browse/CXF-8134
> Project: CXF
>  Issue Type: Improvement
>Affects Versions: 3.4.0
>Reporter: Andriy Redko
>Assignee: Andriy Redko
>Priority: Major
> Fix For: 3.4.0
>
> Attachments: image-2019-12-22-16-34-24-327.png, 
> image-2019-12-22-16-34-31-499.png, image-2019-12-22-16-34-44-435.png
>
>
> Spring Boot 2.2 has just been released:
>  * [https://spring.io/blog/2019/10/16/spring-boot-2-2-0]
>  * 
> [https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-2.2-Release-Notes]
> One of the most important and impactful changes are related to *Jakarta EE 
> dependencies*:
>  
> {quote}Where possible, we have moved from Java EE dependencies with a 
> {{javax.**}} group ID to the equivalent Jakarta EE dependencies with a 
> {{jakarta.}} group ID in Spring Boot’s starters. Dependency management for 
> the Jakarta EE API dependencies has been added alongside the existing 
> dependency management for the Java EE API dependencies. The dependency 
> management for the Java EE API dependencies will be removed in the future and 
> all users are encouraged to move to the Jakarta EE API dependencies.
> As part of the Java EE to Jakarta EE migration, two dependencies have changed 
> artifact ID in their latest maintenance releases. {{com.sun.mail:javax.mail}} 
> is now {{com.sun.mail:jakarta.mail}} and {{org.glassfish:javax.el}} is now 
> {{org.glassfish:jakarta.el}}. In the unlikely event that you were using 
> either of these dependencies directly, please update your {{pom.xml}} or 
> {{build.gradle}} accordingly.
> {quote}
>  
>  



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

[jira] [Commented] (CXF-8134) Upgrade to Spring Boot 2.2

[Dennis Kieselhorst (Jira)]

[ 
https://issues.apache.org/jira/browse/CXF-8134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17002165#comment-17002165
 ] 

Dennis Kieselhorst commented on CXF-8134:
-

Ok my bad, looks like I did the testing without properly installing the master 
branch but having built the branch with the fixed dependencies before :( It's 
working except the OSGi mess so I'll revert the changes and move them to a 
separate branch...

> Upgrade to Spring Boot 2.2
> --
>
> Key: CXF-8134
> URL: https://issues.apache.org/jira/browse/CXF-8134
> Project: CXF
>  Issue Type: Improvement
>Affects Versions: 3.4.0
>Reporter: Andriy Redko
>Assignee: Andriy Redko
>Priority: Major
> Fix For: 3.4.0
>
> Attachments: image-2019-12-22-16-34-24-327.png, 
> image-2019-12-22-16-34-31-499.png, image-2019-12-22-16-34-44-435.png
>
>
> Spring Boot 2.2 has just been released:
>  * [https://spring.io/blog/2019/10/16/spring-boot-2-2-0]
>  * 
> [https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-2.2-Release-Notes]
> One of the most important and impactful changes are related to *Jakarta EE 
> dependencies*:
>  
> {quote}Where possible, we have moved from Java EE dependencies with a 
> {{javax.**}} group ID to the equivalent Jakarta EE dependencies with a 
> {{jakarta.}} group ID in Spring Boot’s starters. Dependency management for 
> the Jakarta EE API dependencies has been added alongside the existing 
> dependency management for the Java EE API dependencies. The dependency 
> management for the Java EE API dependencies will be removed in the future and 
> all users are encouraged to move to the Jakarta EE API dependencies.
> As part of the Java EE to Jakarta EE migration, two dependencies have changed 
> artifact ID in their latest maintenance releases. {{com.sun.mail:javax.mail}} 
> is now {{com.sun.mail:jakarta.mail}} and {{org.glassfish:javax.el}} is now 
> {{org.glassfish:jakarta.el}}. In the unlikely event that you were using 
> either of these dependencies directly, please update your {{pom.xml}} or 
> {{build.gradle}} accordingly.
> {quote}
>  
>  



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

[jira] [Commented] (CXF-8134) Upgrade to Spring Boot 2.2

[Dennis Kieselhorst (Jira)]

[ 
https://issues.apache.org/jira/browse/CXF-8134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17001993#comment-17001993
 ] 

Dennis Kieselhorst commented on CXF-8134:
-

Well I share that concern but looking at our sample projects I haven't noticed 
any duplicate dependencies.

> Upgrade to Spring Boot 2.2
> --
>
> Key: CXF-8134
> URL: https://issues.apache.org/jira/browse/CXF-8134
> Project: CXF
>  Issue Type: Improvement
>Affects Versions: 3.4.0
>Reporter: Andriy Redko
>Assignee: Andriy Redko
>Priority: Major
> Fix For: 3.4.0
>
>
> Spring Boot 2.2 has just been released:
>  * [https://spring.io/blog/2019/10/16/spring-boot-2-2-0]
>  * 
> [https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-2.2-Release-Notes]
> One of the most important and impactful changes are related to *Jakarta EE 
> dependencies*:
>  
> {quote}Where possible, we have moved from Java EE dependencies with a 
> {{javax.**}} group ID to the equivalent Jakarta EE dependencies with a 
> {{jakarta.}} group ID in Spring Boot’s starters. Dependency management for 
> the Jakarta EE API dependencies has been added alongside the existing 
> dependency management for the Java EE API dependencies. The dependency 
> management for the Java EE API dependencies will be removed in the future and 
> all users are encouraged to move to the Jakarta EE API dependencies.
> As part of the Java EE to Jakarta EE migration, two dependencies have changed 
> artifact ID in their latest maintenance releases. {{com.sun.mail:javax.mail}} 
> is now {{com.sun.mail:jakarta.mail}} and {{org.glassfish:javax.el}} is now 
> {{org.glassfish:jakarta.el}}. In the unlikely event that you were using 
> either of these dependencies directly, please update your {{pom.xml}} or 
> {{build.gradle}} accordingly.
> {quote}
>  
>  



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

[jira] [Resolved] (CXF-8134) Upgrade to Spring Boot 2.2

[Dennis Kieselhorst (Jira)]

 [ 
https://issues.apache.org/jira/browse/CXF-8134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Kieselhorst resolved CXF-8134.
-
Resolution: Fixed

Hi [~reta],

we should definitely get the Jakarta dependency changes done but the newest 
Spring Boot version still works with CXF so I did the upgrade. Let me know if I 
am missing something.

Best,

Dennis

> Upgrade to Spring Boot 2.2
> --
>
> Key: CXF-8134
> URL: https://issues.apache.org/jira/browse/CXF-8134
> Project: CXF
>  Issue Type: Improvement
>Affects Versions: 3.4.0
>Reporter: Andriy Redko
>Assignee: Andriy Redko
>Priority: Major
> Fix For: 3.4.0
>
>
> Spring Boot 2.2 has just been released:
>  * [https://spring.io/blog/2019/10/16/spring-boot-2-2-0]
>  * 
> [https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-2.2-Release-Notes]
> One of the most important and impactful changes are related to *Jakarta EE 
> dependencies*:
>  
> {quote}Where possible, we have moved from Java EE dependencies with a 
> {{javax.**}} group ID to the equivalent Jakarta EE dependencies with a 
> {{jakarta.}} group ID in Spring Boot’s starters. Dependency management for 
> the Jakarta EE API dependencies has been added alongside the existing 
> dependency management for the Java EE API dependencies. The dependency 
> management for the Java EE API dependencies will be removed in the future and 
> all users are encouraged to move to the Jakarta EE API dependencies.
> As part of the Java EE to Jakarta EE migration, two dependencies have changed 
> artifact ID in their latest maintenance releases. {{com.sun.mail:javax.mail}} 
> is now {{com.sun.mail:jakarta.mail}} and {{org.glassfish:javax.el}} is now 
> {{org.glassfish:jakarta.el}}. In the unlikely event that you were using 
> either of these dependencies directly, please update your {{pom.xml}} or 
> {{build.gradle}} accordingly.
> {quote}
>  
>  



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

[jira] [Resolved] (CXF-8165) Upgrade to Spring Framework 5.2.x and Spring Security 5.2.x

[Dennis Kieselhorst (Jira)]

 [ 
https://issues.apache.org/jira/browse/CXF-8165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Kieselhorst resolved CXF-8165.
-
Resolution: Fixed

> Upgrade to Spring Framework 5.2.x and Spring Security 5.2.x
> ---
>
> Key: CXF-8165
> URL: https://issues.apache.org/jira/browse/CXF-8165
> Project: CXF
>  Issue Type: Task
>Affects Versions: 3.4.0
>Reporter: Andriy Redko
>Assignee: Andriy Redko
>Priority: Major
> Fix For: 3.4.0
>
>




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

[jira] [Updated] (CXF-8173) Illegal reflective access to field java.util.concurrent.ThreadPoolExecutor.mainLock

[Dennis Kieselhorst (Jira)]

 [ 
https://issues.apache.org/jira/browse/CXF-8173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Kieselhorst updated CXF-8173:

Fix Version/s: 3.3.5
   3.4.0

> Illegal reflective access to field 
> java.util.concurrent.ThreadPoolExecutor.mainLock
> ---
>
> Key: CXF-8173
> URL: https://issues.apache.org/jira/browse/CXF-8173
> Project: CXF
>  Issue Type: Bug
>Affects Versions: 3.3.4
>Reporter: Jimmy Praet
>Assignee: Freeman Yue Fang
>Priority: Major
> Fix For: 3.4.0, 3.3.5
>
>
> I get the following warning on JDK 11:
> {code:java}
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by 
> org.apache.cxf.common.util.ReflectionUtil$11 
> (file:/D:/mvn_repo/org/apache/cxf/cxf-core/3.3.4/cxf-core-3.3.4.jar) to field 
> java.util.concurrent.ThreadPoolExecutor.mainLock
> WARNING: Please consider reporting this to the maintainers of 
> org.apache.cxf.common.util.ReflectionUtil$11
> WARNING: Use --illegal-access=warn to enable warnings of further illegal 
> reflective access operations
> WARNING: All illegal access operations will be denied in a future 
> release{code}
>  With --illegal-access=debug:
> {code:java}
> WARNING: Illegal reflective access by 
> org.apache.cxf.common.util.ReflectionUtil$11 
> (file:/D:/mvn_repo/org/apache/cxf/cxf-core/3.3.4/cxf-core-3.3.4.jar) to field 
> java.util.concurrent.ThreadPoolExecutor.mainLock
>  at org.apache.cxf.common.util.ReflectionUtil$11.run(ReflectionUtil.java:184)
>  at org.apache.cxf.common.util.ReflectionUtil$11.run(ReflectionUtil.java:182)
>  at java.base/java.security.AccessController.doPrivileged(Native Method)
>  at 
> org.apache.cxf.common.util.ReflectionUtil.setAccessible(ReflectionUtil.java:182)
>  at 
> org.apache.cxf.workqueue.AutomaticWorkQueueImpl.getExecutor(AutomaticWorkQueueImpl.java:206)
>  at 
> org.apache.cxf.workqueue.AutomaticWorkQueueImpl.execute(AutomaticWorkQueueImpl.java:425)
>  at 
> org.apache.cxf.workqueue.AutomaticWorkQueueImpl.execute(AutomaticWorkQueueImpl.java:455)
>  at 
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseOnWorkqueue(HTTPConduit.java:1233)
>  at 
> org.apache.cxf.transport.http.URLConnectionHTTPConduit$URLConnectionWrappedOutputStream.handleResponseAsync(URLConnectionHTTPConduit.java:333)
>  at 
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1572)
>  at 
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1371)
>  at 
> org.apache.cxf.ext.logging.LoggingOutputStream.postClose(LoggingOutputStream.java:53)
>  at org.apache.cxf.io.CachedOutputStream.close(CachedOutputStream.java:228)
>  at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56)
>  at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:671)
>  at 
> org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:63)
>  at 
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)
>  at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:530)
>  at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:434)
>  at org.apache.camel.component.cxf.CxfProducer.process(CxfProducer.java:117)
>  at 
> be.fgov.kszbcss.camel.support.component.soap.SoapCallProducer.process(SoapCallProducer.java:93)
>  at org.apache.camel.processor.SendProcessor.process(SendProcessor.java:134)
>  at 
> org.apache.camel.processor.errorhandler.RedeliveryErrorHandler$RedeliveryState.run(RedeliveryErrorHandler.java:476)
>  at 
> org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.schedule(DefaultReactiveExecutor.java:185)
>  at 
> org.apache.camel.impl.engine.DefaultReactiveExecutor.scheduleMain(DefaultReactiveExecutor.java:59)
>  at org.apache.camel.processor.Pipeline.process(Pipeline.java:87)
>  at 
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:228)
>  at 
> org.apache.camel.component.cxf.CxfConsumer$CxfConsumerInvoker.asyncInvoke(CxfConsumer.java:182)
>  at 
> org.apache.camel.component.cxf.CxfConsumer$CxfConsumerInvoker.invoke(CxfConsumer.java:158)
>  at 
> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:59)
>  at 
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
>  at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> {code}
>  



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

[jira] [Updated] (CXF-8183) JDK 9+ Illegal reflective access caused in AutomaticWorkQueueImpl

[Dennis Kieselhorst (Jira)]

 [ 
https://issues.apache.org/jira/browse/CXF-8183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Kieselhorst updated CXF-8183:

Fix Version/s: 3.3.5
   3.4.0

> JDK 9+ Illegal reflective access caused in AutomaticWorkQueueImpl
> -
>
> Key: CXF-8183
> URL: https://issues.apache.org/jira/browse/CXF-8183
> Project: CXF
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 3.3.4
> Environment: OpenJDK 11 inside docker container 
> {{fabric8/java-centos-openjdk11-jre}}
>Reporter: Peter Schulz
>Assignee: Freeman Yue Fang
>Priority: Major
> Fix For: 3.4.0, 3.3.5
>
>
> We use CXF for SOAP with {{cxf-rt-transports-http-hc-3.3.4.jar}}  (Async 
> HTTP) and do get the following warning: 
> {code:none}
> WARNING: Illegal reflective access by 
> org.apache.cxf.common.util.ReflectionUtil$11 
> (file:/Users/peterschulz/.m2/repository/org/apache/cxf/cxf-core/3.3.4/cxf-core-3.3.4.jar)
>  to field java.util.concurrent.ThreadPoolExecutor.mainLock
> WARNING: Please consider reporting this to the maintainers of 
> org.apache.cxf.common.util.ReflectionUtil$11
> WARNING: Use --illegal-access=warn to enable warnings of further illegal 
> reflective access operations
> WARNING: All illegal access operations will be denied in a future 
> release{code}
>  
> {{org.apache.cxf.workqueue.AutomaticWorkQueueImpl}} line 206 and/or 439 
> {code:java}
> Field f = ThreadPoolExecutor.class.getDeclaredField("mainLock");
> ReflectionUtil.setAccessible(f);
> l = (ReentrantLock)f.get(executor);
> /*...*/
> ReflectionUtil.setAccessible(addWorkerMethod).invoke(executor, 
> addWorkerArgs);{code}



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

[jira] [Commented] (CXF-8141) Weblogic12+版本后，@WebResult@WebParam注解失效了

[Dennis Kieselhorst (Jira)]

[ 
https://issues.apache.org/jira/browse/CXF-8141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16970428#comment-16970428
 ] 

Dennis Kieselhorst commented on CXF-8141:
-

Is it possible for you to translate your comment to English? Thanks!

> Weblogic12+版本后，@WebResult@WebParam注解失效了
> ---
>
> Key: CXF-8141
> URL: https://issues.apache.org/jira/browse/CXF-8141
> Project: CXF
>  Issue Type: Bug
>  Components: WS-* Components
>Affects Versions: 2.1.10
>Reporter: huangzhen
>Priority: Major
> Fix For: Invalid
>
> Attachments: image-2019-10-30-17-54-33-283.png, 
> image-2019-10-30-17-58-24-463.png, image-2019-10-30-17-59-39-653.png
>
>
> 我有个项目，使用了webservices来部署服务，部署在tomcat或者weblogic10版本里都是ok的。但是升级到weblogic12以上版本后，webservices接口里设置的参数@WebResult@WebParam注解失效了。



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

[jira] [Commented] (CXF-8100) JAXB Class Not Found Exception on Java >=9 and Tomcat

[Dennis Kieselhorst (Jira)]

[ 
https://issues.apache.org/jira/browse/CXF-8100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16960315#comment-16960315
 ] 

Dennis Kieselhorst commented on CXF-8100:
-

Hi [~mrcrab] can you share a WAR file so that we can deploy it for testing?

Please note that you are using some old dependencies, e.g. jaxb-core is no 
longer valid. You should consistently use the 2.3.2 version and add:

<{color:#80}dependency{color}>
 <{color:#80}groupId{color}>jakarta.xml.bind
 
<{color:#80}artifactId{color}>jakarta.xml.bind-api
 <{color:#80}version{color}>2.3.2


<{color:#80}dependency{color}>
 
<{color:#80}groupId{color}>org.glassfish.jaxb
 
<{color:#80}artifactId{color}>jaxb-runtime
 <{color:#80}version{color}>2.3.2


> JAXB Class Not Found Exception on Java >=9 and Tomcat
> -
>
> Key: CXF-8100
> URL: https://issues.apache.org/jira/browse/CXF-8100
> Project: CXF
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 3.3.3
> Environment: Ubuntu 18.10
> OpenJDK Runtime Environment (build 12.0.1+12)
> Tomcat 9.0.14
>Reporter: Christof R
>Priority: Major
>  Labels: bug
>
> When creating a SOAP Client with JaxWsProxyFactoryBean.create(), JAXB's class 
> loader does not find the context factory (see stack trace at the bottom) and 
> throws a ClassNotFound Exception. This does *not* happen when I run test with 
> Junit, but it happens when I deploy my Apache CXF Application to Tomcat. All 
> the JAXB artifacts (cxf-rt-databinding-jaxb-3.3.0.jar, jaxb-api-2.3.1.jar, 
> jaxb-core-2.3.0.1.jar, jaxb-impl-2.3.2.jar, jaxb-runtime-2.3.1.jar and 
> jaxb-xjc-2.3.2.jar) are in WEB-INF/lib and are therefore available to the web 
> apps class loader.
> The reason why JAXB does not find the class is, according to the stack 
> overflow post [JAXB not available on Tomcat 9 and Java 
> 9/10|https://stackoverflow.com/questions/51518781/jaxb-not-available-on-tomcat-9-and-java-9-10],
>  that JAXB uses the "thread's context class loader". In Tomcat, this class 
> loader is the system class loader, and because Tomcat [builds a class loader 
> hierarchy|https://tomcat.apache.org/tomcat-9.0-doc/class-loader-howto.html], 
> the system class loader does not know about a web app's dependencies. JAXB 
> Implementations were removed from the JRE in Java 9 and now the system class 
> loader does not find them.
> According to the mentioned post, this problem could be solved by refactoring 
> org.apache.cxf.common.jaxb.JAXBContextCache and switching invocations from
>   
> {code:java}
> newInstance( Class[] classesToBeBound, Map properties )
> {code}
> to
> {code:java}
> newInstance( String contextPath, ClassLoader classLoader, Map  
> properties)
> {code}
> , where JAXBContextCache could pass down the correct classLoader.  Another 
> probably "hacky" solution is to wrap all interactions with JAXB in a proper 
> thread (as described in this post: [JAXB Hell on JDK 
> 9|https://sjhannah.com/blog/2018/11/21/jaxb-hell-on-jdk-9/]). 
> Stack trace: 
> {code:java}
> Caused by: org.apache.cxf.service.factory.ServiceConstructionException: null
>   at 
> org.apache.cxf.jaxb.JAXBDataBinding.initialize(JAXBDataBinding.java:355)
>   at 
> org.apache.cxf.service.factory.AbstractServiceFactoryBean.initializeDataBindings(AbstractServiceFactoryBean.java:86)
>   at 
> org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean.buildServiceFromClass(ReflectionServiceFactoryBean.java:470)
>   at 
> org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.buildServiceFromClass(JaxWsServiceFactoryBean.java:693)
>   at 
> org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean.initializeServiceModel(ReflectionServiceFactoryBean.java:530)
>   at 
> org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean.create(ReflectionServiceFactoryBean.java:263)
>   at 
> org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.create(JaxWsServiceFactoryBean.java:199)
>   at 
> org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createEndpoint(AbstractWSDLBasedEndpointFactory.java:103)
>   at 
> org.apache.cxf.frontend.ClientFactoryBean.create(ClientFactoryBean.java:91)
>   at 
> org.apache.cxf.frontend.ClientProxyFactoryBean.create(ClientProxyFactoryBean.java:159)
>   at 
> org.apache.cxf.jaxws.JaxWsProxyFactoryBean.create(JaxWsProxyFactoryBean.java:142)
>   ...
> Caused by: javax.xml.bind.JAXBException: Implementation of JAXB-API has not 
> been found on module path or classpath.
>   at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:232)
>   at javax.xml.bind.ContextFinder.find(ContextFinder.java:375)
>   at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:691)
>   at 
> 

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

[Dennis Kieselhorst (Jira)]

[ 
https://issues.apache.org/jira/browse/CXF-7910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16960314#comment-16960314
 ] 

Dennis Kieselhorst commented on CXF-7910:
-

Thanks, let's wait for the Servicemix release then...

> Change JAX-WS javax to jakarta artifact dependencies
> 
>
> Key: CXF-7910
> URL: https://issues.apache.org/jira/browse/CXF-7910
> Project: CXF
>  Issue Type: Task
>  Components: JAX-WS Runtime
>Reporter: Dennis Kieselhorst
>Priority: Minor
> Fix For: 3.4.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> See https://github.com/eclipse-ee4j/jax-ws-api/issues/46
> According to https://projects.eclipse.org/projects/ee4j.jaxws/ will be 
> released on 2018-12-14.



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

[jira] [Resolved] (CXF-8114) cxf-codegen-plugin generates invalid code for operations with empty parameters

[Dennis Kieselhorst (Jira)]

 [ 
https://issues.apache.org/jira/browse/CXF-8114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Kieselhorst resolved CXF-8114.
-
Resolution: Won't Fix

[~wienczny] resolving this for now. Feel free to reopen with additional 
feedback.

> cxf-codegen-plugin generates invalid code for operations with empty parameters
> --
>
> Key: CXF-8114
> URL: https://issues.apache.org/jira/browse/CXF-8114
> Project: CXF
>  Issue Type: Bug
>Affects Versions: 3.3.3
>Reporter: Stephan Wienczny
>Priority: Major
> Attachments: OneClickForRefund.wsdl
>
>
> We are trying to implement a webservice from a given wsdl. It contains an 
> operation (createRetoureId) that references an empty element 
> (CreateRetoureIdRequest)
> as parameter, e.g. it is an operation without an actual parameter. In the 
> generated code this parameter is mapped to "java.lang.Object":
> {{}}{{@WebMethod}}
> {{@WebResult(name = "CreateRetoureIdResponse", targetNamespace = 
> "http://oneclickforrefund.dpag.de;, partName = "parameters")}}
> {{@Generated(value = "org.apache.cxf.tools.wsdlto.WSDLToJava", date = 
> "2019-09-13T11:24:07.696+02:00")}}
> {{public CreateRetoureIdResponse createRetoureId(}}
> {{ @WebParam(partName = "createRetoureIdRequest", name = 
> "CreateRetoureIdRequest", targetNamespace = 
> "http://oneclickforrefund.dpag.de;)}}
> {{ java.lang.Object createRetoureIdRequest}}
> {{) throws CreateRetoureIdException_Exception;}}
>  
> I did not find a way to pass a valid value to the method when being invoked 
> from Java. Neither "null" nor "new Object()" result in a message being send.
>  
> The wsdl is attached and publicly available at 
> [https://internetmarke.deutschepost.de/OneClickForRefund?wsdl] 
>  



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

[jira] [Commented] (CXF-8114) cxf-codegen-plugin generates invalid code for operations with empty parameters

[Dennis Kieselhorst (Jira)]

[ 
https://issues.apache.org/jira/browse/CXF-8114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16945142#comment-16945142
 ] 

Dennis Kieselhorst commented on CXF-8114:
-

I suppose you don't own the service you are trying to call? If you changed the 
wsdl and remove the message part, it would work.
{code:java}


{code}
instead of
{code:java}

  
  

{code}
Another option is described here 
[https://stackoverflow.com/questions/6134348/wsdl-type-for-getter-without-parameter].
 I think It's more a JAX-WS/ JAXB issue than something specific to CXF.

> cxf-codegen-plugin generates invalid code for operations with empty parameters
> --
>
> Key: CXF-8114
> URL: https://issues.apache.org/jira/browse/CXF-8114
> Project: CXF
>  Issue Type: Bug
>Affects Versions: 3.3.3
>Reporter: Stephan Wienczny
>Priority: Major
> Attachments: OneClickForRefund.wsdl
>
>
> We are trying to implement a webservice from a given wsdl. It contains an 
> operation (createRetoureId) that references an empty element 
> (CreateRetoureIdRequest)
> as parameter, e.g. it is an operation without an actual parameter. In the 
> generated code this parameter is mapped to "java.lang.Object":
> {{}}{{@WebMethod}}
> {{@WebResult(name = "CreateRetoureIdResponse", targetNamespace = 
> "http://oneclickforrefund.dpag.de;, partName = "parameters")}}
> {{@Generated(value = "org.apache.cxf.tools.wsdlto.WSDLToJava", date = 
> "2019-09-13T11:24:07.696+02:00")}}
> {{public CreateRetoureIdResponse createRetoureId(}}
> {{ @WebParam(partName = "createRetoureIdRequest", name = 
> "CreateRetoureIdRequest", targetNamespace = 
> "http://oneclickforrefund.dpag.de;)}}
> {{ java.lang.Object createRetoureIdRequest}}
> {{) throws CreateRetoureIdException_Exception;}}
>  
> I did not find a way to pass a valid value to the method when being invoked 
> from Java. Neither "null" nor "new Object()" result in a message being send.
>  
> The wsdl is attached and publicly available at 
> [https://internetmarke.deutschepost.de/OneClickForRefund?wsdl] 
>  



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

[jira] [Commented] (CXF-7996) Jakarta EE TCKs and compatibility

[Dennis Kieselhorst (Jira)]

[ 
https://issues.apache.org/jira/browse/CXF-7996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16925195#comment-16925195
 ] 

Dennis Kieselhorst commented on CXF-7996:
-

[~reta] have you seen the user guide PDF inside 
[http://download.eclipse.org/ee4j/jakartaee-tck/jakartaee8/promoted/restful-ws-tck-2.1.0.zip]
 - took me some time to find it...

> Jakarta EE TCKs and compatibility
> -
>
> Key: CXF-7996
> URL: https://issues.apache.org/jira/browse/CXF-7996
> Project: CXF
>  Issue Type: Task
>Reporter: Andriy Redko
>Assignee: Andriy Redko
>Priority: Major
>
> Mail thread: 
> https://mail-archives.apache.org/mod_mbox/cxf-dev/201901.mbox/%3C6edd1da6-d651-
> e2a3-8092-59bdc7a54...@apache.org%3E
> Jakarta EE TCK: https://projects.eclipse.org/proposals/eclipse-jakarta-ee-tck
> Github Repo: https://github.com/eclipse-ee4j/jakartaee-tck



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

[jira] [Closed] (CXF-8111) Run Jakarta RESTful Web Services 2.1 TCK

[Dennis Kieselhorst (Jira)]

 [ 
https://issues.apache.org/jira/browse/CXF-8111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Kieselhorst closed CXF-8111.
---

> Run Jakarta RESTful Web Services 2.1 TCK
> 
>
> Key: CXF-8111
> URL: https://issues.apache.org/jira/browse/CXF-8111
> Project: CXF
>  Issue Type: Task
>  Components: JAX-RS
>Reporter: Dennis Kieselhorst
>Priority: Major
>
> We should run the TCK 
> [http://download.eclipse.org/ee4j/jakartaee-tck/jakartaee8/promoted/restful-ws-tck-2.1.0.zip]
>  and ideally have a Jenkins job for it.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

[jira] [Resolved] (CXF-8111) Run Jakarta RESTful Web Services 2.1 TCK

[Dennis Kieselhorst (Jira)]

 [ 
https://issues.apache.org/jira/browse/CXF-8111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Kieselhorst resolved CXF-8111.
-
Resolution: Duplicate

> Run Jakarta RESTful Web Services 2.1 TCK
> 
>
> Key: CXF-8111
> URL: https://issues.apache.org/jira/browse/CXF-8111
> Project: CXF
>  Issue Type: Task
>  Components: JAX-RS
>Reporter: Dennis Kieselhorst
>Priority: Major
>
> We should run the TCK 
> [http://download.eclipse.org/ee4j/jakartaee-tck/jakartaee8/promoted/restful-ws-tck-2.1.0.zip]
>  and ideally have a Jenkins job for it.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

[jira] [Commented] (CXF-8111) Run Jakarta RESTful Web Services 2.1 TCK

[Dennis Kieselhorst (Jira)]

[ 
https://issues.apache.org/jira/browse/CXF-8111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16925194#comment-16925194
 ] 

Dennis Kieselhorst commented on CXF-8111:
-

Sorry, missed that. So closing this as duplicate...

> Run Jakarta RESTful Web Services 2.1 TCK
> 
>
> Key: CXF-8111
> URL: https://issues.apache.org/jira/browse/CXF-8111
> Project: CXF
>  Issue Type: Task
>  Components: JAX-RS
>Reporter: Dennis Kieselhorst
>Priority: Major
>
> We should run the TCK 
> [http://download.eclipse.org/ee4j/jakartaee-tck/jakartaee8/promoted/restful-ws-tck-2.1.0.zip]
>  and ideally have a Jenkins job for it.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

[jira] [Created] (CXF-8111) Run Jakarta RESTful Web Services 2.1 TCK

[Dennis Kieselhorst (Jira)]

Dennis Kieselhorst created CXF-8111:
---

 Summary: Run Jakarta RESTful Web Services 2.1 TCK
 Key: CXF-8111
 URL: https://issues.apache.org/jira/browse/CXF-8111
 Project: CXF
  Issue Type: Task
  Components: JAX-RS
Reporter: Dennis Kieselhorst


We should run the TCK 
[http://download.eclipse.org/ee4j/jakartaee-tck/jakartaee8/promoted/restful-ws-tck-2.1.0.zip]
 and ideally have a Jenkins job for it.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

[jira] [Resolved] (CXF-8110) Update to Jakarta RESTful Web Services API 2.1.6

[Dennis Kieselhorst (Jira)]

 [ 
https://issues.apache.org/jira/browse/CXF-8110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Kieselhorst resolved CXF-8110.
-
Resolution: Fixed

> Update to Jakarta RESTful Web Services API 2.1.6
> 
>
> Key: CXF-8110
> URL: https://issues.apache.org/jira/browse/CXF-8110
> Project: CXF
>  Issue Type: Task
>  Components: JAX-RS
>Reporter: Dennis Kieselhorst
>Assignee: Dennis Kieselhorst
>Priority: Major
> Fix For: 3.4.0
>
>




--
This message was sent by Atlassian Jira
(v8.3.2#803003)

[jira] [Assigned] (CXF-8110) Update to Jakarta RESTful Web Services API 2.1.6

[Dennis Kieselhorst (Jira)]

 [ 
https://issues.apache.org/jira/browse/CXF-8110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Kieselhorst reassigned CXF-8110:
---

Assignee: Dennis Kieselhorst

> Update to Jakarta RESTful Web Services API 2.1.6
> 
>
> Key: CXF-8110
> URL: https://issues.apache.org/jira/browse/CXF-8110
> Project: CXF
>  Issue Type: Task
>  Components: JAX-RS
>Reporter: Dennis Kieselhorst
>Assignee: Dennis Kieselhorst
>Priority: Major
> Fix For: 3.4.0
>
>




--
This message was sent by Atlassian Jira
(v8.3.2#803003)

[jira] [Created] (CXF-8110) Update to Jakarta RESTful Web Services API 2.1.6

[Dennis Kieselhorst (Jira)]

Dennis Kieselhorst created CXF-8110:
---

 Summary: Update to Jakarta RESTful Web Services API 2.1.6
 Key: CXF-8110
 URL: https://issues.apache.org/jira/browse/CXF-8110
 Project: CXF
  Issue Type: Task
  Components: JAX-RS
Reporter: Dennis Kieselhorst
 Fix For: 3.4.0






--
This message was sent by Atlassian Jira
(v8.3.2#803003)

[jira] [Updated] (CXF-7949) Update Servlet dependency to 4.x, Tomcat to 9.x and Jetty to 10.x

[Dennis Kieselhorst (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CXF-7949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Kieselhorst updated CXF-7949:

Summary: Update Servlet dependency to 4.x, Tomcat to 9.x and Jetty to 10.x  
(was: Update Servlet dependency to 4.x and Tomcat to 9.x)

> Update Servlet dependency to 4.x, Tomcat to 9.x and Jetty to 10.x
> -
>
> Key: CXF-7949
> URL: https://issues.apache.org/jira/browse/CXF-7949
> Project: CXF
>  Issue Type: Task
>Reporter: Dennis Kieselhorst
>Priority: Minor
> Fix For: 3.4.0
>
>
> Use Jakarta Servlet release https://github.com/eclipse-ee4j/servlet-api



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[jira] [Resolved] (CXF-7601) Add support for Microprofile OpenAPI implementation (as an alternative to Swagger Core 2.0)

[Dennis Kieselhorst (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CXF-7601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Kieselhorst resolved CXF-7601.
-
Resolution: Fixed

> Add support for Microprofile OpenAPI implementation (as an alternative to 
> Swagger Core 2.0)
> ---
>
> Key: CXF-7601
> URL: https://issues.apache.org/jira/browse/CXF-7601
> Project: CXF
>  Issue Type: Improvement
>Reporter: Dennis Kieselhorst
>Assignee: Dennis Kieselhorst
>Priority: Minor
> Fix For: 3.4.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

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

[Dennis Kieselhorst (JIRA)]

[ 
https://issues.apache.org/jira/browse/CXF-7910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16907596#comment-16907596
 ] 

Dennis Kieselhorst commented on CXF-7910:
-

I've just rebased and updated the branch. Can we resolve the OSGi issues and 
merge this to master?

> Change JAX-WS javax to jakarta artifact dependencies
> 
>
> Key: CXF-7910
> URL: https://issues.apache.org/jira/browse/CXF-7910
> Project: CXF
>  Issue Type: Task
>  Components: JAX-WS Runtime
>Reporter: Dennis Kieselhorst
>Priority: Minor
> Fix For: 3.4.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> See https://github.com/eclipse-ee4j/jax-ws-api/issues/46
> According to https://projects.eclipse.org/projects/ee4j.jaxws/ will be 
> released on 2018-12-14.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[jira] [Commented] (CXF-7601) Add support for Microprofile OpenAPI implementation (as an alternative to Swagger Core 2.0)

[Dennis Kieselhorst (JIRA)]

[ 
https://issues.apache.org/jira/browse/CXF-7601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16838127#comment-16838127
 ] 

Dennis Kieselhorst commented on CXF-7601:
-

Yes, also thought about, would prefer 3.4.0 as it makes more sense to introduce 
new features in those kind of releases but if it would take several months to 
go, I'd merge it to 3.3.x.

> Add support for Microprofile OpenAPI implementation (as an alternative to 
> Swagger Core 2.0)
> ---
>
> Key: CXF-7601
> URL: https://issues.apache.org/jira/browse/CXF-7601
> Project: CXF
>  Issue Type: Improvement
>Reporter: Dennis Kieselhorst
>Assignee: Dennis Kieselhorst
>Priority: Minor
> Fix For: 3.4.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CXF-7601) Add support for Microprofile OpenAPI implementation (as an alternative to Swagger Core 2.0)

[Dennis Kieselhorst (JIRA)]

[ 
https://issues.apache.org/jira/browse/CXF-7601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16838123#comment-16838123
 ] 

Dennis Kieselhorst commented on CXF-7601:
-

I already merged the latest changes from master.

> Add support for Microprofile OpenAPI implementation (as an alternative to 
> Swagger Core 2.0)
> ---
>
> Key: CXF-7601
> URL: https://issues.apache.org/jira/browse/CXF-7601
> Project: CXF
>  Issue Type: Improvement
>Reporter: Dennis Kieselhorst
>Assignee: Dennis Kieselhorst
>Priority: Minor
> Fix For: 3.4.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CXF-7601) Add support for Microprofile OpenAPI implementation (as an alternative to Swagger Core 2.0)

[Dennis Kieselhorst (JIRA)]

[ 
https://issues.apache.org/jira/browse/CXF-7601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16838121#comment-16838121
 ] 

Dennis Kieselhorst commented on CXF-7601:
-

I've just updated the branch to use the 1.0.8 release.

> Add support for Microprofile OpenAPI implementation (as an alternative to 
> Swagger Core 2.0)
> ---
>
> Key: CXF-7601
> URL: https://issues.apache.org/jira/browse/CXF-7601
> Project: CXF
>  Issue Type: Improvement
>Reporter: Dennis Kieselhorst
>Assignee: Dennis Kieselhorst
>Priority: Minor
> Fix For: 3.4.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (CXF-7601) Add support for Microprofile OpenAPI implementation (as an alternative to Swagger Core 2.0)

[Dennis Kieselhorst (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CXF-7601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Kieselhorst updated CXF-7601:

Fix Version/s: 3.4.0

> Add support for Microprofile OpenAPI implementation (as an alternative to 
> Swagger Core 2.0)
> ---
>
> Key: CXF-7601
> URL: https://issues.apache.org/jira/browse/CXF-7601
> Project: CXF
>  Issue Type: Improvement
>Reporter: Dennis Kieselhorst
>Assignee: Dennis Kieselhorst
>Priority: Minor
> Fix For: 3.4.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CXF-7950) Update Johnzon to 1.1.11

[Dennis Kieselhorst (JIRA)]

[ 
https://issues.apache.org/jira/browse/CXF-7950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16830182#comment-16830182
 ] 

Dennis Kieselhorst commented on CXF-7950:
-

[~reta] I noticed you already did it in 
[https://github.com/apache/cxf/tree/CXF-7601_microProfileOpenApi] right?

> Update Johnzon to 1.1.11
> 
>
> Key: CXF-7950
> URL: https://issues.apache.org/jira/browse/CXF-7950
> Project: CXF
>  Issue Type: Task
>Reporter: Dennis Kieselhorst
>Priority: Minor
> Fix For: 3.4.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CXF-7601) Add support for Microprofile OpenAPI implementation (as an alternative to Swagger Core 2.0)

[Dennis Kieselhorst (JIRA)]

[ 
https://issues.apache.org/jira/browse/CXF-7601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16802773#comment-16802773
 ] 

Dennis Kieselhorst commented on CXF-7601:
-

Please go ahead, that's why I've created it :)

> Add support for Microprofile OpenAPI implementation (as an alternative to 
> Swagger Core 2.0)
> ---
>
> Key: CXF-7601
> URL: https://issues.apache.org/jira/browse/CXF-7601
> Project: CXF
>  Issue Type: Improvement
>Reporter: Dennis Kieselhorst
>Assignee: Dennis Kieselhorst
>Priority: Minor
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Dennis Kieselhorst (JIRA)]

[ 
https://issues.apache.org/jira/browse/CXF-7910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16763577#comment-16763577
 ] 

Dennis Kieselhorst commented on CXF-7910:
-

Updated the branch to use the latest saaj-impl servicemix bundle.

Now STSUnitTest fails with:
{noformat}
org.apache.felix.resolver.reason.ReasonException: Unable to resolve root: 
missing requirement [root] osgi.identity; osgi.identity=cxf-sts-service; 
type=karaf.feature; version="[3.3.1.SNAPSHOT,3.3.1.SNAPSHOT]"; 
filter:="(&(osgi.identity=cxf-sts-service)(type=karaf.feature)(version>=3.3.1.SNAPSHOT)(version<=3.3.1.SNAPSHOT))"
 [caused by: Unable to resolve cxf-sts-service/3.3.1.SNAPSHOT: missing 
requirement [cxf-sts-service/3.3.1.SNAPSHOT] osgi.identity; 
osgi.identity=cxf-sts; type=karaf.feature [caused by: Unable to resolve 
cxf-sts/3.3.1.SNAPSHOT: missing requirement [cxf-sts/3.3.1.SNAPSHOT] 
osgi.identity; osgi.identity=cxf-ws-security; type=karaf.feature; 
version="[3.3.1.SNAPSHOT,3.3.1.SNAPSHOT]" [caused by: Unable to resolve 
cxf-ws-security/3.3.1.SNAPSHOT: missing requirement 
[cxf-ws-security/3.3.1.SNAPSHOT] osgi.identity; osgi.identity=cxf-ws-addr; 
type=karaf.feature; version="[3.3.1.SNAPSHOT,3.3.1.SNAPSHOT]" [caused by: 
Unable to resolve cxf-ws-addr/3.3.1.SNAPSHOT: missing requirement 
[cxf-ws-addr/3.3.1.SNAPSHOT] osgi.identity; osgi.identity=cxf-bindings-soap; 
type=karaf.feature; version="[3.3.1.SNAPSHOT,3.3.1.SNAPSHOT]" [caused by: 
Unable to resolve cxf-bindings-soap/3.3.1.SNAPSHOT: missing requirement 
[cxf-bindings-soap/3.3.1.SNAPSHOT] osgi.identity; 
osgi.identity=org.apache.servicemix.bundles.saaj-impl; type=osgi.bundle; 
version="[1.5.1.1,1.5.1.1]"; resolution:=mandatory [caused by: Unable to 
resolve org.apache.servicemix.bundles.saaj-impl/1.5.1.1: missing requirement 
[org.apache.servicemix.bundles.saaj-impl/1.5.1.1] osgi.wiring.package; 
filter:="(&(osgi.wiring.package=javax.activation)(version>=1.2.0)(!(version>=2.0.0)))"]]
    at 
org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1343)
    at org.apache.felix.resolver.ResolverImpl.doResolve(ResolverImpl.java:392)
    at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:378)
    at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:332)
    at 
org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:257)
    at 
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:388)
    at 
org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1025)
    at 
org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$13(FeaturesServiceImpl.java:964)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    at java.lang.Thread.run(Thread.java:748){noformat}
Do we just need to add activation or what does that mean?

> Change JAX-WS javax to jakarta artifact dependencies
> 
>
> Key: CXF-7910
> URL: https://issues.apache.org/jira/browse/CXF-7910
> Project: CXF
>  Issue Type: Task
>  Components: JAX-WS Runtime
>Reporter: Dennis Kieselhorst
>Priority: Minor
> Fix For: 3.4.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> See https://github.com/eclipse-ee4j/jax-ws-api/issues/46
> According to https://projects.eclipse.org/projects/ee4j.jaxws/ will be 
> released on 2018-12-14.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CXF-7601) Add support for Microprofile OpenAPI implementation (as an alternative to Swagger Core 2.0)

[Dennis Kieselhorst (JIRA)]

[ 
https://issues.apache.org/jira/browse/CXF-7601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16763510#comment-16763510
 ] 

Dennis Kieselhorst commented on CXF-7601:
-

Yes, I've just updated the branch.

> Add support for Microprofile OpenAPI implementation (as an alternative to 
> Swagger Core 2.0)
> ---
>
> Key: CXF-7601
> URL: https://issues.apache.org/jira/browse/CXF-7601
> Project: CXF
>  Issue Type: Improvement
>Reporter: Dennis Kieselhorst
>Assignee: Dennis Kieselhorst
>Priority: Minor
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CXF-7834) Using @QueryParam on resource field doesn't work

[Dennis Kieselhorst (JIRA)]

[ 
https://issues.apache.org/jira/browse/CXF-7834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16757204#comment-16757204
 ] 

Dennis Kieselhorst commented on CXF-7834:
-

Hi [~danieldiasjava], you can fork it, take the Weld testcase from Colm 
[https://github.com/apache/cxf/commit/f5c0cc7d46aaf65105eb1014ccfe69e8c69b0edb,]
 add it to the cdi-owb testcases and file a pull request.

> Using @QueryParam on resource field doesn't work
> 
>
> Key: CXF-7834
> URL: https://issues.apache.org/jira/browse/CXF-7834
> Project: CXF
>  Issue Type: Bug
>  Components: JAX-RS
>Affects Versions: 3.1.15
> Environment: TomEE 7.0.5 with CXF 3.1.15
>Reporter: Christian Kaltepoth
>Assignee: Colm O hEigeartaigh
>Priority: Major
> Attachments: cxf-query.tar.gz
>
>
> Hi,
> I'm currently working on the JSR-371 (MVC 1.0) TCK and ran into a weird issue 
> when running it against TomEE 7.0.5 which include CXF 3.1.15.
> For some reason {{@QueryParam}} doesn't work if I place it on a resource 
> field. To be more concrete, in this code the query parameter isn't injected 
> into the field:
> {code:java}
> @Path("inject-test")
> public class InjectParamsController {
> @QueryParam("fieldValue")
> private String fieldValue;
> @GET
> public Response get() {
> // some resource code
> }
> public String getFieldValue() {
> return fieldValue;
> }
> public void setFieldValue(String fieldValue) {
> this.fieldValue = fieldValue;
> }
> }
> {code}
> If I move the annotation to the getter, it is working as expected:
> {code:java}
> @Path("inject-test")
> public class InjectParamsController {
> private String fieldValue;
> @GET
> public Response get() {
> // some resource code
> }
> @QueryParam("fieldValue")
> public String getFieldValue() {
> return fieldValue;
> }
> public void setFieldValue(String fieldValue) {
> this.fieldValue = fieldValue;
> }
> }
> {code}
> Both ways work fine on Glassfish5 and Wildfly.
> It would be great to get your thoughts on this. Something like "Yeah, this is 
> a known bug" or perhaps "You are crazy, this MUST work, you are doing 
> something wrong" :P



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (CXF-7950) Update Johnzon to 1.1.11

[Dennis Kieselhorst (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CXF-7950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Kieselhorst updated CXF-7950:

Fix Version/s: 3.4.0

> Update Johnzon to 1.1.11
> 
>
> Key: CXF-7950
> URL: https://issues.apache.org/jira/browse/CXF-7950
> Project: CXF
>  Issue Type: Task
>Reporter: Dennis Kieselhorst
>Priority: Minor
> Fix For: 3.4.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (CXF-7955) Update HttpComponents client to 4.5.7 and core 4.4.11

[Dennis Kieselhorst (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CXF-7955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Kieselhorst updated CXF-7955:

Summary: Update HttpComponents client to 4.5.7 and core 4.4.11  (was: 
Update HttpComponents client to and core)

> Update HttpComponents client to 4.5.7 and core 4.4.11
> -
>
> Key: CXF-7955
> URL: https://issues.apache.org/jira/browse/CXF-7955
> Project: CXF
>  Issue Type: Task
>Reporter: Dennis Kieselhorst
>Priority: Minor
> Fix For: 3.3.1
>
>
> {code:java}
> 4.5.7
> 4.4.11 causes test failures
> {noformat}
> [ERROR] Tests run: 220, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 
> 39.816 s <<< FAILURE! - in 
> org.apache.cxf.systest.jaxrs.JAXRSClientServerBookTest
> [ERROR] 
> testUriInfoMatchedUrisDecode(org.apache.cxf.systest.jaxrs.JAXRSClientServerBookTest)
>   Time elapsed: 0.052 s  <<< FAILURE!
> java.lang.AssertionError: expected:<200> but was:<404>
>     at 
> org.apache.cxf.systest.jaxrs.JAXRSClientServerBookTest.getAndCompare(JAXRSClientServerBookTest.java:2791)
>     at 
> org.apache.cxf.systest.jaxrs.JAXRSClientServerBookTest.testUriInfoMatchedUrisDecode(JAXRSClientServerBookTest.java:2665)
> [ERROR] 
> testUriInfoMatchedUrisNoDecode(org.apache.cxf.systest.jaxrs.JAXRSClientServerBookTest)
>   Time elapsed: 0.022 s  <<< FAILURE!
> java.lang.AssertionError: expected:<200> but was:<404>
>     at 
> org.apache.cxf.systest.jaxrs.JAXRSClientServerBookTest.getAndCompare(JAXRSClientServerBookTest.java:2791)
>     at 
> org.apache.cxf.systest.jaxrs.JAXRSClientServerBookTest.testUriInfoMatchedUrisNoDecode(JAXRSClientServerBookTest.java:2677)
> [ERROR] 
> testGetBookByURL(org.apache.cxf.systest.jaxrs.JAXRSClientServerBookTest)  
> Time elapsed: 0.02 s  <<< FAILURE!
> java.lang.AssertionError: expected:<200> but was:<404>
>     at 
> org.apache.cxf.systest.jaxrs.JAXRSClientServerBookTest.getAndCompare(JAXRSClientServerBookTest.java:2791)
>     at 
> org.apache.cxf.systest.jaxrs.JAXRSClientServerBookTest.getAndCompareAsStrings(JAXRSClientServerBookTest.java:2769)
>     at 
> org.apache.cxf.systest.jaxrs.JAXRSClientServerBookTest.testGetBookByURL(JAXRSClientServerBookTest.java:1239){noformat}
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CXF-7601) Add support for Microprofile OpenAPI implementation (as an alternative to Swagger Core 2.0)

[Dennis Kieselhorst (JIRA)]

[ 
https://issues.apache.org/jira/browse/CXF-7601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1675#comment-1675
 ] 

Dennis Kieselhorst commented on CXF-7601:
-

I've created a branch 
[https://github.com/apache/cxf/tree/CXF-7601_microProfileOpenApi] with a first 
draft. It's working but you need geronimo-openapi 1.0.5-SNAPSHOT for it as I 
made some fixes there.

[~reta] [~johndament] could you take a look? There is lots of copy/ paste from 
cxf-rt-rs-service-description-openapi-v3 which is already partly copy/ paste 
from cxf-rt-rs-service-description-swagger. The question is, if we want to do a 
more generic approach here? There is also room for more improvement in 
geronimo-openapi (e.g. to reuse OpenAPIEndpoint/ OpenAPIFilter). It's also not 
using latest Microprofile spec yet, created GERONIMO-6682 for that.

> Add support for Microprofile OpenAPI implementation (as an alternative to 
> Swagger Core 2.0)
> ---
>
> Key: CXF-7601
> URL: https://issues.apache.org/jira/browse/CXF-7601
> Project: CXF
>  Issue Type: Improvement
>Reporter: Dennis Kieselhorst
>Assignee: Andriy Redko
>Priority: Minor
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CXF-7950) Update Johnzon to 1.1.11

[Dennis Kieselhorst (JIRA)]

[ 
https://issues.apache.org/jira/browse/CXF-7950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16746255#comment-16746255
 ] 

Dennis Kieselhorst commented on CXF-7950:
-

Setting {color:#80}cxf.johnzon.version {color}to 1.1.11 currently fails 
with:
{noformat}
Message: Unable to resolve root: missing requirement [root] osgi.identity; 
osgi.identity=cxf-jsr-json; type=karaf.feature; version=3.3.0.SNAPSHOT; 
filter:="(&(osgi.identity=cxf-jsr-json)(type=karaf.feature)(version>=3.3.0.SNAPSHOT))"
 [caused by: Unable to resolve cxf-jsr-json/3.3.0.SNAPSHOT: missing requirement 
[cxf-jsr-json/3.3.0.SNAPSHOT] osgi.identity; 
osgi.identity=org.apache.johnzon.core; type=osgi.bundle; 
version="[1.1.11,1.1.11]"; resolution:=mandatory [caused by: Unable to resolve 
org.apache.johnzon.core/1.1.11: missing requirement 
[org.apache.johnzon.core/1.1.11] osgi.extender; 
filter:="(osgi.extender=osgi.serviceloader.registrar)"]]{noformat}

> Update Johnzon to 1.1.11
> 
>
> Key: CXF-7950
> URL: https://issues.apache.org/jira/browse/CXF-7950
> Project: CXF
>  Issue Type: Task
>Reporter: Dennis Kieselhorst
>Priority: Minor
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (CXF-7950) Update Johnzon to 1.1.11

[Dennis Kieselhorst (JIRA)]

Dennis Kieselhorst created CXF-7950:
---

 Summary: Update Johnzon to 1.1.11
 Key: CXF-7950
 URL: https://issues.apache.org/jira/browse/CXF-7950
 Project: CXF
  Issue Type: Task
Reporter: Dennis Kieselhorst






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (CXF-7914) Exception in upgrading cxf-tools-wsdlto-frontend-jaxws jar version from 3.1.* to 3.2.*

[Dennis Kieselhorst (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CXF-7914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Kieselhorst resolved CXF-7914.
-
Resolution: Cannot Reproduce

> Exception in upgrading cxf-tools-wsdlto-frontend-jaxws jar version from 3.1.* 
> to 3.2.*
> --
>
> Key: CXF-7914
> URL: https://issues.apache.org/jira/browse/CXF-7914
> Project: CXF
>  Issue Type: Bug
>  Components: Tooling
>Affects Versions: 3.2.0
>Reporter: Ragul
>Priority: Major
>
> Upgrading cxf from  3.1.16 to 3.2.7 is causing the below expection.
> but Upgarding to minor version 3.1.17 is successfull
> Tried adding common-lang3 depenedency but still the exception persists
> INFO: JDK 8 Platform: Linux
> *StackTrace:*
>  ** soap_server_generate:
>  [echo] Using Apache CXF to generate the WSDL client.
>  [java] Nov 16, 2018 12:48:19 PM org.apache.cxf.staxutils.StaxUtils 
> createXMLInputFactory
>  [java] WARNING: Could not create a secure Stax XMLInputFactory.  Found 
> class com.sun.xml.internal.stream.XMLInputFactoryImpl.  Suggest Woodstox 
> 4.2.0 or newer.
>  [java] Nov 16, 2018 12:48:19 PM org.apache.cxf.staxutils.StaxUtils 
> createXMLInputFactory
>  [java] WARNING: Could not create a secure Stax XMLInputFactory.  Found 
> class com.sun.xml.internal.stream.XMLInputFactoryImpl.  Suggest Woodstox 
> 4.2.0 or newer.
>  [java] Loading FrontEnd jaxws ...
>  [java] Loading DataBinding jaxb ...
>  [java] wsdl2java -xjc-Xfluent-api-ext -xjc-Xfluent-api -d 
> */components/snapshotcollector/target/generated-sources/src/main/java -p 
> com.alcatel.ni.snapshotcollector.commands -wsdlLocation 
> classpath:${wsdl.location} -verbose 
> */components/snapshotcollector/target/generated-sources/src/main/wsee/META-INF/wsdl/snapshotcollector.wsdl
>  [java] wsdl2java - Apache CXF 3.2.7
>  [java]
>  [java] Nov 16, 2018 12:48:20 PM 
> org.apache.cxf.catalog.OASISCatalogManager loadCatalogs
>  [java] WARNING: Catalog found at 
> jar:[file:*/maven/local/repository/org/apache/cxf/cxf-tools-wsdlto-frontend-jaxws/3.2.7/cxf-tools-wsdlto-frontend-jaxws-3.2.7.jar!/META-INF/jax-ws-catalog.xml|file://udir/ragul/maven/local/repository/org/apache/cxf/cxf-tools-wsdlto-frontend-jaxws/3.2.7/cxf-tools-wsdlto-frontend-jaxws-3.2.7.jar!/META-INF/jax-ws-catalog.xml]
>  but no org.apache.xml.resolver.CatalogManager was found.  Check the 
> classpatch for an xmlresolver jar.
>  [java] Exception in thread "main" java.lang.NoClassDefFoundError: 
> org/apache/commons/lang3/StringUtils
>  [java]  at 
> org.apache.cxf.tools.wsdlto.frontend.jaxws.processor.internal.ServiceProcessor.processService(ServiceProcessor.java:253)
>  [java]  at 
> org.apache.cxf.tools.wsdlto.frontend.jaxws.processor.internal.ServiceProcessor.process(ServiceProcessor.java:101)
>  [java]  at 
> org.apache.cxf.tools.wsdlto.frontend.jaxws.processor.WSDLToJavaProcessor.wsdlDefinitionToJavaModel(WSDLToJavaProcessor.java:86)
>  [java]  at 
> org.apache.cxf.tools.wsdlto.frontend.jaxws.processor.WSDLToJavaProcessor.process(WSDLToJavaProcessor.java:60)
>  [java]  at 
> org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.processWsdl(WSDLToJavaContainer.java:282)
>  [java]  at 
> org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:164)
>  [java]  at 
> org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:412)
>  [java]  at 
> org.apache.cxf.tools.common.toolspec.ToolRunner.runTool(ToolRunner.java:105)
>  [java]  at 
> org.apache.cxf.tools.wsdlto.WSDLToJava.run(WSDLToJava.java:113)
>  [java]  at 
> org.apache.cxf.tools.wsdlto.WSDLToJava.run(WSDLToJava.java:86)
>  [java]  at 
> org.apache.cxf.tools.wsdlto.WSDLToJava.main(WSDLToJava.java:185)
>  [java] Caused by: java.lang.ClassNotFoundException: 
> org.apache.commons.lang3.StringUtils
>  [java]  at 
> java.net.URLClassLoader.findClass(URLClassLoader.java:381)
>  [java]  at 
> java.lang.ClassLoader.loadClass(ClassLoader.java:424)
>  [java]  at 
> sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335)
>  [java]  at 
> java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>  [java]  ... 11 more
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CXF-7914) Exception in upgrading cxf-tools-wsdlto-frontend-jaxws jar version from 3.1.* to 3.2.*

[Dennis Kieselhorst (JIRA)]

[ 
https://issues.apache.org/jira/browse/CXF-7914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16745919#comment-16745919
 ] 

Dennis Kieselhorst commented on CXF-7914:
-

No further information received, feel free to reopen with a reproducable sample.

> Exception in upgrading cxf-tools-wsdlto-frontend-jaxws jar version from 3.1.* 
> to 3.2.*
> --
>
> Key: CXF-7914
> URL: https://issues.apache.org/jira/browse/CXF-7914
> Project: CXF
>  Issue Type: Bug
>  Components: Tooling
>Affects Versions: 3.2.0
>Reporter: Ragul
>Priority: Major
>
> Upgrading cxf from  3.1.16 to 3.2.7 is causing the below expection.
> but Upgarding to minor version 3.1.17 is successfull
> Tried adding common-lang3 depenedency but still the exception persists
> INFO: JDK 8 Platform: Linux
> *StackTrace:*
>  ** soap_server_generate:
>  [echo] Using Apache CXF to generate the WSDL client.
>  [java] Nov 16, 2018 12:48:19 PM org.apache.cxf.staxutils.StaxUtils 
> createXMLInputFactory
>  [java] WARNING: Could not create a secure Stax XMLInputFactory.  Found 
> class com.sun.xml.internal.stream.XMLInputFactoryImpl.  Suggest Woodstox 
> 4.2.0 or newer.
>  [java] Nov 16, 2018 12:48:19 PM org.apache.cxf.staxutils.StaxUtils 
> createXMLInputFactory
>  [java] WARNING: Could not create a secure Stax XMLInputFactory.  Found 
> class com.sun.xml.internal.stream.XMLInputFactoryImpl.  Suggest Woodstox 
> 4.2.0 or newer.
>  [java] Loading FrontEnd jaxws ...
>  [java] Loading DataBinding jaxb ...
>  [java] wsdl2java -xjc-Xfluent-api-ext -xjc-Xfluent-api -d 
> */components/snapshotcollector/target/generated-sources/src/main/java -p 
> com.alcatel.ni.snapshotcollector.commands -wsdlLocation 
> classpath:${wsdl.location} -verbose 
> */components/snapshotcollector/target/generated-sources/src/main/wsee/META-INF/wsdl/snapshotcollector.wsdl
>  [java] wsdl2java - Apache CXF 3.2.7
>  [java]
>  [java] Nov 16, 2018 12:48:20 PM 
> org.apache.cxf.catalog.OASISCatalogManager loadCatalogs
>  [java] WARNING: Catalog found at 
> jar:[file:*/maven/local/repository/org/apache/cxf/cxf-tools-wsdlto-frontend-jaxws/3.2.7/cxf-tools-wsdlto-frontend-jaxws-3.2.7.jar!/META-INF/jax-ws-catalog.xml|file://udir/ragul/maven/local/repository/org/apache/cxf/cxf-tools-wsdlto-frontend-jaxws/3.2.7/cxf-tools-wsdlto-frontend-jaxws-3.2.7.jar!/META-INF/jax-ws-catalog.xml]
>  but no org.apache.xml.resolver.CatalogManager was found.  Check the 
> classpatch for an xmlresolver jar.
>  [java] Exception in thread "main" java.lang.NoClassDefFoundError: 
> org/apache/commons/lang3/StringUtils
>  [java]  at 
> org.apache.cxf.tools.wsdlto.frontend.jaxws.processor.internal.ServiceProcessor.processService(ServiceProcessor.java:253)
>  [java]  at 
> org.apache.cxf.tools.wsdlto.frontend.jaxws.processor.internal.ServiceProcessor.process(ServiceProcessor.java:101)
>  [java]  at 
> org.apache.cxf.tools.wsdlto.frontend.jaxws.processor.WSDLToJavaProcessor.wsdlDefinitionToJavaModel(WSDLToJavaProcessor.java:86)
>  [java]  at 
> org.apache.cxf.tools.wsdlto.frontend.jaxws.processor.WSDLToJavaProcessor.process(WSDLToJavaProcessor.java:60)
>  [java]  at 
> org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.processWsdl(WSDLToJavaContainer.java:282)
>  [java]  at 
> org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:164)
>  [java]  at 
> org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:412)
>  [java]  at 
> org.apache.cxf.tools.common.toolspec.ToolRunner.runTool(ToolRunner.java:105)
>  [java]  at 
> org.apache.cxf.tools.wsdlto.WSDLToJava.run(WSDLToJava.java:113)
>  [java]  at 
> org.apache.cxf.tools.wsdlto.WSDLToJava.run(WSDLToJava.java:86)
>  [java]  at 
> org.apache.cxf.tools.wsdlto.WSDLToJava.main(WSDLToJava.java:185)
>  [java] Caused by: java.lang.ClassNotFoundException: 
> org.apache.commons.lang3.StringUtils
>  [java]  at 
> java.net.URLClassLoader.findClass(URLClassLoader.java:381)
>  [java]  at 
> java.lang.ClassLoader.loadClass(ClassLoader.java:424)
>  [java]  at 
> sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335)
>  [java]  at 
> java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>  [java]  ... 11 more
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (CXF-7947) NullPointerException in Utils.java file

[Dennis Kieselhorst (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CXF-7947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Kieselhorst resolved CXF-7947.
-
Resolution: Fixed

> NullPointerException in Utils.java file
> ---
>
> Key: CXF-7947
> URL: https://issues.apache.org/jira/browse/CXF-7947
> Project: CXF
>  Issue Type: Bug
>Reporter: Mahdi Karami
>Assignee: Dennis Kieselhorst
>Priority: Major
> Fix For: 3.3.0, 3.1.18, 3.2.8
>
>
> Hi
> when I used cxf 3.2.5 with  java classes that it's package is null when my 
> run arrive to org.apache.cxf.jaxb.Utils.java class in line number 270 its 
> return NullpointerException beacause my class not have package.
> when I catch this error it's worked. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (CXF-7947) NullPointerException in Utils.java file

[Dennis Kieselhorst (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CXF-7947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Kieselhorst updated CXF-7947:

Fix Version/s: 3.2.8
   3.1.18

> NullPointerException in Utils.java file
> ---
>
> Key: CXF-7947
> URL: https://issues.apache.org/jira/browse/CXF-7947
> Project: CXF
>  Issue Type: Bug
>Reporter: Mahdi Karami
>Assignee: Dennis Kieselhorst
>Priority: Major
> Fix For: 3.3.0, 3.1.18, 3.2.8
>
>
> Hi
> when I used cxf 3.2.5 with  java classes that it's package is null when my 
> run arrive to org.apache.cxf.jaxb.Utils.java class in line number 270 its 
> return NullpointerException beacause my class not have package.
> when I catch this error it's worked. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Dennis Kieselhorst (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CXF-7910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Kieselhorst updated CXF-7910:

Fix Version/s: 3.4.0

> Change JAX-WS javax to jakarta artifact dependencies
> 
>
> Key: CXF-7910
> URL: https://issues.apache.org/jira/browse/CXF-7910
> Project: CXF
>  Issue Type: Task
>  Components: JAX-WS Runtime
>Reporter: Dennis Kieselhorst
>Priority: Minor
> Fix For: 3.4.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> See https://github.com/eclipse-ee4j/jax-ws-api/issues/46
> According to https://projects.eclipse.org/projects/ee4j.jaxws/ will be 
> released on 2018-12-14.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (CXF-7947) NullPointerException in Utils.java file

[Dennis Kieselhorst (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CXF-7947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Kieselhorst updated CXF-7947:

Fix Version/s: 3.3.0

> NullPointerException in Utils.java file
> ---
>
> Key: CXF-7947
> URL: https://issues.apache.org/jira/browse/CXF-7947
> Project: CXF
>  Issue Type: Bug
>Reporter: Mahdi Karami
>Assignee: Dennis Kieselhorst
>Priority: Major
> Fix For: 3.3.0
>
>
> Hi
> when I used cxf 3.2.5 with  java classes that it's package is null when my 
> run arrive to org.apache.cxf.jaxb.Utils.java class in line number 270 its 
> return NullpointerException beacause my class not have package.
> when I catch this error it's worked. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (CXF-7947) NullPointerException in Utils.java file

[Dennis Kieselhorst (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CXF-7947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Kieselhorst reassigned CXF-7947:
---

Assignee: Dennis Kieselhorst

> NullPointerException in Utils.java file
> ---
>
> Key: CXF-7947
> URL: https://issues.apache.org/jira/browse/CXF-7947
> Project: CXF
>  Issue Type: Bug
>Reporter: Mahdi Karami
>Assignee: Dennis Kieselhorst
>Priority: Major
>
> Hi
> when I used cxf 3.2.5 with  java classes that it's package is null when my 
> run arrive to org.apache.cxf.jaxb.Utils.java class in line number 270 its 
> return NullpointerException beacause my class not have package.
> when I catch this error it's worked. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CXF-7947) NullPointerException in Utils.java file

[Dennis Kieselhorst (JIRA)]

[ 
https://issues.apache.org/jira/browse/CXF-7947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16745215#comment-16745215
 ] 

Dennis Kieselhorst commented on CXF-7947:
-

Sounds similar to CXF-7515.

> NullPointerException in Utils.java file
> ---
>
> Key: CXF-7947
> URL: https://issues.apache.org/jira/browse/CXF-7947
> Project: CXF
>  Issue Type: Bug
>Reporter: Mahdi Karami
>Priority: Major
>
> Hi
> when I used cxf 3.2.5 with  java classes that it's package is null when my 
> run arrive to org.apache.cxf.jaxb.Utils.java class in line number 270 its 
> return NullpointerException beacause my class not have package.
> when I catch this error it's worked. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (CXF-7753) Support draft-cavage-http-signatures-09 OOTB

[Dennis Kieselhorst (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CXF-7753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Kieselhorst updated CXF-7753:

Fix Version/s: 3.3.0

> Support draft-cavage-http-signatures-09 OOTB
> 
>
> Key: CXF-7753
> URL: https://issues.apache.org/jira/browse/CXF-7753
> Project: CXF
>  Issue Type: New Feature
>  Components: JAX-RS Security
>Reporter: David J. M. Karlsen
>Priority: Major
>  Labels: security, signature
> Fix For: 3.3.0
>
>
> It would be nice to support http signing signatures:
> https://tools.ietf.org/html/draft-cavage-http-signatures-09
> It will probably increase in popularity as it's part of PSD2 security:
> https://www.stet.eu/assets/files/PSD2/API-DSP2-STET_V1.2.3_final.pdf
> I've found a library which could be used: 
> https://github.com/mbarbero/http-messages-signing
> either making the integration in that library, or providing a cxf component 
> using parts of it for the signing part.
> By doing this validation of incoming requests, as well as signing of outgoing 
> reqs could be handled transparently by either an interceptor, or maybe more 
> vanilla, a JAX-RS filter.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CXF-7856) AbstractFeature must not extend WebServiceFeature

[Dennis Kieselhorst (JIRA)]

[ 
https://issues.apache.org/jira/browse/CXF-7856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16743719#comment-16743719
 ] 

Dennis Kieselhorst commented on CXF-7856:
-

We should definitely solve this. Currently a JAXRS application is not working 
on JDK 11 without adding JAXWS API.

> AbstractFeature must not extend WebServiceFeature
> -
>
> Key: CXF-7856
> URL: https://issues.apache.org/jira/browse/CXF-7856
> Project: CXF
>  Issue Type: Bug
>Reporter: Romain Manni-Bucau
>Priority: Minor
>
> rational being that a cxf feature is not bound to jaxws (it works with jaxrs)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Dennis Kieselhorst (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CXF-7910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Kieselhorst reassigned CXF-7910:
---

Assignee: (was: Dennis Kieselhorst)

> Change JAX-WS javax to jakarta artifact dependencies
> 
>
> Key: CXF-7910
> URL: https://issues.apache.org/jira/browse/CXF-7910
> Project: CXF
>  Issue Type: Task
>  Components: JAX-WS Runtime
>Reporter: Dennis Kieselhorst
>Priority: Minor
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> See https://github.com/eclipse-ee4j/jax-ws-api/issues/46
> According to https://projects.eclipse.org/projects/ee4j.jaxws/ will be 
> released on 2018-12-14.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Dennis Kieselhorst (JIRA)]

[ 
https://issues.apache.org/jira/browse/CXF-7910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16742862#comment-16742862
 ] 

Dennis Kieselhorst commented on CXF-7910:
-

Thank you for testing.

If we postpone it, it should be 3.4.0. In my view it's a major change that 
should not be introduced in a minor release.

> Change JAX-WS javax to jakarta artifact dependencies
> 
>
> Key: CXF-7910
> URL: https://issues.apache.org/jira/browse/CXF-7910
> Project: CXF
>  Issue Type: Task
>  Components: JAX-WS Runtime
>Reporter: Dennis Kieselhorst
>Assignee: Dennis Kieselhorst
>Priority: Minor
> Fix For: 3.3.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> See https://github.com/eclipse-ee4j/jax-ws-api/issues/46
> According to https://projects.eclipse.org/projects/ee4j.jaxws/ will be 
> released on 2018-12-14.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CXF-7907) Change jaxb-api to jakarta.xml.bind-api artifact dependency

[Dennis Kieselhorst (JIRA)]

[ 
https://issues.apache.org/jira/browse/CXF-7907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16742317#comment-16742317
 ] 

Dennis Kieselhorst commented on CXF-7907:
-

Ok, cxf-xjc-utils needs an update too.

> Change jaxb-api to jakarta.xml.bind-api artifact dependency
> ---
>
> Key: CXF-7907
> URL: https://issues.apache.org/jira/browse/CXF-7907
> Project: CXF
>  Issue Type: Task
>Reporter: Dennis Kieselhorst
>Assignee: Freeman Fang
>Priority: Minor
> Fix For: 3.3.0
>
>
> see [https://github.com/eclipse-ee4j/jaxb-api/pull/66]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Dennis Kieselhorst (JIRA)]

[ 
https://issues.apache.org/jira/browse/CXF-7910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16742316#comment-16742316
 ] 

Dennis Kieselhorst commented on CXF-7910:
-

Ok please update once more, I've just merged the latest changes from CXF-7907 
to the branch.

> Change JAX-WS javax to jakarta artifact dependencies
> 
>
> Key: CXF-7910
> URL: https://issues.apache.org/jira/browse/CXF-7910
> Project: CXF
>  Issue Type: Task
>  Components: JAX-WS Runtime
>Reporter: Dennis Kieselhorst
>Assignee: Dennis Kieselhorst
>Priority: Minor
> Fix For: 3.3.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> See https://github.com/eclipse-ee4j/jax-ws-api/issues/46
> According to https://projects.eclipse.org/projects/ee4j.jaxws/ will be 
> released on 2018-12-14.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CXF-7907) Change jaxb-api to jakarta.xml.bind-api artifact dependency

[Dennis Kieselhorst (JIRA)]

[ 
https://issues.apache.org/jira/browse/CXF-7907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16741841#comment-16741841
 ] 

Dennis Kieselhorst commented on CXF-7907:
-

Ok sad, but looks like except for jaxb-core the old com.sun.xml.bind artifacts 
still exist for 2.3.2.

> Change jaxb-api to jakarta.xml.bind-api artifact dependency
> ---
>
> Key: CXF-7907
> URL: https://issues.apache.org/jira/browse/CXF-7907
> Project: CXF
>  Issue Type: Task
>Reporter: Dennis Kieselhorst
>Assignee: Freeman Fang
>Priority: Minor
> Fix For: 3.3.0
>
>
> see [https://github.com/eclipse-ee4j/jaxb-api/pull/66]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Dennis Kieselhorst (JIRA)]

[ 
https://issues.apache.org/jira/browse/CXF-7910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16741836#comment-16741836
 ] 

Dennis Kieselhorst commented on CXF-7910:
-

Ok added the two entries to features.xml, the errors are gone. As I'm not an 
OSGi user, it's hard for me to test it.

Moreover I think some cleanup of the features.xml is possible (as commented in 
CXF-7907). I don't think we need servicemix dependencies when EE4J already 
provide OSGi bundles, do we? So we can possibly remove 
org.apache.servicemix.specs.saaj-api-1.3, geronimo-ws-metadata_2.0_spec, 
org.apache.servicemix.specs.jaxws-api-2.3, ...

> Change JAX-WS javax to jakarta artifact dependencies
> 
>
> Key: CXF-7910
> URL: https://issues.apache.org/jira/browse/CXF-7910
> Project: CXF
>  Issue Type: Task
>  Components: JAX-WS Runtime
>Reporter: Dennis Kieselhorst
>Assignee: Dennis Kieselhorst
>Priority: Minor
> Fix For: 3.3.0
>
>
> See https://github.com/eclipse-ee4j/jax-ws-api/issues/46
> According to https://projects.eclipse.org/projects/ee4j.jaxws/ will be 
> released on 2018-12-14.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Dennis Kieselhorst (JIRA)]

[ 
https://issues.apache.org/jira/browse/CXF-7910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16741830#comment-16741830
 ] 

Dennis Kieselhorst commented on CXF-7910:
-

There is another one: [https://github.com/eclipse-ee4j/jws-api]

That's the one that contains javax.jws.soap.

> Change JAX-WS javax to jakarta artifact dependencies
> 
>
> Key: CXF-7910
> URL: https://issues.apache.org/jira/browse/CXF-7910
> Project: CXF
>  Issue Type: Task
>  Components: JAX-WS Runtime
>Reporter: Dennis Kieselhorst
>Assignee: Dennis Kieselhorst
>Priority: Minor
> Fix For: 3.3.0
>
>
> See https://github.com/eclipse-ee4j/jax-ws-api/issues/46
> According to https://projects.eclipse.org/projects/ee4j.jaxws/ will be 
> released on 2018-12-14.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CXF-7907) Change jaxb-api to jakarta.xml.bind-api artifact dependency

[Dennis Kieselhorst (JIRA)]

[ 
https://issues.apache.org/jira/browse/CXF-7907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16741826#comment-16741826
 ] 

Dennis Kieselhorst commented on CXF-7907:
-

I noticed that features.xml still has

<{color:#80}bundle 
{color}{color:#ff}start-level={color}{color:#008000}"20"{color}>mvn:com.sun.xml.bind/jaxb-impl/${cxf.jaxb.bundle.version}
<{color:#80}bundle 
{color}{color:#ff}start-level={color}{color:#008000}"20"{color}>mvn:com.sun.xml.bind/jaxb-xjc/${cxf.jaxb.bundle.version}
<{color:#80}bundle 
{color}{color:#ff}start-level={color}{color:#008000}"20"{color}>mvn:com.sun.xml.bind/jaxb-core/${cxf.jaxb.bundle.version}

should be changed to org.glassfish.jaxb as well, shouldn't it?

> Change jaxb-api to jakarta.xml.bind-api artifact dependency
> ---
>
> Key: CXF-7907
> URL: https://issues.apache.org/jira/browse/CXF-7907
> Project: CXF
>  Issue Type: Task
>Reporter: Dennis Kieselhorst
>Assignee: Freeman Fang
>Priority: Minor
> Fix For: 3.3.0
>
>
> see [https://github.com/eclipse-ee4j/jaxb-api/pull/66]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Dennis Kieselhorst (JIRA)]

[ 
https://issues.apache.org/jira/browse/CXF-7910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16741778#comment-16741778
 ] 

Dennis Kieselhorst commented on CXF-7910:
-

Well this is already defined as transitive dependency in: 
[http://central.maven.org/maven2/org/apache/servicemix/specs/org.apache.servicemix.specs.jaxws-api-2.3/2.3_1/org.apache.servicemix.specs.jaxws-api-2.3-2.3_1.pom]

Do you mean we should also change it to the Jakarta one? 
[http://central.maven.org/maven2/jakarta/xml/soap/jakarta.xml.soap-api/1.4.1/]

 

> Change JAX-WS javax to jakarta artifact dependencies
> 
>
> Key: CXF-7910
> URL: https://issues.apache.org/jira/browse/CXF-7910
> Project: CXF
>  Issue Type: Task
>  Components: JAX-WS Runtime
>Reporter: Dennis Kieselhorst
>Assignee: Dennis Kieselhorst
>Priority: Minor
> Fix For: 3.3.0
>
>
> See https://github.com/eclipse-ee4j/jax-ws-api/issues/46
> According to https://projects.eclipse.org/projects/ee4j.jaxws/ will be 
> released on 2018-12-14.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Dennis Kieselhorst (JIRA)]

[ 
https://issues.apache.org/jira/browse/CXF-7910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739326#comment-16739326
 ] 

Dennis Kieselhorst commented on CXF-7910:
-

Tried a quick update, however failed with OSGi errors: 
https://github.com/apache/cxf/tree/CXF-7910_jakarta_jaxws-api

> Change JAX-WS javax to jakarta artifact dependencies
> 
>
> Key: CXF-7910
> URL: https://issues.apache.org/jira/browse/CXF-7910
> Project: CXF
>  Issue Type: Task
>  Components: JAX-WS Runtime
>Reporter: Dennis Kieselhorst
>Assignee: Dennis Kieselhorst
>Priority: Minor
> Fix For: 3.3.0
>
>
> See https://github.com/eclipse-ee4j/jax-ws-api/issues/46
> According to https://projects.eclipse.org/projects/ee4j.jaxws/ will be 
> released on 2018-12-14.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Dennis Kieselhorst (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CXF-7910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Kieselhorst reassigned CXF-7910:
---

Assignee: Dennis Kieselhorst

> Change JAX-WS javax to jakarta artifact dependencies
> 
>
> Key: CXF-7910
> URL: https://issues.apache.org/jira/browse/CXF-7910
> Project: CXF
>  Issue Type: Task
>  Components: JAX-WS Runtime
>Reporter: Dennis Kieselhorst
>Assignee: Dennis Kieselhorst
>Priority: Minor
> Fix For: 3.3.0
>
>
> See https://github.com/eclipse-ee4j/jax-ws-api/issues/46
> According to https://projects.eclipse.org/projects/ee4j.jaxws/ will be 
> released on 2018-12-14.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CXF-7907) Change jaxb-api to jakarta.xml.bind-api artifact dependency

[Dennis Kieselhorst (JIRA)]

[ 
https://issues.apache.org/jira/browse/CXF-7907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739299#comment-16739299
 ] 

Dennis Kieselhorst commented on CXF-7907:
-

Yes I think that is the cleanest solution.

> Change jaxb-api to jakarta.xml.bind-api artifact dependency
> ---
>
> Key: CXF-7907
> URL: https://issues.apache.org/jira/browse/CXF-7907
> Project: CXF
>  Issue Type: Task
>Reporter: Dennis Kieselhorst
>Assignee: Freeman Fang
>Priority: Minor
> Fix For: 3.3.0
>
>
> see [https://github.com/eclipse-ee4j/jaxb-api/pull/66]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CXF-7907) Change jaxb-api to jakarta.xml.bind-api artifact dependency

[Dennis Kieselhorst (JIRA)]

[ 
https://issues.apache.org/jira/browse/CXF-7907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739203#comment-16739203
 ] 

Dennis Kieselhorst commented on CXF-7907:
-

Hi [~ffang],

thanks for starting with the changes. I think we are not done yet. Some 
exclusions are necessary to avoid a mixture of the old and the new artifact. 
Moreover I wonder if we need an OSGi bundle for it.

In my view it would also make sense to set cxf.jaxb.version to 2.3.2 and also 
update the impl.

> Change jaxb-api to jakarta.xml.bind-api artifact dependency
> ---
>
> Key: CXF-7907
> URL: https://issues.apache.org/jira/browse/CXF-7907
> Project: CXF
>  Issue Type: Task
>Reporter: Dennis Kieselhorst
>Assignee: Freeman Fang
>Priority: Minor
> Fix For: 3.3.0
>
>
> see [https://github.com/eclipse-ee4j/jaxb-api/pull/66]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (CXF-7907) Change jaxb-api to jakarta.xml.bind-api artifact dependency

[Dennis Kieselhorst (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CXF-7907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Kieselhorst updated CXF-7907:

Fix Version/s: 3.3.0

> Change jaxb-api to jakarta.xml.bind-api artifact dependency
> ---
>
> Key: CXF-7907
> URL: https://issues.apache.org/jira/browse/CXF-7907
> Project: CXF
>  Issue Type: Task
>Reporter: Dennis Kieselhorst
>Assignee: Freeman Fang
>Priority: Minor
> Fix For: 3.3.0
>
>
> see [https://github.com/eclipse-ee4j/jaxb-api/pull/66]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CXF-7907) Change jaxb-api to jakarta.xml.bind-api artifact dependency

[Dennis Kieselhorst (JIRA)]

[ 
https://issues.apache.org/jira/browse/CXF-7907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16738487#comment-16738487
 ] 

Dennis Kieselhorst commented on CXF-7907:
-

Now available on central: 
http://central.maven.org/maven2/jakarta/xml/bind/jakarta.xml.bind-api/2.3.2/

> Change jaxb-api to jakarta.xml.bind-api artifact dependency
> ---
>
> Key: CXF-7907
> URL: https://issues.apache.org/jira/browse/CXF-7907
> Project: CXF
>  Issue Type: Task
>Reporter: Dennis Kieselhorst
>Assignee: Freeman Fang
>Priority: Minor
> Fix For: 3.3.0
>
>
> see [https://github.com/eclipse-ee4j/jaxb-api/pull/66]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)