5.1.2. Prerequisites

The following topics are covered:

5.1.2.1. Removing all the hard coded portal container name (i.e. "portal")
5.1.2.2. Removing all the hard coded rest context name (i.e. "rest")
5.1.2.3. Removing all the hard coded realm name (i.e. "exo-domain")
5.1.2.4. Making your Http Filters compatible
5.1.2.5. Making your HttpServlets compatible
5.1.2.6. Making your HttpSessionListeners compatible
5.1.2.7. Use init tasks if you need a PortalContainer to initialize an Http Filter or an HttpServlet
5.1.2.8. Making your LoginModules compatible
5.1.2.9. Avoiding static modifier on component dependency
5.1.2.10. Avoid component initialization based on component dependency in the constructor

To be able to migrate an application to GateIn, the first thing we need to do is to ensure that our application supports properly several portal container instances. The following section aims to help you to be compatible with GateIn.