Skip to content

Conversation

@bstansberry
Copy link
Contributor

@bstansberry bstansberry commented Nov 30, 2025

https://issues.redhat.com/browse/WFLY-21081

This is just a draft. But aside from a couple details I'll mention below, this is what I'm thinking to do for this. It's basically the todo-backend quickstart but with a different persistence layer. The todo-backend QS seems like a perfectly good one for showing a REST CRUD app, and duplicating it makes it easy to see how using Jakarta Data is different from using Jakarta Persistence.

Right now it uses WildFly Preview and doesn't use Glow. Both of these things relate to the fact that Jakarta Data is currently 'preview' stability. The intent of this PR is to satisfy a requirement for moving that to 'community' so when that happens I'd update this PR to use the normal feature pack and use Glow.

@scottmarlow FYI.

@emmartins
Copy link
Contributor

@bstansberry FYI no need to update any README.adoc, those are rebuilt if the related README-source.adoc is changed. You can keep such changes tho, no issue with that.

@bstansberry
Copy link
Contributor Author

True. I built that locally because I wanted to read the html page, and then forgot and added that to the commit.


By default, it exposes a single datasource.
In the backend, the name of this datasource is `ToDos` and is specified in the `persistence.xml` to configure JPA:
In the backend, the name of this datasource is `ToDoRepository` and is specified in the `persistence.xml` to configure JPA:
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Oops; it seems I made an edit to the wrong file. And even in the todo-jakarta-data QS this isn't correct.

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.

2 participants