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

Need Jetty impl of org.jboss.weld.environment.deployment.discovery.DiscoveryStrategy #199

Closed
jmcc0nn3ll opened this issue Feb 16, 2016 · 1 comment

Comments

@jmcc0nn3ll
Copy link
Contributor

migrated from Bugzilla #464330
status ASSIGNED severity normal in component cdi for 9.3.x
Reported in version 9.3.0 on platform All
Assigned to: Jan Bartel

On 2015-04-09 16:42:36 -0400, Joakim Erdfelt wrote:

The weld DiscoveryStrategy is the interface that weld uses to obtain bytecode class scanning information from the classpath.

There is a default implementation found at
org.jboss.weld.environment.deployment.discovery.ReflectionDiscoveryStrategy

which uses your standard bytecode scanning, in a similar way that Jetty does.

And there's also a Jandex specific implementation found at
org.jboss.weld.environment.deployment.discovery.jandex.JandexDiscoveryStrategy

We should strive to create a JettyDiscoveryStrategy that utilizes the information that Jetty knows, including any information obtained from quickstart.

On 2015-04-09 16:43:14 -0400, Joakim Erdfelt wrote:

We'll need to submit a patch to weld against

org.jboss.weld.environment.deployment.discovery.DiscoveryStrategyFactory

so we can pick our own implementation.

@jmcc0nn3ll jmcc0nn3ll added the Bug For general bugs on Jetty side label Feb 16, 2016
@joakime joakime added Enhancement Help Wanted and removed Bug For general bugs on Jetty side labels Feb 17, 2016
@joakime joakime removed their assignment Feb 17, 2016
@gregw
Copy link
Contributor

gregw commented Sep 11, 2019

Integration redone in #3804

@gregw gregw closed this as completed Sep 11, 2019
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

3 participants