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

Java IllegalArgumentException:无效的ejb jar:它包含零个ejb,java,jakarta-ee,ejb,ejb-3.0,glassfish-3,Java,Jakarta Ee,Ejb,Ejb 3.0,Glassfish 3,关于这个问题,我似乎有很多问题,但我仍然无法解决。我知道,当一个人试图部署ejb模块时,如果没有任何带有@Stateless、@Stateful、@MessageDriven或@Singleton注释的类,就会引发这个异常。但这不是我的情况,我有几个类注释如下: @Stateless @Remote(TestServiceInterface.class) public class TestService extends TestSuperclass implements TestServiceI

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

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

它还会在引发异常之前打印这一行:

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$1.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.access$1200(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{
}
@无状态
@远程(TestServiceInterface.class)
公共类TestService扩展TestSuperclass实现TestServiceInterface,可序列化{
}
我这样评价这个班:

@Stateless
@Remote(TestServiceInterface.class)
public class TestService extends TestSuperclass implements TestServiceInterface<Test>, Serializable{
}
@Stateless
@Remote(TestServiceInterface.class)
public class TestService implements TestServiceInterface<Test>, Serializable{
}
@无状态
@远程(TestServiceInterface.class)
公共类TestService实现TestServiceInterface,可序列化{
}

现在它不再抛出异常了。

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

与此相反:

@Stateless
@Remote(TestServiceInterface.class)
public class TestService extends TestSuperclass implements TestServiceInterface<Test>, Serializable{
}
@无状态
@远程(TestServiceInterface.class)
公共类TestService扩展TestSuperclass实现TestServiceInterface,可序列化{
}
我这样评价这个班:

@Stateless
@Remote(TestServiceInterface.class)
public class TestService extends TestSuperclass implements TestServiceInterface<Test>, Serializable{
}
@Stateless
@Remote(TestServiceInterface.class)
public class TestService implements TestServiceInterface<Test>, Serializable{
}
@无状态
@远程(TestServiceInterface.class)
公共类TestService实现TestServiceInterface,可序列化{
}

现在它不再抛出异常了。

请将您的
pom.xml
添加到问题中…我没有使用maven。您如何将“lib”jar添加到EJB模块?在netbeans项目部分,右键单击项目->属性->库->添加项目。错误消息表明库未正确打包到项目中。您是否将其打包为EJB/JAR?这不会以这种方式工作…但是您应该切换到基于maven的项目。请将您的
pom.xml
添加到问题中…我没有使用maven。您如何将“lib”jar添加到EJB模块?在netbeans项目部分,右键单击项目->属性->库->添加项目。错误消息表明库未正确打包到项目中。您是否将其打包为EJB/JAR?这不会以这种方式工作……不过您应该切换到基于maven的项目。我们不会在项目中的任何类中扩展TestSuperclass类。在将EAR文件部署到Payara Micro server时,我遇到了同样的问题。你能帮帮我吗?异常stacktrace中没有任何更改…我们没有在项目中的任何类中扩展TestSuperclass类。在将EAR文件部署到Payara Micro server时,我遇到了同样的问题。你能帮帮我吗?异常stacktrace中没有更改。。。