For me, too. I mainly added this as hub for our discussions around this.
Still not sure whether we want this additional dependency.
I think we could make this optional. If meta data providers were pluggable (e.g. using java.util.ServiceLoader), the engine would just use those providers available. And only if the Jandex provider is around it would be used (and that module would have a dependency to the Jandex lib).
Also how much do we really gain?
I think it would only be worth if we could reuse the existing index from the container. In that case it should help performance-wise.
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
For me, too. I mainly added this as hub for our discussions around this.
I think we could make this optional. If meta data providers were pluggable (e.g. using java.util.ServiceLoader), the engine would just use those providers available. And only if the Jandex provider is around it would be used (and that module would have a dependency to the Jandex lib).
I think it would only be worth if we could reuse the existing index from the container. In that case it should help performance-wise.