IllegalArgumentException:无效的 ejb jar:它包含零个 ejb

IllegalArgumentException: Invalid ejb jar: it contains zero ejb

关于这个问题我似乎有很多问题,但我仍然无法解决它,我知道当有人试图部署一个没有任何 类 注释的 ejb 模块时会抛出这个异常使用@Stateless、@Stateful、@MessageDriven 或@Singleton。但这不是我的情况,我有几个 类 注释如下:

@Stateless
@Remote(TestServiceInterface.class)
public class TestService extends TestSuperclass implements TestServiceInterface<Test>, Serializable{
}

这是界面:

public interface TestServiceInterface<T> extends AnotherInterface<T>{
}

我的所有接口都位于另一个项目中,该项目的 jar 作为库添加到我的 ejb 模块中。

当我尝试部署时出现以下异常:

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:76)
    at com.sun.enterprise.deployment.util.ApplicationValidator.accept(ApplicationValidator.java:128)
    at com.sun.enterprise.deployment.EjbBundleDescriptor.visit(EjbBundleDescriptor.java:730)
    at com.sun.enterprise.deployment.Application.visit(Application.java:1765)
    at com.sun.enterprise.deployment.archivist.ApplicationFactory.openArchive(ApplicationFactory.java:195)
    at org.glassfish.javaee.core.deployment.DolProvider.load(DolProvider.java:185)
    at org.glassfish.javaee.core.deployment.DolProvider.load(DolProvider.java:94)
    at com.sun.enterprise.v3.server.ApplicationLifecycle.loadDeployer(ApplicationLifecycle.java:827)
    at com.sun.enterprise.v3.server.ApplicationLifecycle.setupContainerInfos(ApplicationLifecycle.java:769)
    at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:368)
    at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:240)
    at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:389)
    at com.sun.enterprise.v3.admin.CommandRunnerImpl.execute(CommandRunnerImpl.java:348)
    at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:363)
    at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1085)
    at com.sun.enterprise.v3.admin.CommandRunnerImpl.access00(CommandRunnerImpl.java:95)
    at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1291)
    at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1259)
    at com.sun.enterprise.v3.admin.AdminAdapter.doCommand(AdminAdapter.java:461)
    at com.sun.enterprise.v3.admin.AdminAdapter.service(AdminAdapter.java:212)
    at com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java:179)
    at com.sun.enterprise.v3.server.HK2Dispatcher.dispath(HK2Dispatcher.java:117)
    at com.sun.enterprise.v3.services.impl.ContainerMapper$Hk2DispatcherCallable.call(ContainerMapper.java:354)
    at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:195)
    at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:860)
    at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:757)
    at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1056)
    at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:229)
    at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137)
    at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104)
    at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90)
    at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79)
    at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54)
    at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59)
    at com.sun.grizzly.ContextTask.run(ContextTask.java:71)
    at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532)
    at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513)
    at java.lang.Thread.run(Thread.java:745).

更新:

它还在抛出异常之前打印这一行:

[#|2015-06-25T08:43:22.256-0300|WARNING|glassfish3.1.2|global|_ThreadID=126;_ThreadName=Thread-2;|Error in annotation processing: java.lang.NoClassDefFoundError: com/packageName/TestServiceInterface|#]

更新 2

似乎 netbeans 能够以某种方式部署它!但是,如果我尝试直接在 glassfish 管理页面上或通过命令行 ("asadmin deploy") 进行部署,则会出现异常。

我可能遗漏了什么,如有任何帮助,我们将不胜感激。

似乎由于某种原因,远程 EJB 无法扩展我的 TestSuperclass,所以我不得不删除 extends TestSuperclass

而不是这个:

@Stateless
@Remote(TestServiceInterface.class)
public class TestService extends TestSuperclass implements TestServiceInterface<Test>, Serializable{
}

我这样声明 class:

@Stateless
@Remote(TestServiceInterface.class)
public class TestService implements TestServiceInterface<Test>, Serializable{
}

现在它不再抛出异常了。