[
https://jira.jboss.org/jira/browse/WBX-33?page=com.atlassian.jira.plugin....
]
Benjamin Graf updated WBX-33:
-----------------------------
Description:
I recognized an issue while compiling latest webbeans se extension. Two unit tests fails
because of an NullPointerException. The reason for this exception is:
SE Extension finally sends an shutdown event which is fired to all observers in
EventManager.notifyObservers().
Finally this method in WebBeans Core Impl invokes
DependentContext.instance().setActive(false);
And there is the problem. If you follow the invokationprocess you'll get an instance
of the current introduced IsolatedStaticSingletonProvider whose internal object reference
is already null. Maybe this instance was cleaned to early by the event processing?
Take a look at ShutdownManager (bootstrap.shutdown())
was:
I recognized an issue while compiling latest webbeans se extension. Two unit tests fails
because of an NullPointerException. The reason for this exception is:
SE Extension finally sends an shutdown event which is fired to all observers in
EventManager.notifyObservers().
Finally this method in WebBeans Core Impl invokes
DependentContext.instance().setActive(false);
And there is the problem. If you follow the invokationprocess you'll get an instance
of the current introduced IsolatedStaticSingletonProvider whose internal object reference
of the ManagerImpl is already null. Maybe this instance was cleaned to early by the event
processing?
Problem with webbeans event handling while compiling SE extension
-----------------------------------------------------------------
Key: WBX-33
URL:
https://jira.jboss.org/jira/browse/WBX-33
Project: Web Beans Extensions
Issue Type: Bug
Components: Java SE
Environment: Windows XP+JDK6.12+Maven 2.0.9
Reporter: Benjamin Graf
I recognized an issue while compiling latest webbeans se extension. Two unit tests fails
because of an NullPointerException. The reason for this exception is:
SE Extension finally sends an shutdown event which is fired to all observers in
EventManager.notifyObservers().
Finally this method in WebBeans Core Impl invokes
DependentContext.instance().setActive(false);
And there is the problem. If you follow the invokationprocess you'll get an instance
of the current introduced IsolatedStaticSingletonProvider whose internal object reference
is already null. Maybe this instance was cleaned to early by the event processing?
Take a look at ShutdownManager (bootstrap.shutdown())
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira