Beépített rewrite rule engine életre keltése
http://mashb.wordpress.com/2010/03/04/creating-a-rewrite-rule-in-jboss/
Tomcat-Native beállítása JBoss alatt
http://community.jboss.org/wiki/UsingJBossWithTomcatNativeAndSSL
context.xml és hatásai JBoss Web Context alatt
Platforms
The table below is a comparison of locations a context.xml can be used in Tomcat and JBossAS. The base directory, CATALINA_HOME, is defined in JBossAS as:
- JBossAS 4.2.3 GA - JBOSS_HOME/server/config/deploy/jboss-web.deployer
- JBossAS 4.3 GA - JBOSS_HOME/server/config/deploy/jboss-web.deployer
- JBossAS 5.0.0 GA - JBOSS_HOME/server/config/deploy/jbossweb.sar
Location |
Tomcat 5.5.x |
JBossAS 4.3 |
Tomcat 6.x |
JBossAS 5.0.0 |
||
|---|---|---|---|---|---|---|
CATALINA_HOME/server.xml (Server/Host/Context) |
- |
+ |
- |
+ |
||
CATALINA_HOME/conf/server.xml (Server/Host/Context) |
+ |
- |
+ |
- |
||
CATALINA_HOME/context.xml |
- |
- |
- |
- |
||
CATALINA_HOME/conf/context.xml |
+ |
- |
+ |
- |
||
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="aad96c0c-83cd-451c-bf72-11ed67f14b22"><ac:plain-text-body><![CDATA[ |
CATALINA_HOME/conf/[Engine]/[Host]/context.xml |
+ |
- |
+ |
- |
]]></ac:plain-text-body></ac:structured-macro> |
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="dbe3ee79-51b2-4bc6-87a1-917f53055580"><ac:plain-text-body><![CDATA[ |
CATALINA_HOME/conf/[Engine]/[Host]/context.xml.default |
+ |
- |
+ |
- |
]]></ac:plain-text-body></ac:structured-macro> |
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="c148c469-6a5f-4904-8970-022db90143ef"><ac:plain-text-body><![CDATA[ |
CATALINA_HOME/conf/[Engine]/[Host]/[ctxPath].xml |
+ |
- |
+ |
- |
]]></ac:plain-text-body></ac:structured-macro> |
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="b216882f-0058-4f8f-858b-0acb006d2e46"><ac:plain-text-body><![CDATA[ |
JBOSS_HOME/server/[config]/conf/[Engine]/[Host]/context.xml |
- |
- |
- |
- |
]]></ac:plain-text-body></ac:structured-macro> |
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="fae7d6f5-a1ef-4b73-b673-3fd5fe488041"><ac:plain-text-body><![CDATA[ |
JBOSS_HOME/server/[config]/conf/[Engine]/[Host]/[ctxPath].xml |
- |
- |
- |
- |
]]></ac:plain-text-body></ac:structured-macro> |
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="f98ba21d-0087-43b0-9875-f91f7ec7285d"><ac:plain-text-body><![CDATA[ |
[deployed-web-app]/META-INF/context.xml |
+ |
- |
+ |
- |
]]></ac:plain-text-body></ac:structured-macro> |
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="efc7bbbd-bf19-4d21-ad45-70e6428741ac"><ac:plain-text-body><![CDATA[ |
[deployed-web-app]/WEB-INF/context.xml |
- |
+ |
- |
+ |
]]></ac:plain-text-body></ac:structured-macro> |
Location Effects
This list explains the effect of each location
[deployed-web-app]/WEB-INF/context.xml - Applies only to the web app
[deployed-web-app]/META-INF/context.xml - Applies only to the web app
CATALINA_HOME/conf/[Engine]/[Host]/context.xml.default - Applies to all web apps deployed on [Host] by default. A context.xml deployed with a web app will over-ride.
CATALINA_HOME/server.xml (Server/Host/Context)- Applies to all web apps deployed on [Host]. Can be overridden by context.xml deployed with web app.
CATALINA_HOME/conf/server.xml (Server/Host/Context) - Applies to all web apps deployed on [Host]. Can be overridden by context.xml deployed with a web app.
CATALINA_HOME/conf/context.xml - Applies to all web apps deployed on [Host]. Can be overridden by context.xml deployed with a web app.
Deploying a custom context in JBossAS
Deploy a custom context by following these points:
- A custom context must extend o.a.catalina.core.StandardContext
- The custom context class must be deployed with a corresponding mbeans-descriptors.xml
The custom context and mbeans-descriptor.xml must be deployed in a JAR to JBOSS_HOME/server/[config]/lib
- The o.a.catalina.startup.ContextConfig must be extended if context configuration needs customization.
- JBossAS 5.0
Edit JBOSS_HOME/server/[config]/deployers/jbossweb.deployer/META-INF/war-deployers-jboss-beans.xml
- Within the element <mbean name="WarDeployer" add the following properties
- Mandatory: <property name="contextMBeanCode">org.your.project.CustomContext<property>
- Optional: <property name"contextConfigMBeanCode">org.your.project.CustomContextConfig<property>
- JBossAS 4.3
Edit JBOSS_HOME/server/[config]/deploy/jboss-web.deployer/META-INF/jboss-service.xml
- Within <mbean code="org.jboss.web.tomcat.service.JBossWeb" name="jboss.web:service=WebServer"
- Add <attribute name="ContextMBeanCode">org.your.project.CustomContext<attribute>
- Prepare a mbeans-descriptors.xml and include it in a jar file along with your custom context class.
Deploy the jar file in JBOSS_HOME/server/[config]/lib