JBOSS 8 Compability

[rufus_sidford]

We are currently using JBoss EAP 7 JAVA 8 to host an application that uses the SAP Crystal Reports, developer version for Eclipse Runtime libraries. 

We need to upgrade to JBoss EAP 8 JAVA 17 however the latest SP 31 Runtime libraries do not seem to be compatible with it. We are getting JAVA namespace issues. 

Is there an alternative Runtime libraries that uses the modern JAVA namespaces?

The current namespaces are Jakarta EE 8 and JBOSS EAP 8 uses Jakarta EE 10 API namespace

[DonWilliams]

More info from the Product Owner:

Customer may want to consider stay on JBoss 7.x (or use tomcat 9), which is using Jakarta EE 8 namespace.

Newer versions (JBoss 8, Tomcat 10) switched to Jakarta EE 10, which is incompatible with Jakarta EE 8, this is the fundamental problem.

[DonWilliams]

Hello,

I let Product Owner and R&D know about your info and they agreed the version info is incorrect in the PAM so they will change it, it takes time to make the changes due to internal processes but it will be updated...

Also, as you noted in the error you are getting, R&D confirmed the reason it's not working is due to the NameSpace change JBoss/WildFly did.

I've asked them to do the testing for the next release of Eclipse, unfortunately the release schedule for Eclipse is about once a year, typically in January, so for now no option to make this work on newer versions...

Maybe Tomcat is an option for you? I'll check with R&D and see if Tomcat works with this SP. I'm sure it will since SAP BOE/CR Server installs Tomcat as the default WEB server for that product.

Here's a link to CR for Eclipse PAM:

https://www.sap.com/documents/2016/09/ea59ef67-887c-0010-82c7-eda71af511fa.html

[rufus_sidford]

We have been running under JBoss 7 for some years so changing the application to use Tomcat 9 (The versions that still supports the Java EE 8 platform) would be a major rewrite. From my understanding Tomcat 10+ requires a more modern version of the EE naming to work. The CR runtime libraies seem to be the only ones that do not offer a modern version to support the latest app servers.

[DonWilliams]

That is the problem, the SAP BOE Product is the core product that all of the SDK's, Java, .NET, RESTFul are all built off of. So SAP has the same problem you have, because "they" changed the functionality and therefore the backward compatibilities it's the same issue that SAP has with upgrading. BOE is a huge project and not easy when it comes to third parties changing/upgrading to new work flows or API's, platforms, etc.. So like you it would cause SAP to do a major rewrite to support the newer platforrms. And then of course it's a backward compatibility issue for exisitng Customer installs. That's why Product is suggesting to stay on the existing platform, the one that works, for now. There are 1000's if installs that would break if SAP upgraded.... So like you, it's not that easy to upgrade...

FYI - the Platform info has been updated...

[rufus_sidford]

There may be "1000's if installs that would break if SAP upgraded" however another view is that there are 1000's of installs that are unable to move on from legacy application instance because SAP will not provide a modern version of there libraies.

[DonWilliams]

I suggest moving to JBoss 10.

See supported application in CR for Eclipse here:

https://www.sap.com/documents/2016/09/ea59ef67-887c-0010-82c7-eda71af511fa.html

10 seems to be the only one supported along with Java 8.

[rufus_sidford]

There is currently no such thing as JBoss 10.

JBoss 8 is the latest and current version.

I think the documentation is confused and is actually referring to Wildfly 10 - A very old version of wildfly. (Wildfly is sort of the FOSS version of JBOSS )

Currently we are using JBoss 7.4 and that maps to Wildfly 23

We are about to move to JBoss 8.0 and that maps to Wildfly 28

The latest version of Wildfly is 35