4:48 p.m.
Resolver Exception sometimes gets hidden by a subsequent NPE
------------------------------------------------------------
Key: JBOSGI-480
URL: https://issues.jboss.org/browse/JBOSGI-480
Project: JBoss OSGi
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: David Bosschaert
Assignee: David Bosschaert
In some cases a resolver exception gets shadowed by a NPE that happens during the
processing of the resolver exception, this means that the end user has no way of knowing
why the resolution failed, he only sees the NPE.
The offending code can be found in the FelixResolver class, line 117:
XResolverException resex = new XResolverException(msg, exmod.getModule(), exreq);
In some cases exmod is null which means that an NPE gets thrown and the resolution
exception is lost.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:03 p.m.
New subject: [JBoss JIRA] Updated: (JBOSGI-480) Resolver Exception sometimes gets hidden by a subsequent NPE
[
https://issues.jboss.org/browse/JBOSGI-480?page=com.atlassian.jira.plugin...
]
Thomas Diesler updated JBOSGI-480:
----------------------------------
Fix Version/s: Approved and Unscheduled
Resolver Exception sometimes gets hidden by a subsequent NPE
------------------------------------------------------------
Key: JBOSGI-480
URL: https://issues.jboss.org/browse/JBOSGI-480
Project: JBoss OSGi
Issue Type: Bug
Security Level: Public(Everyone can see)
Reporter: David Bosschaert
Assignee: David Bosschaert
Fix For: Approved but Unscheduled
In some cases a resolver exception gets shadowed by a NPE that happens during the
processing of the resolver exception, this means that the end user has no way of knowing
why the resolution failed, he only sees the NPE.
The offending code can be found in the FelixResolver class, line 117:
XResolverException resex = new XResolverException(msg, exmod.getModule(), exreq);
In some cases exmod is null which means that an NPE gets thrown and the resolution
exception is lost.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:10 p.m.
New subject: [JBoss JIRA] Updated: (JBOSGI-480) Resolver Exception sometimes gets hidden by a subsequent NPE
[
https://issues.jboss.org/browse/JBOSGI-480?page=com.atlassian.jira.plugin...
]
Thomas Diesler updated JBOSGI-480:
----------------------------------
Fix Version/s: JBossOSGi 1.0.1
(was: Approved but Unscheduled)
Resolver Exception sometimes gets hidden by a subsequent NPE
------------------------------------------------------------
Key: JBOSGI-480
URL: https://issues.jboss.org/browse/JBOSGI-480
Project: JBoss OSGi
Issue Type: Bug
Security Level: Public(Everyone can see)
Reporter: David Bosschaert
Assignee: David Bosschaert
Fix For: JBossOSGi 1.0.1
In some cases a resolver exception gets shadowed by a NPE that happens during the
processing of the resolver exception, this means that the end user has no way of knowing
why the resolution failed, he only sees the NPE.
The offending code can be found in the FelixResolver class, line 117:
XResolverException resex = new XResolverException(msg, exmod.getModule(), exreq);
In some cases exmod is null which means that an NPE gets thrown and the resolution
exception is lost.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:12 p.m.
New subject: [JBoss JIRA] Updated: (JBOSGI-480) Resolver Exception sometimes gets hidden by a subsequent NPE
[
https://issues.jboss.org/browse/JBOSGI-480?page=com.atlassian.jira.plugin...
]
Thomas Diesler updated JBOSGI-480:
----------------------------------
Fix Version/s: Core Framework 1.0.1
(was: JBossOSGi 1.0.1)
Resolver Exception sometimes gets hidden by a subsequent NPE
------------------------------------------------------------
Key: JBOSGI-480
URL: https://issues.jboss.org/browse/JBOSGI-480
Project: JBoss OSGi
Issue Type: Bug
Security Level: Public(Everyone can see)
Reporter: David Bosschaert
Assignee: David Bosschaert
Fix For: Core Framework 1.0.1
In some cases a resolver exception gets shadowed by a NPE that happens during the
processing of the resolver exception, this means that the end user has no way of knowing
why the resolution failed, he only sees the NPE.
The offending code can be found in the FelixResolver class, line 117:
XResolverException resex = new XResolverException(msg, exmod.getModule(), exreq);
In some cases exmod is null which means that an NPE gets thrown and the resolution
exception is lost.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:14 p.m.
New subject: [JBoss JIRA] Updated: (JBOSGI-480) Resolver Exception sometimes gets hidden by a subsequent NPE
[
https://issues.jboss.org/browse/JBOSGI-480?page=com.atlassian.jira.plugin...
]
Thomas Diesler updated JBOSGI-480:
----------------------------------
Assignee: Thomas Diesler (was: David Bosschaert)
Resolver Exception sometimes gets hidden by a subsequent NPE
------------------------------------------------------------
Key: JBOSGI-480
URL: https://issues.jboss.org/browse/JBOSGI-480
Project: JBoss OSGi
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Core Framework
Reporter: David Bosschaert
Assignee: Thomas Diesler
Fix For: Core Framework 1.0.1
In some cases a resolver exception gets shadowed by a NPE that happens during the
processing of the resolver exception, this means that the end user has no way of knowing
why the resolution failed, he only sees the NPE.
The offending code can be found in the FelixResolver class, line 117:
XResolverException resex = new XResolverException(msg, exmod.getModule(), exreq);
In some cases exmod is null which means that an NPE gets thrown and the resolution
exception is lost.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:14 p.m.
New subject: [JBoss JIRA] Updated: (JBOSGI-480) Resolver Exception sometimes gets hidden by a subsequent NPE
[
https://issues.jboss.org/browse/JBOSGI-480?page=com.atlassian.jira.plugin...
]
Thomas Diesler updated JBOSGI-480:
----------------------------------
Component/s: Core Framework
Resolver Exception sometimes gets hidden by a subsequent NPE
------------------------------------------------------------
Key: JBOSGI-480
URL: https://issues.jboss.org/browse/JBOSGI-480
Project: JBoss OSGi
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Core Framework
Reporter: David Bosschaert
Assignee: Thomas Diesler
Fix For: Core Framework 1.0.1
In some cases a resolver exception gets shadowed by a NPE that happens during the
processing of the resolver exception, this means that the end user has no way of knowing
why the resolution failed, he only sees the NPE.
The offending code can be found in the FelixResolver class, line 117:
XResolverException resex = new XResolverException(msg, exmod.getModule(), exreq);
In some cases exmod is null which means that an NPE gets thrown and the resolution
exception is lost.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:45 p.m.
New subject: [JBoss JIRA] (JBOSGI-480) Resolver Exception sometimes gets hidden by a subsequent NPE
[
https://issues.jboss.org/browse/JBOSGI-480?page=com.atlassian.jira.plugin...
]
Thomas Diesler resolved JBOSGI-480.
-----------------------------------
Fix Version/s: (was: JBossOSGi 1.0.1)
Resolution: Duplicate Issue
Duplicates JBOSGI-490
Resolver Exception sometimes gets hidden by a subsequent NPE
------------------------------------------------------------
Key: JBOSGI-480
URL: https://issues.jboss.org/browse/JBOSGI-480
Project: JBoss OSGi
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Core Framework
Reporter: David Bosschaert
Assignee: Thomas Diesler
In some cases a resolver exception gets shadowed by a NPE that happens during the
processing of the resolver exception, this means that the end user has no way of knowing
why the resolution failed, he only sees the NPE.
The offending code can be found in the FelixResolver class, line 117:
XResolverException resex = new XResolverException(msg, exmod.getModule(), exreq);
In some cases exmod is null which means that an NPE gets thrown and the resolution
exception is lost.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4496
days inactive
4690
days old
jboss-osgi-issues@lists.jboss.org
6 comments
2 participants
participants (2)
-
David Bosschaert (JIRA) -
Thomas Diesler (JIRA)