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

Specify the various Scope subtype's lifecycle in their Javadoc #13496

Closed
24 tasks done
lukaseder opened this issue Apr 27, 2022 · 0 comments
Closed
24 tasks done

Specify the various Scope subtype's lifecycle in their Javadoc #13496

lukaseder opened this issue Apr 27, 2022 · 0 comments

Comments

@lukaseder
Copy link
Member

lukaseder commented Apr 27, 2022

By now, we have numerous Scope types in our API. They all have a different lifecycle, and thus a different meaning of:

In order to have predictable behaviour in implementations and when interacting with those scopes, we should clearly specify their lifecycles in the relevant Javadocs.

The list will be amended:

  • BindingScope (see Add BindingScope, a common super type of the various BindingXYZContext types #13497)
    • BindingSQLContext
    • BindingGetResultSetContext
    • BindingGetSQLInputContext
    • BindingGetStatementContext
    • BindingRegisterContext
    • BindingSetSQLOutputContext
    • BindingSetStatementContext
  • CacheContext
  • Context
    • BindContext
    • RenderContext
  • DSLContext
    • CloseableDSLContext
  • ExecuteContext
  • ExecuteScope
  • GeneratorContext
  • Meta
  • Migration
  • ParseContext
  • RecordContext
  • ResourceManagingScope
  • TransactionContext
  • VisitContext
@lukaseder lukaseder added this to the Version 3.17.0 milestone Apr 27, 2022
lukaseder added a commit that referenced this issue Apr 27, 2022
lukaseder added a commit that referenced this issue Apr 27, 2022
- Context
- DSLContext
- ExecuteContext
- GeneratorContext
- Meta
- Migration
- MigrationContext
- RecordContext
- ResourceManagingScope
- TransactionContext
- VisitContext
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant