Static fields and properties

This article provides an introduction to cross-technology handling of static fields and properties.
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 static field and properties from Python package like they were available in any language but invocation must be performed through Javonet SDK API.

Get/Set static field from custom Python package

With Javonet it is possible to reference any custom Python package and interact with public static fields and properties declared on types defined within that module almost the same as with any other any language library.

Snippet below represents the sample code from Python package which contains class with fields:

class TestClass:
    def __init__(self, public_value, private_value):
        self.public_value = public_value
        self.private_value = private_value

    static_value = 3
static_value = 3

It is possible to get one of the declared static fields from Python package using following any language code.

This uses in memory runtime bridging to load the Python package, and next retrieves reference to specific type and gets the static field. Result of the invocation is returned as regular any language value and can be used for further processing. It is possible to set one of the declared static fields from Python package using following any language code.

This uses in memory runtime bridging to load the Python package, and next retrieves reference to specific type, then sets and gets the static field. Result of the invocation is returned as regular any language value and can be used for further processing.

Get/Set static field from standard Python package

The same steps are required to get types and fields from framework Python package:

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 Python package 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.