Issue Details (XML | Word | Printable)

Key: GLASSFISH-19978
Type: Bug Bug
Status: Resolved Resolved
Resolution: Cannot Reproduce
Priority: Minor Minor
Assignee: jjsnyder83
Reporter: myfear
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
glassfish

public enum classes log severe messages in server log

Created: 21/Mar/13 04:49 AM   Updated: 11/Apr/13 09:25 PM   Resolved: 11/Apr/13 09:25 PM
Component/s: cdi
Affects Version/s: None
Fix Version/s: future release

Time Tracking:
Not Specified

Environment:

GlassFish Server Open Source Edition 4.0 (build 80)


Tags: fishcat
Participants: jjsnyder83, myfear and tlcksnyder


 Description  « Hide

Having two public enum types in my app leads to following log messages during deployment:

public enum Role { JUNIOR, PRINCIPAL, SENIOR }

INFO: Loading application [MissionControl] at [/MissionControl]
SEVERE: No valid EE environment for injection of net.eisele.mcontrl.entities.types.MissionState
SEVERE: No valid EE environment for injection of net.eisele.mcontrl.entities.types.MissionState
SEVERE: No valid EE environment for injection of net.eisele.mcontrl.entities.types.MissionState
SEVERE: No valid EE environment for injection of net.eisele.mcontrl.entities.types.Role
SEVERE: No valid EE environment for injection of net.eisele.mcontrl.entities.types.MissionState
SEVERE: No valid EE environment for injection of net.eisele.mcontrl.entities.types.MissionState
SEVERE: No valid EE environment for injection of net.eisele.mcontrl.entities.types.MissionState
SEVERE: No valid EE environment for injection of net.eisele.mcontrl.entities.types.MissionState
SEVERE: No valid EE environment for injection of net.eisele.mcontrl.entities.types.MissionState
SEVERE: No valid EE environment for injection of net.eisele.mcontrl.entities.types.Role
SEVERE: No valid EE environment for injection of net.eisele.mcontrl.entities.types.Role
SEVERE: No valid EE environment for injection of net.eisele.mcontrl.entities.types.MissionState
INFO: MissionControl was successfully deployed in 1.546 milliseconds.



tlcksnyder added a comment - 21/Mar/13 01:24 PM

Please provide a test case, or explain further as to why you feel this is a CDI issue. We cannot investigate without more information and a test case.