You have defined different Spring Boot profiles for your Java Domain Service service and want to activate one of them when deploying the service through an application composition project in order to apply a specific bunch of configurations.
In this document you can find some best practice code samples that might be helpful while writing code for Java domain service projects.
When working with Domain services mapping between api namespace and domain namespace is often needed, for example :
You already have an existing Java Domain service, you want to include unit testing for that service.
You want to disable security checks for REST endpoints or even the entire service in your project for a specific reason.
You have an already existing Java Domain Service and you want to retrieve root entities by complex filter criterias. To achieve this, the generated Repository class has to be extended.
You have designed API operations with more than just one resoponse to cover both the success and error case. In your implementation code you want to return a specific response body if an error happens.
Integrate Gen AI service into your Java application.
Integrate IBM WatsonX AI service into your Java application to summarize long texts.
Set up a WebSocket server in your Domain Java service using Java Stack 2.0 to enable real-time bidirectional communication.
To debug your Java Solution, you can debug them in a number of ways. JUnit is one of them, and using the docker images for the events locally is another method. For more info, please see here.
In order to integrate an event against Kafka, you need to publish an event to a Kafka topic.
You want to run Java services built with the Workbench locally by use of the tool mirrord.
Content on this page reflects earlier versions of the and will be updated soon.
Content on this page reflects earlier versions of the and will be updated soon.
Content on this page reflects earlier versions of the and will be updated soon.
Content on this page reflects earlier versions of the and will be updated soon.
Content on this page reflects earlier versions of the and will be updated soon.
Content on this page reflects earlier versions of the and will be updated soon.
Content on this page reflects earlier versions of the and will be updated soon.
Content on this page reflects earlier versions of the and will be updated soon.
Content on this page reflects earlier versions of the and will be updated soon.
Content on this page reflects earlier versions of the and will be updated soon.
Content on this page reflects earlier versions of the and will be updated soon.
Content on this page reflects earlier versions of the and will be updated soon.
Content on this page reflects earlier versions of the and will be updated soon.
You have a Domain Service Java project and want to do local debugging.
You already have an existing Spring Boot application which you want to transform to a Project to use the benefits of the Workbench.
You want to create robust data models that reflect the structure of relational databases using the .
An External Entity is considered a proxy of an entity that is managed by another microservice. Normally, the external entity contains only the most important data that is regularly needed in the context of the aggregate to which the external entity belongs. Because of these specifics, it is handled differently than a usual Entity.
Your have a service that only offers async communication, but you need to call it synchronously.
You want to design transaction-like behaviour using the SAGA pattern support in your Java Domain Service based project.
Goal: Enable and configure distributed tracing for REST calls, MongoDB operations, and Kafka events in Java stack 2.0 applications using OpenTelemetry with Jaeger.