[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-4971) Deploying BIRT application to JBoss AS 5.x

[Max Rydahl Andersen (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBIDE-4971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Max Rydahl Andersen updated JBIDE-4971:
---------------------------------------

    Fix Version/s: 3.1.0.GA
         Priority: Blocker  (was: Major)


Marking as blocker for now to make sure we get the proper teams involved if needed.

> Deploying BIRT application to JBoss AS 5.x
> ------------------------------------------
>
>                 Key: JBIDE-4971
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-4971
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: birt, JBossAS
>    Affects Versions: 3.1.0.M3
>            Reporter: Snjezana Peco
>            Assignee: Snjezana Peco
>            Priority: Blocker
>             Fix For: 3.1.0.GA
>
>         Attachments: eap5log1.txt, eap5log2.txt, eap5log3.txt, eap5log4.txt, testbirt-ds.xml, testbirtfiles.zip
>
>
> Steps to reproduce:
> - download testbirt.zip project from https://anonsvn.jboss.org/repos/jbosstools/workspace/snjeza/seam-examples/testbirt.zip (56MB)
> - configure Seam 2.2.0 and a JBoss Runtime
> - deploy to JBoss AS server
> - call the "Test Birt" link 
> JBoss AS 4.2.3
> - works correctly
> JBoss AS 5.1.0 GA
> - doesn't work due to the problem described on http://www.jboss.org/index.html?module=bb&op=viewtopic&t=156898
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira