|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
I don't share your view on 5.1.2. Even though classloading requirement is not explicitly mentioned in 5.1.2 we cannot expect the container to treat a class that cannot be fully loaded as enabled bean. If we did the container would need to fail the deployment every time it encounters a CNFE.
I completely agree that there are cases when the observer is important, mandatory and the deployment should rather fail than to start without the observer being called. On the other hand there are cases when the deployment contains optional components only activated when some other framework is available on the classpath (e.g. an abstraction over a specific templating framework). These optional components are not expected to fail the deployment if they cannot be loaded.
None of these options is required by the specification. Since the proposed change would disallow the latter use-case and break existing applications I am reluctant to implementing the change.