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

2019-05-12 Thread Dennis Kieselhorst (JIRA)


[ 
https://issues.apache.org/jira/browse/CXF-7601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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)

2019-05-12 Thread Andriy Redko (JIRA)


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

Andriy Redko commented on CXF-7601:
---

Great, please feel free to get it in when you think it is time. I saw you 
targeted 3.4.0, no issues with that, but may be 3.3.x would be good as well? 
Since this is a new module, no drastic changes ...

> 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)

2019-05-12 Thread Dennis Kieselhorst (JIRA)


[ 
https://issues.apache.org/jira/browse/CXF-7601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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)

2019-05-12 Thread Andriy Redko (JIRA)


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

Andriy Redko commented on CXF-7601:
---

Thanks [~deki], I just saw the artifact on Central as well. Would you rebase it 
against master or I could do that? Thanks!

> 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)

2019-05-12 Thread Dennis Kieselhorst (JIRA)


[ 
https://issues.apache.org/jira/browse/CXF-7601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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)

2019-05-12 Thread 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] [Resolved] (CXF-8039) Dependency javax.xml.ws/jaxws-api should be changed to the jakarta one

2019-05-12 Thread Andriy Redko (JIRA)


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

Andriy Redko resolved CXF-8039.
---
Resolution: Duplicate

Duplicate of https://issues.apache.org/jira/browse/CXF-7910

> Dependency javax.xml.ws/jaxws-api should be changed to the jakarta one
> --
>
> Key: CXF-8039
> URL: https://issues.apache.org/jira/browse/CXF-8039
> Project: CXF
>  Issue Type: Bug
>  Components: JAX-WS Runtime
>Affects Versions: 3.3.1
> Environment: Java 11
>Reporter: Xilai Dai
>Priority: Major
>
> {code}
> 
> javax.xml.ws
> jaxws-api
> 2.3.0
> 
> {code}
> This jaxws-api dependency is defined in some of the pom.xm (e.g 
> parent/pom.xml) for JDK 9 and above.
> But this jaxws-api bundle has wrong package version exported for 
> "javax.xml.ws.*" packages, the expected exported version is 2.3.x, but it 
> exports the version 2.4.0. As consequence there is exception thrown on user 
> bundle for OSGi (karaf) deployment.
> {code}
> missing requirement [my-serrvice/1.0.0] osgi.wiring.package; filter:="(&(osg
> i.wiring.package=javax.xml.ws)(version>=2.4.0)(!(version>=3.0.0)))"]]
> {code}
> The javax.xml.ws api from Jakarta is good enough has the right package 
> version exported for OSGi scenaro.
> {code}
> 
> jakarta.xml.ws
> jakarta.xml.ws-api
> 2.3.2
> 
> {code}
> For JAXB api, the Jakarta one already used for JAVA 9/10/11, so the WS api 
> should be also changed to the Jakarta one.



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


[jira] [Created] (CXF-8039) Dependency javax.xml.ws/jaxws-api should be changed to the jakarta one

2019-05-12 Thread Xilai Dai (JIRA)
Xilai Dai created CXF-8039:
--

 Summary: Dependency javax.xml.ws/jaxws-api should be changed to 
the jakarta one
 Key: CXF-8039
 URL: https://issues.apache.org/jira/browse/CXF-8039
 Project: CXF
  Issue Type: Bug
  Components: JAX-WS Runtime
Affects Versions: 3.3.1
 Environment: Java 11
Reporter: Xilai Dai


{code}

javax.xml.ws
jaxws-api
2.3.0

{code}

This jaxws-api dependency is defined in some of the pom.xm (e.g parent/pom.xml) 
for JDK 9 and above.

But this jaxws-api bundle has wrong package version exported for 
"javax.xml.ws.*" packages, the expected exported version is 2.3.x, but it 
exports the version 2.4.0. As consequence there is exception thrown on user 
bundle for OSGi (karaf) deployment.
{code}
missing requirement [my-serrvice/1.0.0] osgi.wiring.package; filter:="(&(osg
i.wiring.package=javax.xml.ws)(version>=2.4.0)(!(version>=3.0.0)))"]]
{code}

The javax.xml.ws api from Jakarta is good enough has the right package version 
exported for OSGi scenaro.
{code}

jakarta.xml.ws
jakarta.xml.ws-api
2.3.2

{code}

For JAXB api, the Jakarta one already used for JAVA 9/10/11, so the WS api 
should be also changed to the Jakarta one.



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