|
|
|
|
Re: scout + springdata jpa [message #1743969 is a reply to message #1743899] |
Wed, 21 September 2016 08:10 |
|
Hi,
thanks for the answer. So basically you are doing the manual mapping for every form/page when retrieving data via JPA? I had hoped that there was some kind of automatic way possible for this cumbersome tasks.
Have you ever heard of ModellMapper and tools like this? Would they be of some help?
Peter
|
|
|
Re: scout + springdata jpa [message #1746464 is a reply to message #1743899] |
Sat, 29 October 2016 17:31 |
|
Hi there,
Matthias Zimmermann wrote on Tue, 20 September 2016 13:19we are currently in the process of building such an example [1]. warning: it's still early stage. basically in this combination of Spring Boot (and Spring Data) and Scout we will only use a Scout client that is bundled with the Spring server (and not use a Scout server). so in this case form data objects are not useful and will not be used. instead, model data will be manually mapped to form fields in the form handlers.
- form data objects are driven by the form design (the ui perspective) and are meant to serve as communication objects between the Scout client and server
- jpa entities are usually derived from the business model (the business perspective) and only in trivial cases the two perspectives are a good match
- typically, some manual mapping from the model needs to be done to the forms/pages/...
[1] https://github.com/BSI-Business-Systems-Integration-AG/SpringBoot-and-EclipseScout
I looked at the code @github and I wondered, where the magic happens, where the Scout UI is called instead of Controller methods by Spring Boot?
Can someone please shed light on this topic for me?
Thanks
Peter
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03888 seconds