Versions Compared

Key

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

Web components packaged in Web Application Archives (WAR) can be deployed in WSO2 AS as web applications. This includes any generic web application, JAX-RS/JAX-WS application or Spring application that is packaged into WAR files. For more information on WAR files, please refer to http://ant.apache.org/manual/Tasks/war.html.

Tip

Note that it is not allowed to have Web applications named 't.war'.

The following topics explains these different types of web applications deployable in AS, and how they should be developed for WSO2 AS:

...

  • Only the following subset of the spring packages (Spring Framework version 3.1.0) are delivered with AS:
  • org.springframework.ws spring-xml (version : 2.0.3.RELEASE)
  • org.springframework spring-core (version : 3.1.0)
  • org.springframework spring-beans (version : 3.1.0)
  • org.springframework spring-context (version : 3.1.0)
  • org.springframework spring-web (version : 3.1.0)

  • If the Application application needs any other spring packages, then those they need to be deployed with the application itself.
  • Projects which that are built with Spring 2.5 or higher versions will be backward compatible with delivered version of Spring Framework. However, it is recommended to build your application with Spring 3.1.0 before deployment.
  • If the Application application is based on a higher version of the Spring framework, then that version needs to be deployed with the application. The framework which is deployed with the application will be given the priority in the run time.

...

  • The following sub packages of Spring 3.0.7 are shipped with the Application Server CXF environment. 
  • spring-aop
  • spring-asm
  • spring-beans
  • spring-context
  • spring-core
  • spring-expression
  • spring-web

  • If the user wants to upgrade the Spring versions, one of the following actions can be carried out: 
  • Remove existing Spring JARs from from the <product_home>/lib/runtimes/cxf directory and replace them with the new JARs.
  • Include the required JARs inside the WEB-INF/lib directory of the application and deploy it in the Tomcat runtime environment.

If you want to configure use more advanced configurations for your web application by , such as enabling Single Sign On (SSO), enabling fine grained authorization using XACML, enabling SaaS mode or CORS see the topic on Configuring Applications for AS; see the Working with Applications topic for instructions.