Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Through the WSO2 Application Server's runtime environment, you can control class loading per server or application. The default following runtimes that are available with WSO2 AS are sufficient for most users, but you can also define your own runtimes. There are four default run-times available in AS 5.3.0, which are as follows:

  • Tomcat Environment : This is the minimal runtime, which is identical to a pure Tomcat runtime. It only has Tomcat, Servlet, JSP, EL and JSTL available in the server-level classpath. If you want additional JARs, you should package them with the web application or place them in the Tomcat environment's extension directory.
  • Carbon Environment : This consists of both the Tomcat environment and the WSO2 Carbon runtime. It does not provide CXF or Spring dependencies. If you want additional JARs, you should package them with the web application or place them in the WSO2 Carbon environment's extension directory.
  • CXF Environment : This consists of the Tomcat environment, CXF and Spring. It does not provide the WSO2 Carbon runtime. If you want additional JARs, you should package them with the web application or place in the CXF environment's lib directory.
  • Javaee Environment: This consists of the Javaee runtime. 

The subsequent sections explain how to place your external dependencies in a running Carbon server, to configure class loading per application or server.

Table of Contents
maxLevel3
minLevel3

...

Extending the runtime environments

You This section explains how to place your external dependencies in a running server, to configure class loading per application or server. You can share dependencies with a number of applications without packaging them with each and every one of them. To do this, place the common dependencies in the following directories depending on your environment.

...