You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2008/10/10 12:29:44 UTC

[jira] Updated: (FELIX-750) BundleException messages lack bundle ids

     [ https://issues.apache.org/jira/browse/FELIX-750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler updated FELIX-750:
-----------------------------------

    Attachment: Felix.java.patch

Proposed patch

> BundleException messages lack bundle ids
> ----------------------------------------
>
>                 Key: FELIX-750
>                 URL: https://issues.apache.org/jira/browse/FELIX-750
>             Project: Felix
>          Issue Type: Improvement
>          Components: Framework
>            Reporter: Alexander Klimetschek
>            Priority: Minor
>         Attachments: Felix.java.patch
>
>
> If there is a problem with a bundle, the name, version and other information that identifies the bundle should be part of the exception message for tracing back which bundle caused a problem.
> For example, I got this exception during an automated install of many bundles and have (from looking at the stacktrace and the osgi web console) no clue which bundle was affected:
> org.osgi.framework.BundleException: Bundle symbolic name and version are not unique.
> 	at org.apache.felix.framework.Felix.createModule(Felix.java:3408)
> 	at org.apache.felix.framework.Felix.createBundleInfo(Felix.java:3332)
> 	at org.apache.felix.framework.Felix.installBundle(Felix.java:2315)
> 	at org.apache.felix.framework.Felix.installBundle(Felix.java:2229)
> It is generally helpful for developers using a framework to have context information in exception messages (aka the important pieces of the current variable stack).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.