2 Replies Latest reply on Aug 31, 2010 9:48 AM by Nikolaj Brinch Jørgensen

    Groovy 1.7.x and classloading issues

    Nikolaj Brinch Jørgensen Newbie

      Hi,

       

      I'm currently developing services for a customer. I'm using Groovy, but the groovy version in JBoss ESB is rather old (1.5.4). I do not have the lucury to update the ESB, but would like to include my own groovy-all-1.7.4.jar, and set up classloader isolation, for the ESB to use my version of Groovy for my services.

       

      So far I've had no luck, what so ever.

       

      I'm running JBoss ESB 4.7 deployed on JBoss AS 5.1.0.GA.

       

      I've tried including groovy-all-1.7.4.jar in my esb archive (and also tried to use groovy-1.7.4 + asm + antlr), and included a META-INF/jboss-classloading.xml as documentation on the internet describes. But with no luck.

       

      <?xml version="1.0" encoding="UTF-8"?>
      <classloading xmlns="urn:jboss:classloading:1.0" 
           domain="xbrl_servcices.esb" 
           name="xbrl_services.esb" 
           import-all="true" 
           export-all="NON_EMPTY"
           version="0.0.0" 
           parent-first="false" 
           parentDomain="DefaultDomain" />
      

       

      Also my deployment.xml contains:

       

      <loader-repository>
           org.jboss.soa.esb:loader=xbrl_services.esb
           <loader-repository-config>
                java2ParentDelegation=false
           </loader-repository-config>
      </loader-repository>
      
      In case I would like to deploy to ESB 4.x
      Nothing seems to work. The problem is a classcast exception on the antlr CommonToken and Token classes.
      Please advice.
      Thanks,
      NEKO