JUDO Dispatcher Architecture FAQs

Question 1

Can I intercept operation calls in the JUDO runtime?

Accepted Answer

Yes, by implementing the OperationCallInterceptor, you can define logic that runs during the preCall and postCall phases of any dispatched operation.

Question 2

How are transactions managed in this architecture?

Accepted Answer

The Dispatcher manages transactions via Spring's PlatformTransactionManager, opening a transaction before an operation and committing it after successful execution and interceptor processing.

Question 3

What is the JUDO Dispatcher?

Accepted Answer

The JUDO Dispatcher is the central routing component that handles all operation calls, routing them to behavior, script, or SDK handlers while managing interceptors and transactions.

Question 4

How do I extend JUDO with custom variables?

Accepted Answer

You can implement the EnvironmentVariableProvider interface to add custom variables to the expression context, which are then resolved by the VariableResolverManager.

Question 5

What are the built-in CRUD handlers available?

Accepted Answer

JUDO includes several built-in handlers for standard operations, including CreateInstanceCall, UpdateInstanceCall, DeleteInstanceCall, ListCall, and RefreshCall.

JUDO Dispatcher Architecture

Key Features

Use Cases

JUDO Dispatcher Architecture

Key Features

Use Cases