1 Reply Latest reply on Oct 4, 2007 5:05 PM by Dustin Norlander

    project jar never gets scanned on startup

    Dustin Norlander Apprentice

      I have a large project that I am splitting into too separate ear files. I have modified the build script and config files to build two different ear files (two different build targets). I've almost got it working but I have hit a wall: the main jar file never gets scanned for components.
      that is,
      project.ear
      +project.jar <--never gets scanned
      +project.war

      I know there is some config param I am missing but I can't figure it out.

      I get this:

      13:10:52,858 INFO [EJB3Deployer] Deployed: file:/home/dustin/rhdevstudio/jboss-eap/jboss-as/server/default/deploy/trend.ear/trend.jar/
      


      but it never scans.

      my jboss-app.xml
      <jboss-app>
       <loader-repository>
       seam.jboss.org:loader=trend
       </loader-repository>
      </jboss-app>
      


      my application.xml
      <application xmlns="http://java.sun.com/xml/ns/javaee"
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd"
       version="5">
      
       <display-name>Trend</display-name>
      
       <module>
       <web>
       <web-uri>trend.war</web-uri>
       <context-root>/</context-root>
       </web>
       </module>
      
       <module>
       <ejb>trend.jar</ejb>
       </module>
      
      <!-- Seam and EL -->
       <module>
       <ejb>jboss-seam.jar</ejb>
       </module>
      </application>
      


      Any help is appreciated,
      Dustin