[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-1590) Problem when deploying seam application as directory deployment in glassfish

[Gavin King (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBSEAM-1590?page=all ]

Gavin King closed JBSEAM-1590.
------------------------------

    Resolution: Cannot Reproduce Bug

Better to take this discussion to the user forum.

> Problem when deploying seam application as directory deployment in glassfish
> ----------------------------------------------------------------------------
>
>                 Key: JBSEAM-1590
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-1590
>             Project: JBoss Seam
>          Issue Type: Bug
>    Affects Versions: 2.0.0.BETA1
>         Environment: glassfish V2 build 53
> seam 2.0.0 beta1
> jdk 1.6.0 update1
> netbeans 6 daily build
>            Reporter: ivica c
>             Fix For: 2.0.0.CR1
>
>
> Problem occurs when deploying seam application as directory deployment in glassfish. I am getting this exception:
> Exception occured in J2EEC Phasejava.lang.IllegalArgumentException: Invalid ejb jar [lib/jboss-seam.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. 
> com.sun.enterprise.deployment.backend.IASDeploymentException: Error loading deployment descriptors for module [ctg-main] -- Invalid ejb jar [lib/jboss-seam.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. 
>         at com.sun.enterprise.deployment.backend.Deployer.loadDescriptors(Deployer.java:388)
>         at com.sun.enterprise.deployment.backend.AppDeployerBase.loadDescriptors(AppDeployerBase.java:358)
>         at com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.java:226)
>         at com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppDeployer.java:148)
>         at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:191)
>         at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108)
>         at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:905)
>         at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:279)
>         at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:774)
>         at com.sun.enterprise.management.deploy.DeployThread.deploy(DeployThread.java:187)
>         at com.sun.enterprise.management.deploy.DeployThread.run(DeployThread.java:223)
> Caused by: java.lang.IllegalArgumentException: Invalid ejb jar [lib/jboss-seam.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. 
>         at com.sun.enterprise.deployment.util.EjbBundleValidator.accept(EjbBundleValidator.java:95)
>         at com.sun.enterprise.deployment.util.ApplicationValidator.accept(ApplicationValidator.java:82)
>         at com.sun.enterprise.deployment.EjbBundleDescriptor.visit(EjbBundleDescriptor.java:729)
>         at com.sun.enterprise.deployment.Application.visit(Application.java:1754)
>         at com.sun.enterprise.deployment.archivist.ApplicationArchivist.validate(ApplicationArchivist.java:470)
>         at com.sun.enterprise.deployment.archivist.ApplicationArchivist.openArchive(ApplicationArchivist.java:790)
>         at com.sun.enterprise.deployment.archivist.ApplicationArchivist.openArchive(ApplicationArchivist.java:744)
>         at com.sun.enterprise.deployment.backend.Deployer.loadDescriptors(Deployer.java:349)
>         ... 10 more
> but when I deploy as norma arhive(when upload it) everything works fine.

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