Skip to content

Conversation

@navaneethsnair1
Copy link
Contributor

Draft blog: https://blogs-draft-openlibertyio.mqj6zf7jocq.us-south.codeengine.appdomain.cloud/blog/2025/11/18/25.0.0.12-beta.html

Could you please check with this blog and let me know the review comments. Thank you!



* <<springboot, SpringBoot 4.0>>
* <<data1.1, Early preview of Jakarta Data 1.1>>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The link for this on the draft server doesn't go anywhere. Maybe it is confused by the . character?
Early preview of Jakarta Data 1.1

// // // // // // // //
[#data1.1]
== Early preview of Jakarta Data 1.1
This release reviews three new features of Jakarta Data 1.1: retrieving a subset or projection of entity attributes, the `@Is` annotation, and `Constraint` subtype parameters for repository methods that apply basic constraints to repository `@Find` and `@Delete` operations.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
This release reviews three new features of Jakarta Data 1.1: retrieving a subset or projection of entity attributes, the `@Is` annotation, and `Constraint` subtype parameters for repository methods that apply basic constraints to repository `@Find` and `@Delete` operations.
This release previews three new features of Jakarta Data 1.1: retrieving a subset or projection of entity attributes, the `@Is` annotation, and `Constraint` subtype parameters for repository methods that apply basic constraints to repository `@Find` and `@Delete` operations.

== Early preview of Jakarta Data 1.1
This release reviews three new features of Jakarta Data 1.1: retrieving a subset or projection of entity attributes, the `@Is` annotation, and `Constraint` subtype parameters for repository methods that apply basic constraints to repository `@Find` and `@Delete` operations.

Previously, repository methods couldn't limit retrieval of results to subsets of entity attributes (commonly referred to as projections). Now, repository methods can return Java records that represent a subset of an entity. In addition, parameter-based `@Find` and `@Delete` methods earlier were not able to filter on conditions other than equality. Now more advanced filtering can be done in two different ways: typing the repository method parameter with a `Constraint` subtype or indicating the `Constraint` subtype by using the `@Is` annotation.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is very minor, but within this same paragraph, the , character is included after Previously, and Now, in two other places, and is not consistent here. In case that matters, here is the correction,

Suggested change
Previously, repository methods couldn't limit retrieval of results to subsets of entity attributes (commonly referred to as projections). Now, repository methods can return Java records that represent a subset of an entity. In addition, parameter-based `@Find` and `@Delete` methods earlier were not able to filter on conditions other than equality. Now more advanced filtering can be done in two different ways: typing the repository method parameter with a `Constraint` subtype or indicating the `Constraint` subtype by using the `@Is` annotation.
Previously, repository methods couldn't limit retrieval of results to subsets of entity attributes (commonly referred to as projections). Now, repository methods can return Java records that represent a subset of an entity. In addition, parameter-based `@Find` and `@Delete` methods earlier were not able to filter on conditions other than equality. Now, more advanced filtering can be done in two different ways: typing the repository method parameter with a `Constraint` subtype or indicating the `Constraint` subtype by using the `@Is` annotation.

}
```

The first half of the static metamodel class includes constants for each of the entity attribute names so that you don't need to otherwise hardcode string values into your application. The rest half of the static metamodel class provides a special instance for each entity attribute, from which you can build restrictions and sorting to apply to queries at run time.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The first half of the static metamodel class includes constants for each of the entity attribute names so that you don't need to otherwise hardcode string values into your application. The rest half of the static metamodel class provides a special instance for each entity attribute, from which you can build restrictions and sorting to apply to queries at run time.
The first half of the static metamodel class includes constants for each of the entity attribute names so that you don't need to otherwise hardcode string values into your application. The second half of the static metamodel class provides a special instance for each entity attribute, from which you can build restrictions and sorting to apply to queries at run time.


* link:https://jakarta.ee/specifications/data/1.1/apidocs[Jakarta Data 1.1 API Javadoc]
* link:https://jakarta.ee/specifications/data/1.1/jakarta-data-1.1.0-m1[Jakarta Data 1.1 specification]
* link:https://jakarta.ee/specifications/data/1.1/[Jakarta Data 1.1 overvi ew page]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* link:https://jakarta.ee/specifications/data/1.1/[Jakarta Data 1.1 overvi ew page]
* link:https://jakarta.ee/specifications/data/1.1/[Jakarta Data 1.1 overview page]

}
```

Following is an example of the repository and static metamodel being used.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Following is an example of the repository and static metamodel being used.
The following is an example of the application using the repository and static metamodel.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Acrolinx suggested 'See the following example of the application that uses the repository and static metamodel.'

Copy link
Member

@njr-11 njr-11 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added review comments for the Jakarta Data 1.1 section. It's likely that many of these are my own grammar mistakes and were copied from the issue I originally opened for this. I didn't notice them until re-reading it on the preview. Sorry about that.

== SpringBoot 4.0
Open Liberty currently supports running Spring Boot 1.5, 2.x, and 3.x applications. With the introduction of the new `springBoot-4.0` feature, users can now deploy Spring Boot 4.x applications by enabling this feature. While Liberty consistently supports Spring Boot applications packaged as `WAR` files, this enhancement extends support to both `JAR` and `WAR` formats for Spring Boot 4.x applications.

The springBoot-4.0 feature provides a complete support for running a Sprint Boot 4.x application on Open Liberty as well as having the capability to thin the application when creating applications in containers.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you please remove a before complete like below

Suggested change
The springBoot-4.0 feature provides a complete support for running a Sprint Boot 4.x application on Open Liberty as well as having the capability to thin the application when creating applications in containers.
The springBoot-4.0 feature provides complete support for running a Sprint Boot 4.x application on Open Liberty as well as having the capability to thin the application when creating applications in containers.


The springBoot-4.0 feature provides a complete support for running a Sprint Boot 4.x application on Open Liberty as well as having the capability to thin the application when creating applications in containers.

To use this feature, the user must be running `Java 17` or later with EE11 features enabled. If the application uses servlets, it must be configured to use `Servlet 6.1`. Include the following features in your `server.xml` file to define settings.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you please add the before settings like below

Suggested change
To use this feature, the user must be running `Java 17` or later with EE11 features enabled. If the application uses servlets, it must be configured to use `Servlet 6.1`. Include the following features in your `server.xml` file to define settings.
To use this feature, the user must be running `Java 17` or later with EE11 features enabled. If the application uses servlets, it must be configured to use `Servlet 6.1`. Include the following features in your `server.xml` file to define the settings.

@habiblawal1
Copy link
Member

I'm happy with the MCP section

@navaneethsnair1 navaneethsnair1 merged commit 7f1d685 into staging Nov 17, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants