0 Replies Latest reply on Dec 4, 2013 7:10 PM by Eric OX

    JBoss library conflit issue

    Eric OX Newbie

      I try to integrate jasper report into my current web application. The current web application config is as below:

      JBoss 4.0.3, EJB 1.1, struts 1.1

       

      As I can't upgrade the current web app's library, I can't integrate jasper report lib into the current library (commons-digester and common-beanutils can't support jasper report lib). Therefore, I need to add another web app for it. I used the the same structure of current web app and upgrade some libraries (commons-digester and common-beanutils). I tested in the following situation:

       

      Case 1. deploy new web app only

      Result => can generate report

       

      Case 2. deploy both new and current web app

      Result => After triggering report generation, it show the exception as below

      java.lang.NoSuchFieldError: PRINTSCALING

      at net.sf.jasperreports.engine.export.JRPdfExporter.exportReportToStream(JRPdfExporter.java:466)

      at net.sf.jasperreports.engine.export.JRPdfExporter.exportReport(JRPdfExporter.java:362)

      at net.sf.jasperreports.engine.JasperExportManager.exportReportToPdfStream(JasperExportManager.java:163)

      at com.qcom.qsm.ReportGeneratorBean.generate(ReportGeneratorBean.java:27)

      at com.qcom.qsm.TestAction.perform(TestAction.java:56)

      at org.apache.struts.action.Action.execute(Action.java:420)

       

      Case 3. I try to use JBoss's isolated method adding jboss-app.xml into the ear file to isolate 2 web app.

      It show the exception when deploying the new web app

      org.jboss.deployment.DeploymentException: Error during deploy; - nested throwable: (javax.naming.NameNotFoundException: comp not bound)

      at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:366)

      at org.jboss.web.WebModule.startModule(WebModule.java:68)

      at org.jboss.web.WebModule.startService(WebModule.java:46)

      at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:274)

      at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:230)

      at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)

      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

      at java.lang.reflect.Method.invoke(Method.java:597)

      at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)

      at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)

      at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)

      at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245)

      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)

      at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:943)

      at $Proxy0.start(Unknown Source)

       

      Do brothers having any idea about the isolation problem and the jasper report generation exception?