14 Replies Latest reply on Feb 4, 2008 3:57 PM by Scott Stark

    extra jars needed when deploying a Seam app into JBAS5 beta4

    Charles Crouch Expert

      Link to a discussion in the Seam forum:

      http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4125083#4125083

      Any ideas why/how this is occurring and what can be done about it?

      Thanks
      Charles

        • 1. Re: extra jars needed when deploying a Seam app into JBAS5 b
          Ales Justin Master

           

          "charles.crouch@jboss.com" wrote:

          Any ideas why/how this is occurring and what can be done about it?

          Since you need to make Seam be VFS aware.
          And since you're deploying Seam core with your app, you cannot simply put a single jboss-seam-as5.jar into configuration lib, because the VFS impl would then miss the Scanner class.
          Meaning, Seam As5 specific classes would be in parent CL of Seam core CL, and hence not being able to see them

          At the moment we did it that way, but the discussion about it will take place at JBW.

          • 2. Re: extra jars needed when deploying a Seam app into JBAS5 b
            Charles Crouch Expert

             

            "alesj" wrote:
            And since you're deploying Seam core with your app, you cannot simply put a single jboss-seam-as5.jar into configuration lib, because the VFS impl would then miss the Scanner class.

            Ok, from talking to Pete I had the jboss-seam-jbas5.jar in WEB-INF/lib.

            "alesj" wrote:
            At the moment we did it that way, but the discussion about it will take place at JBW.


            So this can't be addressed until JBW? Can we not start the discussion now :-)

            Thanks

            • 3. Re: extra jars needed when deploying a Seam app into JBAS5 b
              Ales Justin Master

               

              "charles.crouch@jboss.com" wrote:

              "alesj" wrote:
              At the moment we did it that way, but the discussion about it will take place at JBW.

              So this can't be addressed until JBW? Can we not start the discussion now :-)

              Sure. If you have some ideas how to make this easier, go ahead.
              But this should be as transparent as possible to Seam code.
              Aka non vendor agnostic.

              • 4. Re: extra jars needed when deploying a Seam app into JBAS5 b
                Pete Muir Master

                Charles, please post or send me and Ales the console log of startup.

                Ales, AFAICS the app is set up correctly and this is another problem. Back to some deployer trying to load all classes and their dependencies - IIRC Scott fixed this for beta3.

                Also, if's a WAR deployment putting the jbas5.jar into WEB-INF/lib is correct. The discussion is about something else (how we do the integration).

                • 5. Re: extra jars needed when deploying a Seam app into JBAS5 b
                  Charles Crouch Expert

                   

                  "pete.muir@jboss.org" wrote:
                  Also, if's a WAR deployment putting the jbas5.jar into WEB-INF/lib is correct.


                  I tried both with and without jboss-seam-jbas5.jar in WEB-INF/lib and got the same error below. FWIW I also upgraded to Seam 2.0.1.GA jars

                  C:\usr\apps\jboss\jboss-5.0.0.r69477\bin>run
                  ===============================================================================
                  
                   JBoss Bootstrap Environment
                  
                   JBOSS_HOME: C:\usr\apps\jboss\jboss-5.0.0.r69477
                  
                   JAVA: C:\Program Files\Java\jdk1.5.0_13\bin\java
                  
                   JAVA_OPTS: -Dprogram.name=run.bat -server -Xms128m -Xmx512m -XX:MaxPermSize=256m -Dsun.rmi.dgc.client.gcInterval=3600000
                  -Dsun.rmi.dgc.server.gcInterval=3600000
                  
                   CLASSPATH: C:\Program Files\Java\jdk1.5.0_13\lib\tools.jar;C:\usr\apps\jboss\jboss-5.0.0.r69477\bin\run.jar
                  
                  ===============================================================================
                  
                  14:38:06,421 INFO [ServerImpl] Starting JBoss (Microcontainer)...
                  14:38:06,421 INFO [ServerImpl] Release ID: JBoss [Morpheus] 5.0.0.Beta4 (build: SVNTag=JBoss_5_0_0_Beta4 date=200801290937)
                  
                  14:38:06,421 INFO [ServerImpl] Home Dir: C:\usr\apps\jboss\jboss-5.0.0.r69477
                  14:38:06,421 INFO [ServerImpl] Home URL: file:/C:/usr/apps/jboss/jboss-5.0.0.r69477/
                  14:38:06,421 INFO [ServerImpl] Library URL: file:/C:/usr/apps/jboss/jboss-5.0.0.r69477/lib/
                  14:38:06,421 INFO [ServerImpl] Patch URL: null
                  14:38:06,421 INFO [ServerImpl] Server Name: default
                  14:38:06,421 INFO [ServerImpl] Server Home Dir: C:\usr\apps\jboss\jboss-5.0.0.r69477\server\default
                  14:38:06,437 INFO [ServerImpl] Server Home URL: file:/C:/usr/apps/jboss/jboss-5.0.0.r69477/server/default/
                  14:38:06,437 INFO [ServerImpl] Server Data Dir: C:\usr\apps\jboss\jboss-5.0.0.r69477\server\default\data
                  14:38:06,437 INFO [ServerImpl] Server Temp Dir: C:\usr\apps\jboss\jboss-5.0.0.r69477\server\default\tmp
                  14:38:06,437 INFO [ServerImpl] Server Config URL: file:/C:/usr/apps/jboss/jboss-5.0.0.r69477/server/default/conf/
                  14:38:06,437 INFO [ServerImpl] Server Library URL: file:/C:/usr/apps/jboss/jboss-5.0.0.r69477/server/default/lib/
                  14:38:06,437 INFO [ServerImpl] Root Deployment Filename: jboss-service.xml
                  14:38:07,468 INFO [ServerImpl] Starting Microcontainer, bootstrapURL=file:/C:/usr/apps/jboss/jboss-5.0.0.r69477/server/defa
                  ult/conf/bootstrap-beans.xml
                  14:38:09,875 INFO [ProfileImpl] Using profile root:C:\usr\apps\jboss\jboss-5.0.0.r69477\server\default
                  14:38:10,828 INFO [ServerInfo] Java version: 1.5.0_13,Sun Microsystems Inc.
                  14:38:10,828 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0_13-b05,Sun Microsystems Inc.
                  14:38:10,828 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
                  14:38:10,968 INFO [JMXKernel] Legacy JMX core initialized
                  14:38:20,921 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083/
                  14:38:22,343 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.
                  14:38:22,343 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer
                  14:38:22,750 INFO [TransactionManagerService] Starting recovery manager
                  14:38:22,890 INFO [TransactionManagerService] Recovery manager started
                  14:38:22,890 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference
                  14:38:36,140 INFO [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production en
                  vironments was not found on the java.library.path: C:\Program Files\Java\jdk1.5.0_13\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:
                  \Program Files\ThinkPad\Utilities;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\ATI Technologies\
                  ATI.ACE\;C:\Program Files\Diskeeper Corporation\Diskeeper\;C:\Program Files\ThinkPad\ConnectUtilities;C:\Program Files\Commo
                  n Files\Lenovo;C:\Program Files\Lenovo\Client Security Solution;C:\Program Files\Java\jdk1.5.0_13\bin;C:\usr\apps\maven\mave
                  n-2.0.7\bin;C:\usr\apps\ant\apache-ant-1.7.0\bin;C:\Program Files\Subversion\bin;
                  14:38:36,453 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0.1-8080
                  14:38:36,453 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-8009
                  14:38:36,453 INFO [Catalina] Initialization processed in 1119 ms
                  14:38:36,453 INFO [StandardService] Starting service jboss.web
                  14:38:36,453 INFO [StandardEngine] Starting Servlet Engine: JBoss Web/2.1.0.CR12
                  14:38:36,578 INFO [Catalina] Server startup in 125 ms
                  14:38:40,656 INFO [AspectDeployer] Deploying xml into org.jboss.aop.AspectManager@451dba for BaseClassLoader@11c7a72{vfsfil
                  e:/C:/usr/apps/jboss/jboss-5.0.0.r69477/server/default/deploy/ejb3-interceptors-aop.xml}
                  14:38:47,500 ERROR [AbstractKernelController] Error installing to PostClassLoader: name=vfsfile:/C:/usr/apps/jboss/jboss-5.0
                  .0.r69477/server/default/deploy/embedded-console.war state=ClassLoader mode=Manual requiredState=PostClassLoader
                  org.jboss.deployers.spi.DeploymentException: Error during deploy: vfsfile:/C:/usr/apps/jboss/jboss-5.0.0.r69477/server/defau
                  lt/deploy/embedded-console.war
                   at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
                   at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:175)
                   at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:853)
                   at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:794)
                   at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327)
                   at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309)
                   at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734)
                   at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862)
                   at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784)
                   at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:622)
                   at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411)
                   at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:498)
                   at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:506)
                   at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:246)
                   at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:131)
                   at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:408)
                   at org.jboss.Main.boot(Main.java:208)
                   at org.jboss.Main$1.run(Main.java:534)
                   at java.lang.Thread.run(Thread.java:595)
                  Caused by: java.lang.NoClassDefFoundError: Lorg/drools/agent/RuleAgent;
                   at java.lang.Class.getDeclaredFields0(Native Method)
                   at java.lang.Class.privateGetDeclaredFields(Class.java:2259)
                   at java.lang.Class.getDeclaredFields(Class.java:1715)
                   at org.jboss.metadata.annotation.creator.AbstractComponentProcessor.processClass(AbstractComponentProcessor.java:252
                  )
                   at org.jboss.metadata.annotation.creator.AbstractComponentProcessor.processClass(AbstractComponentProcessor.java:202
                  )
                   at org.jboss.metadata.annotation.creator.AbstractComponentProcessor.process(AbstractComponentProcessor.java:143)
                   at org.jboss.metadata.annotation.creator.web.WebComponentProcessor.process(WebComponentProcessor.java:60)
                   at org.jboss.metadata.annotation.creator.web.WebComponentProcessor.process(WebComponentProcessor.java:42)
                   at org.jboss.metadata.annotation.creator.web.Web25MetaDataCreator.create(Web25MetaDataCreator.java:68)
                   at org.jboss.deployment.AnnotationMetaDataDeployer.processJBossWebMetaData(AnnotationMetaDataDeployer.java:222)
                   at org.jboss.deployment.AnnotationMetaDataDeployer.deploy(AnnotationMetaDataDeployer.java:171)
                   at org.jboss.deployment.AnnotationMetaDataDeployer.deploy(AnnotationMetaDataDeployer.java:90)
                   at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169)
                   ... 17 more
                  14:38:48,953 INFO [TomcatDeployment] deploy, ctxPath=/invoker, vfsUrl=http-invoker.sar/invoker.war
                  14:38:50,812 INFO [RARDeployment] Required license terms exist, view vfsfile:/C:/usr/apps/jboss/jboss-5.0.0.r69477/server/d
                  efault/deploy/jboss-xa-jdbc.rar/META-INF/ra.xml
                  14:38:50,812 INFO [RARDeployment] Required license terms exist, view vfsfile:/C:/usr/apps/jboss/jboss-5.0.0.r69477/server/d
                  efault/deploy/jboss-local-jdbc.rar/META-INF/ra.xml
                  14:38:50,859 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=Defau
                  ltDS' to JNDI name 'java:DefaultDS'
                  14:38:51,046 WARN [QuartzTimerServiceFactory] sql failed: CREATE TABLE qrtz_job_details(JOB_NAME VARCHAR(80) NOT NULL, JOB_
                  GROUP VARCHAR(80) NOT NULL, DESCRIPTION VARCHAR(120) NULL, JOB_CLASS_NAME VARCHAR(128) NOT NULL, IS_DURABLE VARCHAR(1) NOT N
                  ULL, IS_VOLATILE VARCHAR(1) NOT NULL, IS_STATEFUL VARCHAR(1) NOT NULL, REQUESTS_RECOVERY VARCHAR(1) NOT NULL, JOB_DATA BINAR
                  Y NULL, PRIMARY KEY (JOB_NAME,JOB_GROUP))
                  14:38:51,203 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main
                  14:38:51,234 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
                  14:38:51,250 INFO [JobStoreCMT] Using db table-based data access locking (synchronization).
                  14:38:51,281 INFO [JobStoreCMT] Removed 0 Volatile Trigger(s).
                  14:38:51,281 INFO [JobStoreCMT] Removed 0 Volatile Job(s).
                  14:38:51,281 INFO [JobStoreCMT] JobStoreCMT initialized.
                  14:38:51,281 INFO [StdSchedulerFactory] Quartz scheduler 'JBossEJB3QuartzScheduler' initialized from an externally provided
                   properties instance.
                  14:38:51,281 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
                  14:38:51,281 INFO [JobStoreCMT] Freed 0 triggers from 'acquired' / 'blocked' state.
                  14:38:51,296 INFO [JobStoreCMT] Recovering 0 jobs that were in-progress at the time of the last shut-down.
                  14:38:51,296 INFO [JobStoreCMT] Recovery complete.
                  14:38:51,296 INFO [JobStoreCMT] Removed 0 'complete' triggers.
                  14:38:51,296 INFO [JobStoreCMT] Removed 0 stale fired job entries.
                  14:38:51,296 INFO [QuartzScheduler] Scheduler JBossEJB3QuartzScheduler_$_NON_CLUSTERED started.
                  14:38:51,500 INFO [NativeServerConfig] JBoss Web Services - Native
                  14:38:51,500 INFO [NativeServerConfig] jbossws-native-2.0.3.GA (build=200801241020)
                  14:38:52,937 INFO [TomcatDeployment] deploy, ctxPath=/jbossws, vfsUrl=jbossws.sar/jbossws-context.war
                  14:38:53,140 INFO [RARDeployment] Required license terms exist, view vfsfile:/C:/usr/apps/jboss/jboss-5.0.0.r69477/server/d
                  efault/deploy/jms-ra.rar/META-INF/ra.xml
                  14:38:53,218 INFO [TomcatDeployment] deploy, ctxPath=/jmx-console, vfsUrl=jmx-console.war
                  14:38:54,609 INFO [JMXConnectorServerService] JMX Connector server: service:jmx:rmi://127.0.0.1/jndi/rmi://127.0.0.1:1090/j
                  mxconnector
                  14:38:54,671 INFO [RARDeployment] Required license terms exist, view vfsfile:/C:/usr/apps/jboss/jboss-5.0.0.r69477/server/d
                  efault/deploy/mail-ra.rar/META-INF/ra.xml
                  14:38:54,953 INFO [MailService] Mail Service bound to java:/Mail
                  14:38:55,281 INFO [TomcatDeployment] deploy, ctxPath=/web-console, vfsUrl=management/console-mgr.sar/web-console.war
                  14:38:56,562 WARN [SecurityMetadataStore] WARNING! POTENTIAL SECURITY RISK. It has been detected that the MessageSucker com
                  ponent which sucks messages from one node to another has not had its password changed from the installation default. Please
                  see the JBoss Messaging user guide for instructions on how to do this.
                  14:38:56,953 INFO [ServerPeer] JBoss Messaging 1.4.1.Beta1 server [0] started
                  14:38:57,062 WARN [ConnectionFactoryJNDIMapper] supportsFailover attribute is true on connection factory: jboss.messaging.c
                  onnectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* suppo
                  rt failover
                  14:38:57,062 WARN [ConnectionFactoryJNDIMapper] supportsLoadBalancing attribute is true on connection factory: jboss.messag
                  ing.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not*
                  support load balancing
                  14:38:57,171 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseco
                  nds
                  14:38:57,171 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@220ad8 started
                  14:38:57,171 INFO [QueueService] Queue[/queue/ExpiryQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
                  14:38:57,187 INFO [QueueService] Queue[/queue/DLQ] started, fullSize=200000, pageSize=2000, downCacheSize=2000
                  14:38:57,187 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseco
                  nds
                  14:38:57,187 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@184d88 started
                  14:38:57,187 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseco
                  nds
                  14:38:57,187 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@18806c4 started
                  14:38:57,203 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,nam
                  e=JmsXA' to JNDI name 'java:JmsXA'
                  14:38:57,234 INFO [RARDeployment] Required license terms exist, view vfsfile:/C:/usr/apps/jboss/jboss-5.0.0.r69477/server/d
                  efault/deploy/quartz-ra.rar/META-INF/ra.xml
                  14:38:57,265 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main
                  14:38:57,265 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
                  14:38:57,265 INFO [RAMJobStore] RAMJobStore initialized.
                  14:38:57,265 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in
                   Quartz package: 'quartz.properties'
                  14:38:57,265 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
                  14:38:57,265 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
                  14:38:57,296 INFO [TomcatDeployment] deploy, ctxPath=/, vfsUrl=ROOT.war
                  14:38:57,625 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS
                  FOR DETAILS):
                  
                  *** CONTEXTS IN ERROR: Name -> Error
                  
                  vfsfile:/C:/usr/apps/jboss/jboss-5.0.0.r69477/server/default/deploy/embedded-console.war -> java.lang.NoClassDefFoundError:
                  Lorg/drools/agent/RuleAgent;
                  
                  
                  14:38:57,671 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080
                  14:38:57,703 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
                  14:38:57,718 INFO [ServerImpl] JBoss (Microcontainer) [5.0.0.Beta4 (build: SVNTag=JBoss_5_0_0_Beta4 date=200801290937)] Sta
                  rted in 51s:234ms
                  14:39:01,109 WARN [HDScanner] Failed to process changes
                  org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DET
                  AILS):
                  
                  *** CONTEXTS IN ERROR: Name -> Error
                  
                  vfsfile:/C:/usr/apps/jboss/jboss-5.0.0.r69477/server/default/deploy/embedded-console.war -> java.lang.NoClassDefFoundError:
                  Lorg/drools/agent/RuleAgent;
                  
                  
                   at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:576)
                   at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:559)
                   at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:291)
                   at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:221)
                   at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)
                   at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:280)
                   at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:135)
                   at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:
                  65)
                   at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java
                  :142)
                   at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:166)
                   at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
                   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
                   at java.lang.Thread.run(Thread.java:595)
                  


                  • 6. Re: extra jars needed when deploying a Seam app into JBAS5 b
                    Charles Crouch Expert

                    After talking to Ales and Scott on the JBAS5 call today I think you are right Pete that this is a new problem unrelated to jboss-seam-jbas5.jar.

                    Scott can elaborate but this looks to be a problem related to how we scan for annotations, because there are classes in the jboss-seam-2.0.1.GA.jar that have member variables whose types are from jbpm, drools etc, e.g. org\jboss\seam\pageflow\Pageflow.java has a member variable of type org/jbpm/graph/exe/ProcessInstance.

                    One question which came up was why we're not seeing this issue with other JEE 5 containers, which presumably also scan all deployments for annotations?

                    PS adding all the extra jars to the deployment gets the app deploying fine. Its just extra baggage you shouldn't need.

                    Cheers

                    • 7. Re: extra jars needed when deploying a Seam app into JBAS5 b
                      Tomaz Cerar Master

                      Hi,

                      I have also problem with this. But for me it doesn't find Spring and gwt classes.
                      And to solve this problem I have to include spring.jar and gwt-servler.jar from seam distro.
                      And those two jars make 3MB, and for me this is 3mb of overhead...


                      cheers,
                      tomaz

                      • 8. Re: extra jars needed when deploying a Seam app into JBAS5 b
                        Pete Muir Master

                         

                        "charles.crouch@jboss.com" wrote:
                        One question which came up was why we're not seeing this issue with other JEE 5 containers, which presumably also scan all deployments for annotations?


                        Because it's a bug in the AnnotationMetaDataDeployer ;)

                        • 10. Re: extra jars needed when deploying a Seam app into JBAS5 b
                          Charles Crouch Expert

                          I've put this in the Beta4 bucket and marked it for Scott to make sure this gets triaged ASAP.

                          Dimitris/Scott, any comments?

                          Thanks

                          • 11. Re: extra jars needed when deploying a Seam app into JBAS5 b
                            Scott Stark Master

                            I'm looking at it. Needs a new metadata release.

                            • 12. Re: extra jars needed when deploying a Seam app into JBAS5 b
                              Scott Stark Master

                              Its not the AnnotationMetaDataDeployer as it does not really do the scanning that is causing the problem. It already ignores classes for which it cannot obtain annotations from.

                              The problem is with classes that were loadable in terms of class level annotations, but fail to be processed at the field/method level due to missing class dependencies. I have created a new jboss-metadata.jar snapshot that should ignore these types of errors. Can you try this jar out Charles?
                              https://snapshots.jboss.org/maven2/org/jboss/jboss-metadata/1.0.0-SNAPSHOT/jboss-metadata-1.0.0-20080204.183242-85.jar

                              • 13. Re: extra jars needed when deploying a Seam app into JBAS5 b
                                Charles Crouch Expert

                                I tried the jar attached to the jira and it worked great. No unexpected jars required.

                                Side note: *.jar.bak and *.jar.old files put in \server\default\lib will still be attempted to be deployed. I didnt think this happened in 4.x??

                                Cheers

                                • 14. Re: extra jars needed when deploying a Seam app into JBAS5 b
                                  Scott Stark Master

                                  Ok, I'll release a new version of jboss-metadata.jar then.

                                  Will have check on the backup jar loading.