At line 1 changed 1 line. |
!!JBoss 4.0.2 and AppFuse 1.8+ |
!!AppFuse 1.8+ and JBoss 4.0.2 |
At line 5 changed 1 line. |
(1) First, you need to copy the entire appfuse deployment dir under jboss deploy dir. The default deploy dir in JBoss is something like "/server/default/deploy/". I needed to rename the dir as "appfuse.war" (Notice the .war in the name) so that jboss can detect it and reload it without errors. |
(1) First, you need to copy the entire appfuse deployment dir under jboss deploy dir. The default deploy dir in JBoss is something like "/server/default/deploy/". I needed to rename the dir as "appfuse.war" (Notice the .war in the name) so that jboss can detect it and reload it without errors. You can also simply deploy the WAR to this directory. To enable automatic refreshing of JBoss AS WAR deployments add the following entries to your configuration files. |
At line 7 added 37 lines. |
* Add your JBoss home directory to build.properties: |
{{{jboss.home=D:/JBossAS-4.0.3-SP1/server/default}}} |
|
* Add the following Ant targets to the build.xml in the root of your project: |
{{{ |
<!-- =================================================================== --> |
<!-- The "jboss-undeploy" target deletes the web application archive --> |
<!-- from the JBoss servlet container. --> |
<!-- =================================================================== --> |
<target name="jboss-undeploy" if="jboss.home" |
description="Undeploy '${webapp.name}.war' from JBoss AS"> |
<echo message="Undeploying '${webapp.name}.war' from JBoss AS..."/> |
<delete file="${jboss.home}/deploy/${webapp.war}"/> |
</target> |
|
<!-- =================================================================== --> |
<!-- Refresh - Stops JBoss AS, and refreshes everything --> |
<!-- =================================================================== --> |
<target name="jboss-refresh" depends="jboss-undeploy,clean,jboss-deploy" |
description="Undeploys, cleans, then re-deploys"/> |
|
<!-- =================================================================== --> |
<!-- The "jboss-deploy" target deploys the web application in the war --> |
<!-- format to JBoss AS. --> |
<!-- =================================================================== --> |
<target name="jboss-deploy" depends="package-web" if="jboss.home" |
description="Deploy '${webapp.name}.war' to JBoss AS"> |
<echo message="Deploying '${webapp.name}.war' to JBoss AS..."/> |
<copy file="${webapp.dist}/${webapp.war}" |
todir="${jboss.home}/deploy"/> |
</target> |
}}} |
|
* Run {{ant jboss-refresh}} to refresh your webapp deployment. |
|
%%note __NOTE:__ If you're using AppFuse 1.9+ - you're done! If you'd rather use a JNDI DataSource than the Spring-managed connection pool, you can follow the instructions below. You'll also need to change ''applicationContext-resources.xml'' so the dataSource bean reads from JNDI.%% |
|
At line 36 changed 1 line. |
|
|
At line 45 changed 1 line. |
!!AppFuse Security |
!AppFuse Security |
At line 98 changed 1 line. |
I subclassed UserManagerImpl, and created a version specific to JBoss, then I changed UserManagerImpl to use a stub method called flushAuthCache. |
I subclassed UserManagerImpl, and created a version specific to JBoss, then I changed UserManagerImpl to use a stub method called flushAuthCache. UserManagerJBossSpecific invalidates the user cache using JMX. JBoss is pretty cool! |
At line 100 removed 2 lines. |
UserManagerJBossSpecific invalidates the user cache using JMX. JBoss is pretty cool! |
|
At line 149 added 1 line. |
!Logging |
At line 115 removed 2 lines. |
!!Logging |
|