Due to a class loader issue, the oXygen XML built-in protocol handlers cannot be used in a
scenario where the WebApp shares the same Apache Tomcat instance with another application. To
disable the protocol handlers initialization, set the com.oxygenxml.loadBuiltinProtocolHandlers option to
false.
Also, the following issues need to be considered:
- oXygen reads and sets system properties, and while we try to namespace oXygen-specific
ones, there is no guarantee that there won't be any clashes with those set by other
applications.
- you have to adapt the JVM's memory configuration to the scenario where there will be
more applications competing for the same pool of memory.
- oXygen XML Author WebApp currently does not restart (or reload in Apache
Tomcat terminology) correctly unless the Apache Tomcat server is also restarted.