Using enum type

This article provides an introduction to cross-technology handling of enum type. In programming, an enum (short for enumeration) type is a special data type that enables for a variable to be a set of predefined constants. The variable must be equal to one of the values that have been predefined for it. Enums are used to create our own data types, just like classes. They are particularly useful when we want to represent a fixed set of constants, such as days of the week, states, colors, directions, and more. This makes the code more readable and less prone to errors.

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 enum types from any runtime as if they were available in Perl, but interaction must be performed through the Javonet SDK API. This allows you to handle and manipulate enum values, pass them to methods, and return them from methods, all while maintaining the type safety and readability of your Perl code.

Custom any runtime with enum type

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 Perl library.

Snippet below represents the sample code from any runtime which contains enum type.

Javonet SDK contains various methods to interact with enums and consume the results in Perl:

This snippet uses in memory runtime bridging to load the any runtime and next retrieves reference to specific enum type. Then two enum items are created. Their values and names are checked.

Enum items can be passed to any runtime method:

In this example, two enum items are created, too. Then array of enums is created and passed to method which adds enum items to list.

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.