Pass arguments by reference with ref keyword to any runtime in GoLang app
This article provides an introduction to cross-technology invocation of both static and instance methods which contains argument of type ref. Parameter modifier ref in C# (.NET) technology is used in a method signature to pass an argument by reference. It is described in details in this article.
Javonet allows you to reference and use modules or packages written in (Java/Kotlin/Groovy/Clojure, C#/VB.NET, Ruby, Perl, Python, JavaScript/TypeScript) like they were created in your technology. If have not yet created your first project check Javonet overview and quick start guides for your technology.
With Javonet you can interact with methods with ref parameter modifier from any runtime like they were available in GoLang but invocation must be performed through Javonet SDK API.
Javonet allows you to pass any GoLang value type as argument to method from any runtime. For reference type arguments (instances of other classes) you can create such instance with Javonet and pass the Invocation Context variable referencing that object as argument of static method invocation.
Custom any runtime with ref GoLang argument
With Javonet it is possible to reference any custom any runtime and interact with its methods declared on types defined within that module almost the same as with any other GoLang library.
Snippet below represents the sample code from any runtime which contains methods with ref parameter modifier.
Select technology of module you want to use:
It is possible to invoke the declared methods from any runtime using following GoLang code:
Select technology of module you want to use:
This snippet uses in memory runtime bridging to load the any runtime and next retrieves reference to specific type.
Next, two reference type arguments are created. An argument that is passed to a ref parameter must be initialized before it's passed to a method. Two ways of initialization are presented in create values for ref section of the snippet.
Fist argument (refValue1) is initialized using asRef() method with default type of passed value (int). This type matches the type of parameter in RefSampleMethod(ref int x) method.
Second argument (refValue2) is initialized using asRef() method with specifying the exact type which should be use. "System.Int32" is an alias for int.
Both values can be passed to RefSampleMethod(ref int x) method using invokeStaticMethod(...).execute() invocation.
Each reference type argument is get as regular GoLang value using getRefValue() and can be used for further processing.
Custom GoLang with ref keyword
It is possible to invoke the declared method which contains multiple ref arguments from any runtime using following GoLang code:
Select technology of module you want to use:
This snippet uses in memory runtime bridging to load the any runtime and next retrieves reference to specific type.
Next, three reference type arguments are created. An argument that is passed to a ref parameter must be initialized before it's passed to a method. Two ways of initialization are presented in create values for ref section of the snippet.
Fist argument (refToInt) is initialized using asRef() method with default type of passed value (int). This type matches the type of first parameter in RefSampleMethod2 method.
Second value (refToDouble) is initialized using asRef() method with specifying the exact type which should be used. "System.Double" is an alias for double.
Third argument (refToString) is initialized using asRef() method with default type of passed value (string).
All three arguments are processed in RefSampleMethod2 and changed. Their values are obtained using getRefValue() method.
The same operation can be performed remotely by just changing the new Runtime Context invocation from in memory to tcp that will create and interact with your any runtime objects on any remote node, container or service that hosts Javonet Code Gateway. This way you can preserve the same logic in your application and instantly switch between monolithic and microservices architecture without the need to implement the integration layer based on web services or other remote invocation methods.
Read more about use cases and software architecture scenarios where Javonet runtime bridging technology can support your development process.
Was this article helpful?