/micronaut-json-issue

Primary LanguageJava

Micronaut JSON Issue

Trying to recreate an issue I’m experiencing with Micronaut parsing JSON from a POST body.

Running

To run the load tests

  1. cd jhipster-micronaut

  2. ./mvnw clean package

  3. java -jar target/jhipster-micronaut-0.0.1-SNAPSHOT.jar

  4. Open a second terminal

  5. cd loadtests

  6. ./gradlew gatlingRun --rerun-tasks

Detailed output from the load tests will be output in loadtests/gatling-output.log

jhipster-micronaut Application Details

The jhipster-micronaut folder contains an application generated with the WIP JHipster Micronaut generator.

Options used to generate the project

  1. "Monolithic Application"

  2. Webflux? N

  3. Name? jhipsterMicronaut

  4. Default Package? io.github.jhipster.sample

  5. Auth Type? JWT

  6. DB? SQL

  7. Production DB? MySQL

  8. Development DB? H2 in-memory

  9. Cache? ehcache

  10. Hibernate Cache? Y

  11. Build? Maven

  12. Other Technologies? empty

  13. Client Framework? Angular

  14. Bootswatch? Default JHipster

  15. Enable i18n? Y

  16. Native Language? english

  17. Additional Languages? none

  18. Other testing frameworks? none

  19. Other generators? N

After the project was generated, I generated the entities to match the sample application.

Note: I received errors when trying to set up entity relationships on the first pass, so instead I would create the initial entities in one pass and then add the relationships in a second pass.

Initial Entity Generation (Pass 1)

  1. mhipster entity BankAccount

  2. Add field name as String with validation rule Required

  3. Add field balance as BigDecimal with validation rule Required

  4. Rest Controller should use the repository directly

  5. Read only? N

  6. Pagination? N

  7. mhipster entity Label

  8. Add field label as String with validation rules Required and Minimum Length. Minimum length is 3.

  9. Rest Controller should use the repository directly

  10. Read only? N

  11. Pagination? N

  12. mhipster entity Operation

  13. Add field date as Instant with validation rule Required

  14. Add field description as String with no validation rules

  15. Add field amount as BigDecimal with validation rule Required

  16. Rest Controller should use the repository directly

  17. Read only? N

  18. Pagination? Infinite Scroll

Relationship Generation (Pass 2)

  1. mhipster entity BankAccount

  2. "Add more fields and relationships"

  3. ? Do you want to add a relationship to another entity? Yes

  4. ? What is the name of the other entity? user

  5. ? What is the name of the relationship? user

  6. ? What is the type of the relationship? many-to-one

  7. ? When you display this relationship on client-side, which field from 'user' do you want to use? This field will be displayed as a String, so it cannot be a Blob login

  8. ? Do you want to add any validation rules to this relationship? No

  9. ? Do you want to add a relationship to another entity? Yes

  10. ? What is the name of the other entity? operation

  11. ? What is the name of the relationship? operation

  12. ? What is the type of the relationship? one-to-many

  13. ? What is the name of this relationship in the other entity? bankAccount

  14. mhipster entity Label

  15. "Add more fields and relationships"

  16. ? Do you want to add a relationship to another entity? Yes

  17. ? What is the name of the other entity? operation

  18. ? What is the name of the relationship? operation

  19. ? What is the type of the relationship? many-to-many

  20. ? Is this entity the owner of the relationship? No

  21. ? What is the name of this relationship in the other entity? label

  22. mhipster entity Operation

  23. "Add more fields and relationships"

  24. ? Do you want to add a relationship to another entity? Yes

  25. ? What is the name of the other entity? bankAccount

  26. ? What is the name of the relationship? bankAccount

  27. ? What is the type of the relationship? many-to-one

  28. ? When you display this relationship on client-side, which field from 'bankAccount' do you want to use? This field will be displayed as a String, so it cannot be a Blob name

  29. ? Do you want to add any validation rules to this relationship? No

  30. ? Do you want to add a relationship to another entity? Yes

  31. ? What is the name of the other entity? label

  32. ? What is the name of the relationship? label

  33. ? What is the type of the relationship? many-to-many

  34. ? Is this entity the owner of the relationship? Yes

  35. ? What is the name of this relationship in the other entity? label

  36. ? When you display this relationship on client-side, which field from 'label' do you want to use? This field will be displayed as a String, so it cannot be a Blob label

  37. ? Do you want to add any validation rules to this relationship? No