Skip to Main Content

APEX

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Implementing APEX on JBoss -- why not?

ssondereJul 13 2018 — edited Jul 13 2018

I have searched the community and I have searched the documentation -- and I'm more confused for having done so.

First, let me set the stage. I'm an experienced Oracle PL/SQL Developer and have developed using APEX in the past. It's a phenomenal solution and would do some great things for my client. We are trying to put together a Proof of Concept. However, my client has a STRONG preference for JBoss. The client would prefer not to complicate their technology stack and thus may not go with APEX as a solution if it can't be run on JBoss. I hate to walk away from such a great solution because it's going to cause maintenance headaches for my client. I also hate to kludge together a solution that won't really work.

I know that people have configured Oracle APEX on JBoss in the past (for example, this one that I found by searching the forum: http://apexdplsepg.blogspot.com/2011/12/apex-listener-12-with-jboss702.html),. However, I don't know what the impact of doing this would be. Is there a reliability or security risk?

The official Oracle documentation is confusing. For reference, here is a link to (and a paste from) the documentation for Apex 18:

https://docs.oracle.com/database/apex-18.1/HTMIG/choosing-web-listener.htm#HTMIG29322

In this documentation it states:

Oracle REST Data Services (formerly Oracle Application Express Listener) is Java-based, can be installed into any supported J2EE compliant Web Server, and is the preferred option for use with Oracle Application Express. It is a free tool that is fully supported against  Oracle WebLogic Server, Oracle Glassfish Server, and Apache Tomcat. Oracle REST Data Services is part of the reference architecture used to operate the Oracle Database Cloud Service.”

The first statement reads as a very broad declaration of compatibility with all compliant J2EE web servers. "Supported J2EE compliant" in this context could be read as meaning "supporting the J2EE standard."

However, the next statement then lists 3 "supported" servers. If there are really only 3 supported servers, then why in the world would the first sentence ever have been written?

 

So -- why NOT run on JBoss? Why isn't it in the supported list - and what does "supported" mean in this context?

-Scott

Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Aug 10 2018
Added on Jul 13 2018
2 comments
893 views