has anybody deploy CAS 3.4 on JBoss5 successfully ?

[MiNG Jason]

recently, i'm struggling for deploying jasig CAS 3.4.2 on JBoss 5.1.0 GA.

however, i can't deploy it successfully on JBoss5, the main reason is some jar libraries in war file conflict to the libraries in %JBOSS_HOME%\common\lib.

i tried to put a jboss-classloading.xml file in WEB-INF, make the class loader of the war file isolated, but still not working, the log4j will stop working after loading the log4j.xml.

if i remove the jboss-classloading.xml file from WEB-INF, the classess will conflict and cannot deploy.

if anybody has the same problem like me and you have already solved it, please tell me how to do, i really have no idea about this.

appreciate for your helping.

[Ales Justin]

.war should already do child-first lookup, so most of those libs/classes should be your local ones.

The logging is always a pita, so I would suggest you try diff approach:

* http://community.jboss.org/wiki/Logging

AS6 has new better logging layer, which allows you more control.

* http://community.jboss.org/message/521813 (and search for similar)

[MiNG Jason]

I do appreciate your suggestion.

I'll try that.

thanks again.

[Steve Dodge]

I just now successfully deployed CAS 3.4.2  in Jboss6-m4  Should be similar for Jboss5.1.x.  Several things:

1. add a jboss-scanning.xml

{code:xml}<scanning xmlns="urn:jboss:scanning:1.0">

  <path name="WEB-INF/classes">
  </path>

  <path name="WEB-INF/lib/jdom-1.0.jar">
     <include name="org.jdom" />
  </path>

</scanning>{code}

This is to avoid a continual StringIndexOutOfBoundsException when the scanner comes accross the jdom.jar file and scans a class in the root package.

2. Use  maven's pom war overlay feature and do an overlay of your own version of web.xml..  just take a copy of the existing web.xml and remove all references to Log4j and Log4Configurator.

3. Remove from WEB-INF/lib all log4j, slf4j, xml-apis, hibernate-jpa.  These will cause numerous errors as they conflict with jboss provided classes and Jboss provided logging.

4. Also I simply deleted the WEB-INF/class/META-INF/persistence.xml as it was causing jboss to complain about compliance.  You might need this if you are features of cas that are persisted.  Also you may be able to just ignore presistence.xml using the jboss-ignores.txt here http://community.jboss.org/wiki/JBoss5custommetadatafiles, I din't try the ignores approach.

[MiNG Jason]

Thanks for your answer~~~

I'll try that ^_^