[jira] [Created] (OLINGO-1637) Olingo OData2 would not work in Jakarta EE 10 (like Tomcat 10) containers

["Didier Reis (Jira)" <ji...@apache.org>]

Didier Reis created OLINGO-1637:
-----------------------------------

             Summary: Olingo OData2 would not work in Jakarta EE 10 (like Tomcat 10) containers 
                 Key: OLINGO-1637
                 URL: https://issues.apache.org/jira/browse/OLINGO-1637
             Project: Olingo
          Issue Type: Bug
          Components: odata2-core
    Affects Versions: V2 2.0.13
         Environment: Jakarata EE 10 Containers - like Tomcat 10
            Reporter: Didier Reis


Hi all,

 

The issue is that org.apache.olingo olingo-odata2-core 2.0.13
is using some "javax.servlet...", "javax.ws.rs...", ... (EE 8) namespaces
that are incompatible with jakarta (EE 10) containers

 

Environment
Olingo version(s): olingo-odata2-core-2.0.13.jar in EE 10 container (like Tomcat 10)

Possible Solution
Modify you build system to publish a transformed artifact with "jakarta" classifier along with normal artifact.

 

A little more details:

My application migrated to EE 10 was failing to process OData.

I could work around by producing in my local maven repository a transformed
"olingo-odata2-core-2.0.13-jakarta.jar"

 

I did this by adding an extra pom.xml - based on org.eclipse.transformer:transformer-maven-plugin - in my application master pom.xml 

 

Now my other pom.xml modules can consume EE 10 compatible variant by simply adding the dependencies a <classifier>jakarta</classifier>


This fixed my application that can now access process OData again.

 

This work around is however quite cumbersome and requires that the extra transformer pom.xml is tightly coupled with original Olingo source pom.xml it would be much better if this transformation was done once for all ; on publisher side.

Best regards,
Eager consumer.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)