[
https://jira.jboss.org/jira/browse/JBOSGI-137?page=com.atlassian.jira.plu...
]
Thomas Diesler edited comment on JBOSGI-137 at 9/11/09 3:04 AM:
----------------------------------------------------------------
Adrian says: Fixing this parsing problem is on my list of things to fix.
was (Author: thomas.diesler(a)jboss.com):
Adrian sais: Fixing this parsing problem is on my list of things to fix.
Cannot parse Bundle-SymbolicName
--------------------------------
Key: JBOSGI-137
URL:
https://jira.jboss.org/jira/browse/JBOSGI-137
Project: JBoss OSGi
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Core
Reporter: Thomas Diesler
Assignee: Adrian Brock
Fix For: Framework 1.0.x
The AbstractOSGiMetaData.parseSymbolicName() cannot always parse the symbolic name
Currently there is a hack in place falls back to the main attribute
public String getBundleSymbolicName()
{
String symbolicName = null;
ParameterizedAttribute parameters = parseSymbolicName();
if (parameters != null)
symbolicName = parameters.getAttribute();
// [TODO] Remove this fall back
if (symbolicName == null)
symbolicName = getMainAttribute(Constants.BUNDLE_SYMBOLICNAME);
if (symbolicName == null)
throw new IllegalStateException("Cannot obtain " +
Constants.BUNDLE_SYMBOLICNAME);
return symbolicName;
}
--
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