[ 
https://issues.apache.org/jira/browse/ARIES-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14376005#comment-14376005
 ] 

Thomas Watson commented on ARIES-1245:
--------------------------------------

The biggest issue is we have no framework API to capture resolution errors 
while calling FrameworkWiring.resolveBundles

Equinox has such API, but it would require Aries to use some Equinox specific 
API.  This would be similar to how the 'diag' command gets resolution 
information in the Equinox osgi>

http://git.eclipse.org/c/equinox/rt.equinox.bundles.git/tree/bundles/org.eclipse.equinox.console/src/org/eclipse/equinox/console/commands/EquinoxCommandProvider.java#n1939

The getResolutionReport is the interesting method.  Perhaps we can use optional 
imports for these equinox packages to at least give us better errors when 
running on Equinox.  The other option to consider when running on equinox is to 
register your own ResolverHookFactory that returns ResolutionReport.Listener 
types like the EquinoxCommandProvider does above and capture the resolution 
errors that occur while starting a subsystem.  This can be done by 
'handler/agent' that is installing and starting subsystems instead of the 
subsystems implementation itself.

> SubsystemException: Framework could not resolve the bundles
> -----------------------------------------------------------
>
>                 Key: ARIES-1245
>                 URL: https://issues.apache.org/jira/browse/ARIES-1245
>             Project: Aries
>          Issue Type: Bug
>          Components: Subsystem
>         Environment: Windows
>            Reporter: Tom Evans
>            Assignee: Jeremy Hughes
>            Priority: Minor
>         Attachments: StartAction.java.v2.patch, StartActionPatch.txt
>
>
> During testing on Windows we have seen an intermittent problem which causes 
> an application not to be resolved correctly. The only evidence in our logs is 
> the following stack... (The message is not very helpful as it gives no 
> indication of which bundles could not be resolved).
> org.osgi.service.subsystem.SubsystemException: Framework could not resolve 
> the bundles
>       at 
> org.apache.aries.subsystem.core.internal.StartAction.resolve(StartAction.java:170)
>       at 
> org.apache.aries.subsystem.core.internal.StartAction.run(StartAction.java:104)
>       at 
> java.security.AccessController.doPrivileged(AccessController.java:274)
>       at 
> org.apache.aries.subsystem.core.internal.BasicSubsystem.start(BasicSubsystem.java:287)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to