Spring Boot: fix test _entityClass_ResourceIT.java.ejs for composed types with OneToOne and @MapsId (eg when extending User)

[mux-R]

See Issue #29901

Suggested changes

In the file test _entityClass_ResourceIT.java.ejs, I noticed that it's generating the name of the setter with:

mapsIdAssoc.otherEntityNameCapitalized

It's using the class name from the other entity (in this case User) when generating the name for the setter method. Which only works if the field/setter has the same name as the class. However, in my case (and in the case shown in the documentation for extending a user https://www.jhipster.tech/user-entity/ ): The field is called internalUser and the class is called User.

I tried to find something containing InternalUser (case-sensitive) and found the following possibilities:

• mapsIdAssoc.relationshipNameCapitalized
• mapsIdAssoc.propertyNameCapitalized
• mapsIdAssoc.propertyJavaBeanName
  All of these 3 options contained InternalUser. I'm not sure about the exact meanings of each.

My proposed fix is to use:

mapsIdAssoc.propertyNameCapitalized

Testing

I tested my changes from this commit locally (by using npm ci and setting an alias) and am now receiving Spring Boot (Java) code which compiles successfully. I started the application and verified that the entities are visible via the GUI. However, I haven't yet thoroughly tested my new composed types. I'm assuming that it works because it's something that's mentioned in the documentation. But I will be trying to use it (run-time) anyway in the near future because I want to use it.

I haven't written any automated test for it. I might look into that if it's required. However I'm not sure if I'm able to figure out where to put such a test or which kind of test to write.

---

Please make sure the below checklist is followed for Pull Requests.

• All continuous integration tests are green
• Tests are added where necessary
• The JDL part is updated if necessary
• jhipster-online is updated if necessary
• Documentation is added/updated where necessary
• Coding Rules & Commit Guidelines as per our CONTRIBUTING.md document are followed

When you are still working on the PR, consider converting it to Draft (below reviewers) and adding skip-ci label, you can still see CI build result at your branch.

[Tcharl]

I would have use beanname personally, but never worked on mapsid. @OmarHawk maybe?