Re: [dsdp-tm-dev] System registry problem

[David Dykstal <dykstal@xxxxxxx>]

Anna --

My mistake. I was reading too quickly again. You are correct.

The system registry was split in 2.0 as a result of more refactoring  
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().

-- Dave

On Jan 18, 2008, at 11:53 AM, Anna wrote:

> Dave,
>
> > RSEUIPlugin.getTheSystemRegistry() is not deprecated. Is there some
> > reason you stopped using it?
>
> I cannot see such a method in RSE 2.0.2, there's
> getTheSystemRegistryUI(), which is different I guess.
>
> > Another committer could correct me here, but in doing a quick scan of
> > the code it seems that there is no good way to initialize the core
> > registry without starting the UI plugin. We'll see if we can migrate
> > that function into the core in the next release.
> >
> > -- Dave
> >
> > On Jan 18, 2008, at 9:48 AM, Anna wrote:
> >
> > > Hi all,
> > > I've been porting our code from RSE 1.0 to RSE 2.0.2 and found one  
> > > big
> > > problem here: now instead of RSEUIPlugin.getTheSystemRegistry()  
> > > we're
> > > recommended to use SystemStartHere.getSystemRegistry().
> > > Everything works nice if you had your RSE UI started before doing
> > > SystemStartHere.getSystemRegistry(). But if you didn't,
> > > SystemStartHere.getSystemRegistry() returns null, since the only  
> > > place
> > > where this value is set is start() method of RSEUIPlugin.
> > > I filed a bug for this
> > > problem(https://bugs.eclipse.org/bugs/show_bug.cgi?id=215820 ).
> > >
> > > Am I missing anything obvious here?
> > >
> > > Thanks!
> > > Anna.
> > >
> > > _______________________________________________
> > > dsdp-tm-dev mailing list
> > > dsdp-tm-dev@xxxxxxxxxxx
> > > https://dev.eclipse.org/mailman/listinfo/dsdp-tm-dev
> >
> > _______________________________________________
> > dsdp-tm-dev mailing list
> > dsdp-tm-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/dsdp-tm-dev
>
> _______________________________________________
> dsdp-tm-dev mailing list
> dsdp-tm-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/dsdp-tm-dev