[weld-issues] [JBoss JIRA] Updated: (WELD-513) TCK Test Failures: IllegalArg Exceptions - Invalid Ejb Jar
Pete Muir (JIRA)
jira-events at lists.jboss.org
Wed May 5 07:38:05 EDT 2010
[ https://jira.jboss.org/jira/browse/WELD-513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pete Muir updated WELD-513:
---------------------------
Component/s: GlassFish Integration
> TCK Test Failures: IllegalArg Exceptions - Invalid Ejb Jar
> ----------------------------------------------------------
>
> Key: WELD-513
> URL: https://jira.jboss.org/jira/browse/WELD-513
> Project: Weld
> Issue Type: Bug
> Components: GlassFish Integration
> Affects Versions: 1.0.1.Final
> Environment: GlassFish 3.0.1
> Reporter: Roger Kitain
>
> Tck test failure:
> TEST NAME: org.jboss.jsr299.tck.tests.deployment.packaging.bundledLibrary.LibraryInEarTest.test
> SERVER LOG:
> [#|2010-04-30T13:01:54.654-0400|SEVERE|glassfish3.0|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=24;_ThreadName=AutoDeployer;|Exception while deploying the app
> java.lang.IllegalArgumentException: Invalid ejb jar [org.jboss.jsr299.tck.tests.deployment.packaging.bundledLibrary.LibraryInEarTest.jar]: it contains zero ejb.
> Note:
> 1. A valid ejb jar requires at least one session, entity (1.x/2.x style), or message-driven bean.
> 2. EJB3+ entity beans (@Entity) are POJOs and please package them as library jar.
> 3. If the jar file contains valid EJBs which are annotated with EJB component level annotations (@Stateless, @Stateful, @MessageDriven, @Singleton), please check server.log to see whether the annotations were processed properly.
> at com.sun.enterprise.deployment.util.EjbBundleValidator.accept(EjbBundleValidator.java:72)
> at com.sun.enterprise.deployment.util.ApplicationValidator.accept(ApplicationValidator.java:124)
> at com.sun.enterprise.deployment.EjbBundleDescriptor.visit(EjbBundleDescriptor.java:722)
> at com.sun.enterprise.deployment.Application.visit(Application.java:1744)
> at com.sun.enterprise.deployment.archivist.ApplicationArchivist.validate(ApplicationArchivist.java:774)
> at com.sun.enterprise.deployment.archivist.ApplicationArchivist.openWith(ApplicationArchivist.java:253)
> at com.sun.enterprise.deployment.archivist.ApplicationFactory.openWith(ApplicationFactory.java:222)
> at org.glassfish.javaee.core.deployment.DolProvider.load(DolProvider.java:152)
> at org.glassfish.javaee.core.deployment.DolProvider.load(DolProvider.java:79)
> at com.sun.enterprise.v3.server.ApplicationLifecycle.loadDeployer(ApplicationLifecycle.java:612)
> at com.sun.enterprise.v3.server.ApplicationLifecycle.setupContainerInfos(ApplicationLifecycle.java:554)
> at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:262)
> at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:183)
> at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:272)
> at com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:310)
> at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:320)
> at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1176)
> at com.sun.enterprise.v3.admin.CommandRunnerImpl.access$900(CommandRunnerImpl.java:83)
> at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1235)
> at org.glassfish.deployment.autodeploy.AutoOperation.run(AutoOperation.java:141)
> at org.glassfish.deployment.autodeploy.AutoDeployer.deploy(AutoDeployer.java:573)
> at org.glassfish.deployment.autodeploy.AutoDeployer.deployAll(AutoDeployer.java:459)
> at org.glassfish.deployment.autodeploy.AutoDeployer.run(AutoDeployer.java:391)
> at org.glassfish.deployment.autodeploy.AutoDeployer.run(AutoDeployer.java:376)
> at org.glassfish.deployment.autodeploy.AutoDeployService$1.run(AutoDeployService.java:195)
> at java.util.TimerThread.mainLoop(Timer.java:512)
> at java.util.TimerThread.run(Timer.java:462)
--
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
More information about the weld-issues
mailing list