Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [dsdp-tm-dev] System registry problem

Hello Anna,

starting up the whole RSE UI (including all subsystems, filters
and other contributions) just because you need the UI-less
system registry is also not the right thing to do -- but 
that was what it was like in RSE 1.x.

So for RSE 2.x as a first step, the APIs were split into UI
and non UI; unfortunately we ran out of time splitting the
implementation too.

That will be done for RSE 3.x so in the future you should
be safe doing SystemStartHere.getSystemRegistry() and 
everything you can do from the interface you get should
work safely -- without any unnecessary plugin activations.

Until these refactorings are complete, the correct way of
initializing RSE in the 2.x stream is documented here:

Martin Oberhuber, Senior Member of Technical Staff, Wind River
Target Management Project Lead, DSDP PMC Member

> > into the UI and core pieces. Starting the UI plugin will 
> initialize  
> > the core registry. You can do a getTheSystemRegistryUI() to cause  
> > this. After which you should be able to use  
> > SystemStartHere.getSystemRegistry().
> > 
> We did something like that but I still think it's not good way to go.

Back to the top