Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 20 Next »

Spring Boot application is designed to be deployed as traditional war archive. The most important is which version of servlet container is used. Older Servlet containers don’t have support to bootstrap process used in Servlet 3.0 and web.xml must be used (configure it to load an ApplicationContext via a DispatcherServlet).

Basically OpenHub can be deployed to traditional application servers, but some types require specific configuration or modification.

Actually supported servers are:

JBoss AS

WebLogic

WebLogic is supported also out-of-box but there is special trick which is necessary to be used. You must ensure that your servlet initializer directly implements WebApplicationInitializer (even if you extend from a base class that already implements it). But this solves OpenHub via OpenHubApplication.class.

There is known issue on WebLogic 12c with wrong order of filter initialization. Oracle released patches, but it is possible to solve it with inversion order of filter registration.

Cloud

If you’re trying to deploy the application to a Platform-as-a-service, Spring’s vaunted portability buys you a lot of options here. Spring Boot offers perfect support for cloud-based environments. There are not special needs from OpenHub point of view.

EJB support

Actually EJB support is not planned but there is no restriction. Only one think which is necessary is to use web.xml and define metadata-complete to false, see more detail.


  • No labels