AppFuseOnOrion |
|
| Your trail: |
Difference between
version 4
and
version 3:
| At line 80 changed 1 line. |
| !!Modify XML files |
| !!AppFuse Modifications |
| At line 100 added 33 lines. |
| 3. Orion starts Servlets before Listeners, so LoginServlet.init() gets called before StartupListener.contextInitialized(). To fix that problem, you'll need to add code StartupListener.contextInitialized(): |
|
| [{Java2HtmlPlugin |
|
| Map config = (HashMap) ctx.getAttribute(Constants.CONFIG); // "appConfig" |
| if (config == null) { |
| log.info("Creating New Application Context conf Object"); |
| config = new HashMap(); |
| } |
| }] |
| And similarly in LoginServlet.init(): |
|
| [{Java2HtmlPlugin |
|
| Map config = (HashMap) ctx.getAttribute(Constants.CONFIG); // "appConfig" |
| if (config == null) { |
| log.info("Creating New Application Context conf Object"); |
| config = new HashMap(); |
| } |
| }] |
|
| This way it doesnt matter who gets started 1st. The context will be initialized and added to. This works for Tomcat and Orion. |
| 4. Orion doesnt like Matts cool error page trick. Heres how to get around it. |
| * Edit metadata\web\web-security.xml |
| {{{<form-error-page>/security/loginError.jsp</form-error-page>}}} |
| * Create web\security\loginError.jsp containing: |
| {{{<%@ include file="/common/taglibs.jsp"%> |
| <jsp:include page="/security/login.jsp" flush="true"> |
| <jsp:param name="error" value="true"/> |
| </jsp:include> |
| }}} |
| ;:''The latest code in CVS actually uses this strategy as its more portable. ~ [Matt|MattRaible]'' |
|
Back to AppFuseOnOrion,
or to the Page History.
|