Version 17

    HOWTO: Integrate Jakarta Slide

     

    You can do it following this procedure or use the integrated service JBossSlide which features MBean integration and hibernate store implementation.

     

    Goal

    This document should help you get Slide working in JBoss. With the emphasis on should, because frankly I haven't got it working yet. So the actual goal is to help me make it work. (That's why I called it a Work In Progress)

     

    Software Requirements

    • JBoss 3.2.3

    • Jakarta Slide 2.1M1

     

    I assume you've installed JBoss successfully and are ready for the nit and gritty work on Slide.

     

    Installation of Slide

     

    1. Download Slide 2.1M1 server binary

    2. Unpack slide.war in your deploy directory (do not copy the file there)

    3. Remove slide.war/WEB-INF/lib/servlet-2.3.jar because it will interfere with the servlet jars available

    4. Create slide.war/WEB-INF/jboss-web.xml

     

    jboss-web.xml

     

    This file should contain the following:

     
    <?xml version="1.0" encoding="UTF-8"?> 
    <!DOCTYPE jboss-web PUBLIC "-//JBoss//DTD Web Application 2.3//EN" "http://www.jboss.org/j2ee/dtd/jboss-web_3_0.dtd"> 
    
    <jboss-web> 
    
      <class-loading java2ClassLoadingCompliance="false"> 
        <loader-repository>org.apache.slide:loader=slide.war</loader-repository> 
      </class-loading> 
    
      <!-- Resource Environment References --> 
    
      <!-- Resource references --> 
    
      <!-- EJB References --> 
    
    </jboss-web> 
    

     

     

    For the impatient: now you can start up jBoss, and behold Slide works... or doesn't it?

     

    (F)AQ

     

    Authentication doesn't work / I type a random password and get in.

     

    Correct, I haven't modified jboss-web.xml for a security-domain. Since I believe this will be easy to solve I've parked this for later.

     

    I want to use Slide API from another ear/war/jar.

     

    YEAH, me too. Now this is the real issue.

    Entrepreneurs among us will now remove the loader-repository from jboss-web so it's will be loaded into the UCL tree.

     

    Ah slight problem there, because jdom is part of the boot kernel and gets exposed to the deployed components. And since jdom is so high up the hierarchy of class loaders it can't load any other classes needed by Slide.

     

    No problem deploy Slide again in the ear or put lots of jars in the war.

     

    If you've separated stores, no problem. But I've one store. (Note: Slide expects there to be one Domain in the JVM, don't know the impact of having multiple.)

     

     

     

    In short UCL deathtrap. I'm stuck at this point.

     

    Open Issues

     

    • use jboss-web 3.2