|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
Regarding the IdentityStore.setup(). Let's say someone needs a specific JPA implementation for their needs, ours does not fit the requirements. During the store's initialization he needs to perform some checks/add some data before start using it.
How can he do that ? Do it at first invocation ?
I understand the SecurityContext is per-request and the store is shared by all requests, but IMO this does not block us to use it during the setup. Think about the JPA store when used in a container.