[JBoss JIRA] (WFLY-7085) Server should verify EJB business methods during deployment and reject
by Romain Pelisse (JIRA)
[ https://issues.jboss.org/browse/WFLY-7085?page=com.atlassian.jira.plugin.... ]
Romain Pelisse reopened WFLY-7085:
----------------------------------
> Server should verify EJB business methods during deployment and reject
> ----------------------------------------------------------------------
>
> Key: WFLY-7085
> URL: https://issues.jboss.org/browse/WFLY-7085
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 11.0.0.Alpha1
> Reporter: Wolf-Dieter Fink
> Assignee: Romain Pelisse
> Labels: downstream_dependency
> Fix For: 12.0.0.Beta1, 12.0.0.Final, 13.0.0.Beta1, 13.0.0.Final
>
>
> The ejb 3.2 core specification state in chapter 4.9.6 that business methods should not be declared as final or static.
> But a Bean with a business method declared in the local or remote interface can be correct deployed and is accesible under some circumstances.
> To ensure that the Bean is according to the spec and avoid runtime or injection issues the methods should be checked and a VerifyError should be thrown at deployment time.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 12 months
[JBoss JIRA] (WFCORE-3962) Starting WFLY with JDK 11 blows up with ModuleNotFoundException java.se
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3962?page=com.atlassian.jira.plugi... ]
David Lloyd commented on WFCORE-3962:
-------------------------------------
Digging around the OpenJDK source, I was thinking maybe we could try adding the system property {{-Djdk.module.addmods.0=java.se}}? If that works, then we can do that for all JDKs without breaking Java 8.
> Starting WFLY with JDK 11 blows up with ModuleNotFoundException java.se
> -----------------------------------------------------------------------
>
> Key: WFCORE-3962
> URL: https://issues.jboss.org/browse/WFCORE-3962
> Project: WildFly Core
> Issue Type: Bug
> Components: Modules
> Affects Versions: 6.0.0.Alpha3
> Reporter: Matej Novotny
> Assignee: David Lloyd
> Priority: Blocker
> Labels: Java11
>
> As per request, copying MODULES-372 to WFCORE as well.
> Starting WFLY with JDK 11 using {{standalone.sh}} yields:
> {code}
> org.jboss.modules.ModuleNotFoundException: java.se
> at org.jboss.modules.Module.addPaths(Module.java:1266)
> at org.jboss.modules.Module.link(Module.java:1622)
> at org.jboss.modules.Module.relinkIfNecessary(Module.java:1650)
> at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:296)
> at org.jboss.modules.Main.main(Main.java:437)
> {code}
> Output of {{java -version}}:
> {code}
> openjdk version "11-ea" 2018-09-25
> OpenJDK Runtime Environment 18.9 (build 11-ea+21)
> OpenJDK 64-Bit Server VM 18.9 (build 11-ea+21, mixed mode)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 12 months
[JBoss JIRA] (WFCORE-3962) Starting WFLY with JDK 11 blows up with ModuleNotFoundException java.se
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3962?page=com.atlassian.jira.plugi... ]
David Lloyd commented on WFCORE-3962:
-------------------------------------
There appears to be no way to make the JDK load the {{java.se}} modules other than giving it on the command line.
> Starting WFLY with JDK 11 blows up with ModuleNotFoundException java.se
> -----------------------------------------------------------------------
>
> Key: WFCORE-3962
> URL: https://issues.jboss.org/browse/WFCORE-3962
> Project: WildFly Core
> Issue Type: Bug
> Components: Modules
> Affects Versions: 6.0.0.Alpha3
> Reporter: Matej Novotny
> Assignee: David Lloyd
> Priority: Blocker
> Labels: Java11
>
> As per request, copying MODULES-372 to WFCORE as well.
> Starting WFLY with JDK 11 using {{standalone.sh}} yields:
> {code}
> org.jboss.modules.ModuleNotFoundException: java.se
> at org.jboss.modules.Module.addPaths(Module.java:1266)
> at org.jboss.modules.Module.link(Module.java:1622)
> at org.jboss.modules.Module.relinkIfNecessary(Module.java:1650)
> at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:296)
> at org.jboss.modules.Main.main(Main.java:437)
> {code}
> Output of {{java -version}}:
> {code}
> openjdk version "11-ea" 2018-09-25
> OpenJDK Runtime Environment 18.9 (build 11-ea+21)
> OpenJDK 64-Bit Server VM 18.9 (build 11-ea+21, mixed mode)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 12 months