Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-4971

Deploying BIRT application to JBoss AS 5.x

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Blocker
    • Resolution: Done
    • Affects Version/s: 3.1.0.M3
    • Fix Version/s: 3.3.0.M4
    • Component/s: birt, server
    • Labels:
      None
    • Workaround:
      Workaround Exists
    • Workaround Description:
      Hide

      Remove
      <bean name="SeamMTMatcher" class="org.jboss.seam.integration.microcontainer.deployers.SeamTempModificationTypeMatcher"/>
      from $JBOSS_HOME/server/default/deployers/seam.deployer/META-INF/seam-deployers-jboss-beans.xml

      Show
      Remove <bean name="SeamMTMatcher" class="org.jboss.seam.integration.microcontainer.deployers.SeamTempModificationTypeMatcher"/> from $JBOSS_HOME/server/default/deployers/seam.deployer/META-INF/seam-deployers-jboss-beans.xml

      Description

      Steps to reproduce:

      JBoss AS 4.2.3

      • works correctly

      JBoss AS 5.1.0 GA

      JBoss EAP 5.0
      You will often get warnings (eap5log1.txt)
      When calling the "Test Birt" action, you will get either eap5log2.txt or eap5log3.txt.
      The problem isn't always reproducible. Sometimes it doesn't happen, but rarely.

      The problem happens due to the way in which JBoss AS 5 initializes the application. BIRT uses org.eclipse.birt.report.listener.ViewerServletContextListener to initialize the BIRT engine (OSGi) when starting the application. If this listener is commented/removed, the problem won't happen. If the BIRT engine hasn't been already initialized, it will be initialized when starting a BIRT servlet so that this listener isn't obliged. Maybe this is even better because the BIRT engine is initialized only when it is called. For now, we can use this as a workaround. However, it seems that there is a problem when the JBoss AS server initializes the application.
      Another problem is that JBoss AS aggressively logs a warning about missing classes in BIRT internal jars (WEB-INF/platform/plugins/*.jar) when adding a new *xhtml file to the application. This can be solved by adding a line to <JBOSSAS_HOME/server/default/conf/bootstrap/profile.xml:
      ...
      <bean name="WebVisitorAttributes" class="org.jboss.system.server.profile.basic.IncludeExcludeVisitorAttributes">
      <constructor>
      <parameter>
      <set>
      <value>.war</value>
      </set>
      </parameter>
      <parameter>
      <set>
      <value>WEB-INF/classes</value>
      <value>WEB-INF/lib</value>
      <value>WEB-INF/platform</value> <!-- BIRT workaround -->
      </set>
      </parameter>
      </constructor>
      </bean>
      ...

      The workaround isn't applicable to JBoss AS 5.1.0.GA.

        Gliffy Diagrams

          Attachments

          1. eap5log1.txt
            18 kB
          2. eap5log2.txt
            8 kB
          3. eap5log3.txt
            18 kB
          4. eap5log4.txt
            78 kB
          5. testbirt-ds.xml
            0.5 kB
          6. testbirtfiles.zip
            2 kB

            Activity

              People

              • Assignee:
                maxandersen Max Andersen
                Reporter:
                snjeza Snjezana Peco
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: