Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Exception Handling #45

Closed
rtpguru101 opened this issue Oct 5, 2022 · 2 comments
Closed

Exception Handling #45

rtpguru101 opened this issue Oct 5, 2022 · 2 comments

Comments

@rtpguru101
Copy link

Is there any reason why there is no exception handling in this entire template ?

@ogobrecht
Copy link
Member

We discussed this in the past, but we cannot decide for the developer, what should be done in the case of errors.

The first thing which will come to mind is logging, but which logging method/framework? We don't know what the developers are using for logging.

The second thing is, that the generated table APIs are very generic. You can use them to separate the data schema from the business logic schema. In more complex applications and/or data models we would expect that on top of these generic APIs developers build business APIs which are transaction save (the table APIs itself do not commit). In such business APIs (also called BAPI or XAPI) the developers are free to use a logging framework of their choice and do the exception handling depending on their needs.

Hopefully this answers your question.

Best regards
Ottmar

@rtpguru101
Copy link
Author

rtpguru101 commented Oct 23, 2022 via email

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

No branches or pull requests

2 participants