Select a language
- Afrikaans
- አማርኛ
- العربية
- অসমীয়া
- Azərbaycan
- Bashkir
- Български
- বাংলা
- བོད་སྐད་
- Bosnian
- Català
- Čeština
- Cymraeg
- Dansk
- Deutsch
- Dolnoserbšćina
- ދިވެހިބަސް
- Ελληνικά
- Español
- Eesti
- Euskara
- فارسی
- Suomi
- Filipino
- Na Vosa Vakaviti
- Føroyskt
- Français
- Français (Canada)
- Gaeilge
- Galego
- Konkani
- ગુજરાતી
- Hausa
- עברית
- हिन्दी
- Hrvatski
- Hornjoserbšćina
- Haitian Creole
- Magyar
- Հայերեն
- Indonesia
- Ásụ̀sụ́ Ìgbò
- Inuinnaqtun
- Íslenska
- Italiano
- ᐃᓄᒃᑎᑐᑦ
- Inuktitut (Latin)
- 日本語
- ქართული
- Қазақ Тілі
- ខ្មែរ
- Kurdî (Bakur)
- ಕನ್ನಡ
- 한국어
- Kurdî (Navîn)
- Кыргызча
- Lingála
- ລາວ
- Lietuvių
- Ganda
- Latviešu
- 中文 (文言文)
- Maithili
- Malagasy
- Te Reo Māori
- Македонски
- മലയാളം
- Mongolian (Cyrillic)
- ᠮᠣᠩᠭᠣᠯ ᠬᠡᠯᠡ
- मराठी
- Melayu
- Malti
- Hmong Daw
- မြန်မာ
- Norsk Bokmål
- नेपाली
- Nederlands
- Sesotho sa Leboa
- Nyanja
- ଓଡ଼ିଆ
- Hñähñu
- ਪੰਜਾਬੀ
- Polski
- دری
- پښتو
- Português (Brasil)
- Português (Portugal)
- Română
- Русский
- Rundi
- Kinyarwanda
- سنڌي
- සිංහල
- Slovenčina
- Slovenščina
- Gagana Sāmoa
- chiShona
- Soomaali
- Shqip
- Српски (ћирилица)
- Srpski (latinica)
- Sesotho
- Svenska
- Kiswahili
- தமிழ்
- తెలుగు
- ไทย
- ትግር
- Türkmen Dili
- Klingon (Latin)
- Klingon (pIqaD)
- Setswana
- Lea Fakatonga
- Türkçe
- Татар
- Reo Tahiti
- ئۇيغۇرچە
- Українська
- اردو
- Uzbek (Latin)
- Tiếng Việt
- isiXhosa
- Èdè Yorùbá
- Yucatec Maya
- 粵語 (繁體)
- 中文 (简体)
- 繁體中文 (繁體)
- Isi-Zulu
Runtime Context
Runtime Context represents the single context which allows to interact with selected technology.
RuntimeContext refers to single instance of the called runtime within particular target OS process either the local currently running process (inMemory) or particular remote process identified by IP Address and PORT of target Javonet instance.
Multiple Runtime Contexts can be initialized within one process.
Calling the same technology on inMemory communication channel will return the existing instance of runtime context.
Calling the same technology on TCP channel but on different nodes will result with unique Runtime Contexts.
Within the runtime context developer can load any number of libraries and interact with any objects from target technology that are aware of each other due to sharing the same memory space and same runtime instance.
Was this article helpful?
Thanks for your feedback!