Re: [riena-dev] Riena on RAP: NavigationSourceProvider

["Barth, Heiko" <Heiko.Barth@xxxxxxxxxxxx>]

Btw.: We should discuss if the SubModuleView is the right place to notify a "activeNodeChange". But this is independent of the point that we should not use the static instance…

 

 

Von: riena-dev-bounces@xxxxxxxxxxx [mailto:riena-dev-bounces@xxxxxxxxxxx] Im Auftrag von Barth, Heiko
Gesendet: Freitag, 10. September 2010 09:17
An: Riena Developers list
Betreff: Re: [riena-dev] Riena on RAP: NavigationSourceProvider

 

Hi Stefan,

I think you´re right. Working with the static instance of NavigationSourceProvider would cause Problems within RAP because this way different Sessions (different Application instances) would observe one central (static instance) selection.

+1 for your changes!

 

-Heiko

 

Von: riena-dev-bounces@xxxxxxxxxxx [mailto:riena-dev-bounces@xxxxxxxxxxx] Im Auftrag von Liebig, Stefan
Gesendet: Freitag, 10. September 2010 08:41
An: Riena Developers list
Betreff: [riena-dev] Riena on RAP: NavigationSourceProvider

 

Hi Rienars,

 

Could some please verify the changes I have done in

- NavigationSourceProvider

- SubModuleView

 

NavigationSourceProvider kept when instantiated (via an executable extension) a reference to it's instance in a static field. The SubModuleView called a static method on the NSP which than "dispatched" the call via the static instance reference to the NSP instance.

My assumption is that this may cause problems when running with RAP.

 

The SWT Example App is still running in RCP and RAP.

 

Tschüß,

Stefan

 

-------------------------------------------------------------
compeople AG
Untermainanlage 8
60329 Frankfurt/Main

fon: +49 (0) 69 / 27 22 18 0
fax: +49 (0) 69 / 27 22 18 22
web: www.compeople.de

Vorstand: Jürgen Wiesmaier
Aufsichtsratsvorsitzender: Christian Glanz

Sitz der Gesellschaft: Frankfurt/Main
Handelsregister Frankfurt HRB 56759
Ust-Ident.-Nr: DE207665352
-------------------------------------------------------------