Loading 'singleton' like project level objects from Config



In the RE_Framework, today, the information from Config has to be passed to the “Process.xaml” through arguments. It would be great if some component was built, in the framework to make Config directly accessible throughout the projects in the form of a ‘singleton’ like object that J2EE frameworks use very often.
You could also use it to store things like UiBrowser objects, so in cases where the Attach Browser is not working, and the UiBrowser has to be passed on to it, we can directly use the project level object from anywhere in the project, as against passing the UiBrowser.


Possible duplicate of topic below (and related):

Seems to be planned for 2017.2… which probably should now be changed to 2018.1 as there will be no 2017.2 AFAIK.


To me it sounds similar to the Entity feature which is planned for 18.2


Please read all below with “as far as I understand” prefixing :slight_smile:

I’d disagree.

To me Entity is about creating custom objects (basically DTO’s) inside UiStudio. These are not global in scope (as they’re still normal objects that need to be passed as arguments), nor are they Singleton in nature (as that would prohibit using any type of collection of them, greatly limiting use).

This however serves a different need of having a centralized storage for configuration, acting more as the classic app.config (but filled on runtime).

I wouldn’t completely agree with proposed use case for UiBrowser object (singletons always are debatable I guess), hence the “possible” in the “possible duplicate” link in my previous post, albeit that one would fill both this one and the global config needs.

Feel free to disagree of course (especially OP - let’s not hijack completely :wink: ).


So if we had two different things

  1. An application correct holding bean like objects
  2. app config or app properties location/object/dictionary/map

That would do.


There was a typo. I meant “application context” not ‘application correct’


I see. I’m not very familiar with javabeans but if my understanding is correct, Upen you’d want a combination of Entity and Global vars.

If so, when both of these are implemented you could use them for configuration purposes: store all the config settings in an entity and make that entity global.


Yes. thats correct.


Indeed seems to be related with Global/Project Variable.

For now we’ll go after Entity: Project Level Variable

I’ll close it as duplicate.