{"action":"closed","issue":{"url":"https://api.github.com/repos/eclipse-ee4j/yasson/issues/260","repository_url":"https://api.github.com/repos/eclipse-ee4j/yasson","labels_url":"https://api.github.com/repos/eclipse-ee4j/yasson/issues/260/labels{/name}","comments_url":"https://api.github.com/repos/eclipse-ee4j/yasson/issues/260/comments","events_url":"https://api.github.com/repos/eclipse-ee4j/yasson/issues/260/events","html_url":"https://github.com/eclipse-ee4j/yasson/issues/260","id":432506509,"node_id":"MDU6SXNzdWU0MzI1MDY1MDk=","number":260,"title":"Turn JsonbComponentInstanceCreator into a service provider interface","user":{"login":"mkouba","id":913004,"node_id":"MDQ6VXNlcjkxMzAwNA==","avatar_url":"https://avatars1.githubusercontent.com/u/913004?v=4","gravatar_id":"","url":"https://api.github.com/users/mkouba","html_url":"https://github.com/mkouba","followers_url":"https://api.github.com/users/mkouba/followers","following_url":"https://api.github.com/users/mkouba/following{/other_user}","gists_url":"https://api.github.com/users/mkouba/gists{/gist_id}","starred_url":"https://api.github.com/users/mkouba/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mkouba/subscriptions","organizations_url":"https://api.github.com/users/mkouba/orgs","repos_url":"https://api.github.com/users/mkouba/repos","events_url":"https://api.github.com/users/mkouba/events{/privacy}","received_events_url":"https://api.github.com/users/mkouba/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":6,"created_at":"2019-04-12T10:51:50Z","updated_at":"2019-05-02T13:34:40Z","closed_at":"2019-05-02T13:34:40Z","author_association":"NONE","body":"So that an integrator could provide a custom implementation of this interface. `JsonbComponentInstanceCreatorFactory` currently contains some reflection magic to detect the presence of a CDI container. In fact, the presence of the CDI API is enough.\r\n\r\nI believe it would be reasonable to define this SPI. [Quarkus](https://github.com/quarkusio/quarkus) integration would definitely make use of it because our DI solution is compatible with CDI but we don't support all \"portable extensions related\" SPIs (they do not fit into our build time metadata processing approach) and so the invocation of  the `BeanManagerInstanceCreator#getOrCreateComponent()` fails."}}
{"actor":{"display_login":"bravehorsie"}}