[
https://issues.apache.org/jira/browse/UNOMI-838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Sinovassin-Naïk updated UNOMI-838:
-------------------------------------------
Description:
This one might be complex.
The version of cxf that we are using is from 2021, we should update it to a
more recent version.
It would allow to use the jakarta.servlet, ws, etc packages instead of javax,
as they are not part of the JAVA EE ecosystem anymore.
It would also allow to upgrade commons-email version
Upgrading CXF can affect transitive dependencies, leading to potential
conflicts.
For instance, Unomi depend on different versions of shared dependencies like
JAXB, JAX-WS, and other Java EE components. We will need to adapt the versions
to find compatible versions which means upgrading to the jakarta packages.
It can be complex to upgrade the Java EE components because the graphQL library
that we are using is using the ols Java EE components and is not compatible
with the jakarta library.
Moreover, the version 3.3.11 of cxf provides some dependencies which have been
removed in the newer versions.
So we will have to include the missing dependencies in Unomi
was:
This one might be complex.
The version of cxf that we are using is from 2021, we should update it to a
more recent version.
It would allow to use the jakarta.servlet, ws, etc packages instead of javax,
as they are not part of the JAVA EE ecosystem anymore.
It would also allow to upgrade commons-email version
> Upgrade CXF, javax.servlet
> --------------------------
>
> Key: UNOMI-838
> URL: https://issues.apache.org/jira/browse/UNOMI-838
> Project: Apache Unomi
> Issue Type: Task
> Reporter: Jonathan Sinovassin-Naïk
> Priority: Major
>
> This one might be complex.
> The version of cxf that we are using is from 2021, we should update it to a
> more recent version.
> It would allow to use the jakarta.servlet, ws, etc packages instead of javax,
> as they are not part of the JAVA EE ecosystem anymore.
> It would also allow to upgrade commons-email version
> Upgrading CXF can affect transitive dependencies, leading to potential
> conflicts.
> For instance, Unomi depend on different versions of shared dependencies like
> JAXB, JAX-WS, and other Java EE components. We will need to adapt the
> versions to find compatible versions which means upgrading to the jakarta
> packages.
> It can be complex to upgrade the Java EE components because the graphQL
> library that we are using is using the ols Java EE components and is not
> compatible with the jakarta library.
> Moreover, the version 3.3.11 of cxf provides some dependencies which have
> been removed in the newer versions.
> So we will have to include the missing dependencies in Unomi
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
