Does RESTEasy support EJB 2.0 beans?

[tituslup]

Hi,

Does RESTEasy support EJB 2.0 beans?

RESTEasy 6.2.5 documentation points to using annotations for interfaces and beans, but in my application this is handled using ejb-jar.xml descriptor files, for example:

<session>
	<display-name>FolderService</display-name>
	<ejb-name>FolderService</ejb-name>
	<home>com.example.folder.ejb.session.FolderServiceHome</home>
	<remote>com.example.folder.FolderService</remote>
	<ejb-class>com.example.folder.ejb.session.FolderServiceBean</ejb-class>
	<session-type>Stateless</session-type>
	<transaction-type>Container</transaction-type>
</session>

Thanks,
-Titus

[jamezp]

RESTEasy 6.2.5 will not support EJB 2.0 as it targets Jakarta EE 10. It will support EJB's however https://jakarta.ee/specifications/restful-ws/3.1/jakarta-restful-ws-spec-3.1#async_ejbs.

[jamezp]

I used slightly different names, but if I annotate TestEJB2Bean with the Jakarta REST annotations, all seems to work. From the spec link above, I think that is required.

[tituslup]

Just to clarify, the spec link points to inheriting directly from the interface and using the EJB annotations (the new EJB3 approach) and no descriptor file. Are you saying in your example you are using this approach, that it worked this way and this is the only way it can work?

1. If I add @Remote to my interface (the one inheriting from EJBObject) and @stateless to the bean class (the one inheriting from SessionBean), deployment works, but nothing happens with respect to exposing the endpoint.
2. If I add @path as well to the bean, deployment fails with:

Jakarta RESTful Web Services resource [class com.example.oldejb.TestEJB2Bean] does not correspond to a view on the Jakarta Enterprise Beans TestEJB2Interface. @Path annotations can only be placed on classes or interfaces that represent a local, remote or no-interface view of an Jakarta Enterprise Beans.

3. If I drop the descriptor entries, EJBObject and SessionBean (in addition to 1 and 2), essentially using the EJB3 approach, then in works.

[jamezp]

All I did was add the @Path and @GET annotations to the TestEJB2Bean. I did not add EJB annotations. I've attached my example project.

ejb-in-jar.zip

[tituslup]

Thank you for providing the example.
I've ran 'mvn clean install' to generate the packages and copied ejb-war.war to my deployments folder to deploy it.
Deployment worked, management console JAX-RS shows the REST resource and end point indeed works.

19:03:37,099 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Starting deployment of "ejb-war.war" (runtime-name: "ejb-war.war")
19:03:37,301 INFO  [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0003: Processing weld deployment ejb-war.war
19:03:37,587 INFO  [org.jboss.weld.Version] (MSC service thread 1-5) WELD-000900: 5.1.2 (Final)
19:03:38,562 INFO  [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 5) RESTEASY002225: Deploying jakarta.ws.rs.core.Application: class dev.resteasy.examples.web.rest.RestActivator$Proxy$_$$_WeldClientProxy
19:03:38,572 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 5) WFLYUT0021: Registered web context: '/ejb-war' for server 'default-server'
19:03:38,637 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0010: Deployed "ejb-war.war" (runtime-name : "ejb-war.war")

The only problems I see:

• During deployment time there were no JNDI binding logs for this bean
• Management console does not list GreetingsService* under runtime->EJB section.

I wonder what this means ... if this EJB is valid or not.

Just to see what happens, I've copied ejb-jar.jar under the deployments folder and attempted to deploy that, JNDI bindings were logged this time, but deployment failed with the previously mentioned error:

2024-05-14 18:06:47,764 INFO Thread-17 [org.jboss.as.server.deployment.AbstractDeploymentUnitService] [start] WFLYSRV0027: Starting deployment of "ejb-jar.jar" (runtime-name: "ejb-jar.jar")
2024-05-14 18:06:47,789 INFO Thread-23 [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] [setupJNDIBindings] WFLYEJB0473: JNDI bindings for session bean named 'GreetingService' in deployment unit 'deployment "ejb-jar.jar"' are as follows:

        java:global/ejb-jar/GreetingService!dev.resteasy.examples.ejb.service.GreetingServiceHome
        java:app/ejb-jar/GreetingService!dev.resteasy.examples.ejb.service.GreetingServiceHome
        java:module/GreetingService!dev.resteasy.examples.ejb.service.GreetingServiceHome
        java:jboss/exported/ejb-jar/GreetingService!dev.resteasy.examples.ejb.service.GreetingServiceHome
        java:global/ejb-jar/GreetingService!dev.resteasy.examples.ejb.service.GreetingService
        java:app/ejb-jar/GreetingService!dev.resteasy.examples.ejb.service.GreetingService
        java:module/GreetingService!dev.resteasy.examples.ejb.service.GreetingService
        java:jboss/exported/ejb-jar/GreetingService!dev.resteasy.examples.ejb.service.GreetingService
        ejb:/ejb-jar/GreetingService!dev.resteasy.examples.ejb.service.GreetingService

2024-05-14 18:06:47,790 ERROR Thread-23 [org.jboss.msc.service.ServiceControllerImpl] [startFailed] MSC000001: Failed to start service jboss.deployment.unit."ejb-jar.jar".POST_MODULE
org.jboss.msc.service.StartException in service jboss.deployment.unit."ejb-jar.jar".POST_MODULE: WFLYSRV0153: Failed to process phase POST_MODULE of deployment "ejb-jar.jar"
        at org.jboss.as.server@22.0.1.Final//org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:178)
        at org.jboss.msc@1.5.2.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1617)
        at org.jboss.msc@1.5.2.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1580)
        at org.jboss.msc@1.5.2.Final//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1438)
        at org.jboss.threads@2.4.0.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
        at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
        at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
        at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
        at java.base/java.lang.Thread.run(Thread.java:840)
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYRS0010: Jakarta RESTful Web Services resource [class dev.resteasy.examples.ejb.service.GreetServiceSessionBean] does not correspond to a view on the Jakarta Enterprise Beans GreetingService. @Path annotations can only be placed on classes or interfaces that represent a local, remote or no-interface view of an Jakarta Enterprise Beans.

[jamezp]

Ah, good catch! It looks like my deployment is wrong. Let me see if I can fix that.

[tituslup]

Just to close the loop on this thread, I wasn't able to find a working solution using the xml descriptor that ties all the interfaces/beans/home classes. Instead I've focused on migrating to the EJB 3.X structure, with annotations and with no mapping inside the descriptor xml. More code changes, but definitely works.
@jamezp thanks for the inputs.

[jamezp]

Sorry about that. I got distracted on other tasks and didn't find time to pick this back up.