Community
Participate
Working Groups
An adopter is requesting this bug to be fixed in 3.3.1 P +++ This bug was initially created as a clone of Bug #364499 +++ +++ This bug was initially created as a clone of Bug #363973 +++ Unlike most Faceted project creation operations. The EJB Client op does not inherit the behavior of synching or reacting to a new runtime set, and checking for the latest java version supported. This is because it inherits the "default" java version based on the initial fixed facet template. For instance, if the EJB project version is 3.1, then it defaults to java 6.
Created attachment 207624 [details] Proposed patch Patch created using R3_3_1
same fix reviewed earlier... I approve
Correction - this was an EJB problem.. properly categorizing
Created attachment 207763 [details] Null check for runtime An NPE was detected when running the JUnits. A null check must be done for the cases where the project does not have runtime. Note: This patch does not make obsolete the previous patch: it should be applied on top of it.
Committed to R3_3_1_patches