Thanks BJ, from what I see that will do the trick, expect that it is runtime, but I can live with that.
Alain On Tue, Jul 17, 2018 at 7:58 AM BJ Hargrave <hargr...@us.ibm.com> wrote: > Look at the ServiceComponentRuntime service: > https://osgi.org/specification/osgi.cmpn/7.0.0/service.component.html#service.component-introspection > > It provides access to DTOs which describe each component description, > ComponentDescriptionDTO, and actual component instances, > ComponentConfigurationDTO. You can follows the ReferenceDTOs to see the > dependency graph. > > > -- > > BJ Hargrave > Senior Technical Staff Member, IBM // office: +1 386 848 1781 > OSGi Fellow and CTO of the OSGi Alliance // mobile: +1 386 848 3788 > hargr...@us.ibm.com > > > > ----- Original message ----- > From: Alain Picard via osgi-dev <osgi-dev@mail.osgi.org> > Sent by: osgi-dev-boun...@mail.osgi.org > To: osgi-dev@mail.osgi.org > Cc: > Subject: [osgi-dev] Tool/API to analyze component dependencies > Date: Tue, Jul 17, 2018 6:27 AM > > As I'm going through our migration to DS I am in need of understanding our > component "graph" and to make sure there are no cycles. For the core ones, > I manually created of small dot file from the @Reference and used graphviz > to render. > > Now I am looking for some API to automate the process, at dev time if > possible. AFAIK, DS will read the component.xml and create a registry with > all info. Can I make use of this resolution to grab all the info that I > need? > > Thanks > Alain > _______________________________________________ > OSGi Developer Mail List > osgi-dev@mail.osgi.org > https://mail.osgi.org/mailman/listinfo/osgi-dev > > > >
_______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
