On 18 Jan 2012, at 7:30 PM, Steve Ebersole wrote:
> 2) The way this is currently implemented, using JPA now has a dependency
> on the CDI API being available on the classpath. We need to decide if
> that is unreasonable. The other option is to handle it like we do for
> BeanValidation and us
Also, I have been thinking that there really ought to be different
types of "integrators". Not sure what we gain by forcing
MetadataContributingIntegrator, ServiceContributingIntegrator,
TypeContributingIntegrator, etc to extend Integrator
On Sat 18 Aug 2012 05:50:29 PM CDT, Steve Ebersole wr
This ties together a few different discussions that have been going on
simultaneously on the mailing list that I think are all related.
Right now to configure certain services (select one impl over another)
users generally give the FQN for that impl Class. For example to use
C3P0 connection po
reuse the IntegratorService / ServiceLoader ?
On Aug 21, 2012, at 2:14 AM, Steve Ebersole wrote:
> Also, I have been thinking that there really ought to be different types of
> "integrators". Not sure what we gain by forcing
> MetadataContributingIntegrator, ServiceContributingIntegrator,
>
