Raible's Wiki

Raible Designs
Wiki Home
News
Recent Changes

AppFuse

Homepage
  - Korean
  - Chinese
  - Italian
  - Japanese

QuickStart Guide
  - Chinese
  - French
  - German
  - Italian
  - Korean
  - Portuguese
  - Spanish
  - Japanese

User Guide
  - Korean
  - Chinese

Tutorials
  - Chinese
  - German
  - Italian
  - Korean
  - Portuguese
  - Spanish

FAQ
  - Korean

Latest Downloads

Other Applications

Struts Resume
Security Example
Struts Menu

Set your name in
UserPreferences


Referenced by
AppFuseSupport
Articles_cn
Articles_de
Articles_pt
Articles_zh




JSPWiki v2.2.33

[RSS]


Hide Menu

AppFuseOnOrion


Difference between version 12 and version 3:

At line 7 added 4 lines.
For Oracle AS 10g Release 2 (10.1.2.0.2), see [AppFuseOnOracleAS10g].
%%note __NOTE:__ You will have to change the "contextConfigLocation" <context-param> in web.xml (metadata/web/web-settings.xml) to specify each context file individually (comma or space separated). The wildcard syntax (/WEB-INF/applicationContext*.xml) doesn't work on OC4J. More details on the [mailing list|https://appfuse.dev.java.net/servlets/ReadMsg?list=issues&msgNo=414].%%
At line 80 changed 1 line.
!!Modify XML files
!!AppFuse Modifications
At line 104 added 40 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 doesn’t matter who gets started 1st. The context will be initialized and added to. This works for Tomcat and Orion.\\
4. Orion doesn’t like Matt’s cool error page trick. Here’s how to get around it.
* Edit metadata\web\web-security.xml
%%(margin-left: 40px)
{{{<form-error-page>/security/loginError.jsp</form-error-page>}}}%%
* Create web\security\loginError.jsp containing:
%%(margin-left: 40px)
{{{<%@ 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]''
At line 201 added 1 line.
* [The Oracle FAQ|http://www.orafaq.com/]

Back to AppFuseOnOrion, or to the Page History.