-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error while deployed to WildFly 13: "Failed to process business interfaces for EJB class" #405
Comments
Thanks for your feedback. I have not yet tested the deployment under Wildfly 13. I will check this. |
I'm trying to try other versions. |
I just tested successful version 11.0.0-Final. |
yes you are right. There is an issue with Wildfly 12. Thanks for your finding! |
I think with the fixes in the latest snapshot release 4.3.6-SNAPSHOT deployment now should work in Wildfly 12 and Wildfly 13. Can you confirm this? This would be a great help, if you can verify this in your environment. |
Using lastest fix:
While deployed to WildFly 13, there are still errors: 08:58:23,255 INFO [org.eclipse.persistence.connection] (ServerService Thread Pool -- 67) /vfs:/D:/wildfly-13.0.0.Final/bin/content/imixs-jsf-example-4.0.11.war/WEB-INF/classes/_org.imixs.workflow.jpa login successful 08:58:23,798 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "imixs-jsf-example-4.0.11.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit."imixs-jsf-example-4.0.11.war".POST_MODULE" => "WFLYSRV0153: Failed to process phase POST_MODULE of deployment "imixs-jsf-example-4.0.11.war" Connected to server |
Ok, it works for WildFly 11. thanks a lot! |
I also now tested the JSF-Sample Application successfully with wildfly 13.
|
Finally ,it can works with WildFly 13.Great! |
tested successfully. |
What was wrong? And what did you have to do to correct it? I have the same problem and I could not find a solution. |
Can you please post the deployment error from your current server log file. The upper discussion is a bit out of date. Which version are you using - Wildfly and Imixs-JSF-Sample App ? |
I'm doing the server migration in my application, currently it's used JBoss eap 6.4 and now I'm migrating to WildFly 13.0.0.Final.
Thank you |
ok the problem was that I used a final static method in an EJB / Jax-rs class: e.g:
need to be changed into:
final static is not allowed within Java EE7 I think you have the problem in your class: br.com.qualirede.cadastro.domain.estado.EstadoDAO |
Had a method that was using final, I made the adjustment you mentioned and it worked. Thank you very much. |
While deployed to WildFly 13, there are the following errors:
17:47:20,734 INFO [org.eclipse.persistence.connection] (ServerService Thread Pool -- 21) /vfs:/D:/wildfly-13.0.0.Final/bin/content/imixs-jsf-example-4.0.11.war/WEB-INF/classes/_org.imixs.workflow.jpa login successful
17:47:21,107 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.deployment.unit."imixs-jsf-example-4.0.11.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."imixs-jsf-example-4.0.11.war".POST_MODULE: WFLYSRV0153: Failed to process phase POST_MODULE of deployment "imixs-jsf-example-4.0.11.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:150)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1736)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1698)
at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYEJB0466: Failed to process business interfaces for EJB class class org.imixs.workflow.jaxrs.WorkflowRestService
at org.jboss.as.ejb3.deployment.processors.BusinessViewAnnotationProcessor.deploy(BusinessViewAnnotationProcessor.java:96)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:143)
... 8 more
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYEJB0498: Business view method parseWorkitem declared final in org.imixs.workflow.jaxrs.WorkflowRestService
at org.jboss.as.ejb3.deployment.processors.BusinessViewAnnotationProcessor.verifyNoInterfaceViewMethodsNotDeclaredFinal(BusinessViewAnnotationProcessor.java:228)
at org.jboss.as.ejb3.deployment.processors.BusinessViewAnnotationProcessor.processViewAnnotations(BusinessViewAnnotationProcessor.java:149)
at org.jboss.as.ejb3.deployment.processors.BusinessViewAnnotationProcessor.deploy(BusinessViewAnnotationProcessor.java:94)
... 9 more
17:47:21,108 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 2) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "imixs-jsf-example-4.0.11.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit."imixs-jsf-example-4.0.11.war".POST_MODULE" => "WFLYSRV0153: Failed to process phase POST_MODULE of deployment "imixs-jsf-example-4.0.11.war"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYEJB0466: Failed to process business interfaces for EJB class class org.imixs.workflow.jaxrs.WorkflowRestService
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYEJB0498: Business view method parseWorkitem declared final in org.imixs.workflow.jaxrs.WorkflowRestService"}}
17:47:21,110 ERROR [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0021: Deploy of deployment "imixs-jsf-example-4.0.11.war" was rolled back with the following failure message:
{"WFLYCTL0080: Failed services" => {"jboss.deployment.unit."imixs-jsf-example-4.0.11.war".POST_MODULE" => "WFLYSRV0153: Failed to process phase POST_MODULE of deployment "imixs-jsf-example-4.0.11.war"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYEJB0466: Failed to process business interfaces for EJB class class org.imixs.workflow.jaxrs.WorkflowRestService
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYEJB0498: Business view method parseWorkitem declared final in org.imixs.workflow.jaxrs.WorkflowRestService"}}
The text was updated successfully, but these errors were encountered: