On Thu., Apr. 22, 2021, 9:46 a.m. Raymond Augé, <raymond.a...@liferay.com> wrote:
> @ServiceProvider is just a hint no? > > It does not change the implementation behavior... Unless you've found > otherwise, which would be surprising. > To be clear, there is no runtime behavior associated with @ServiceProvider _unless_ you are running tomcat in OSGi, which would bring in the Service Loader Mediator to handle the SPI call, BUT still would not change to logic around using a fallback impl if so coded. > Ray > > On Thu., Apr. 22, 2021, 9:29 a.m. Romain Manni-Bucau, < > rmannibu...@gmail.com> wrote: > >> Hi all, >> >> Websocket server configurator uses the SPI to load the impl and if not >> found fallbacks on the hardcoded tomcat default. >> Isn't the SPI intended to override the default and >> therefore @ServiceProvider breaks this feature? >> If not, how to override it globally without doing it on a per endpoint >> basis? >> >> Romain Manni-Bucau >> @rmannibucau <https://twitter.com/rmannibucau> | Blog >> <https://rmannibucau.metawerx.net/> | Old Blog >> <http://rmannibucau.wordpress.com> | Github < >> https://github.com/rmannibucau> | >> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book >> < >> https://www.packtpub.com/application-development/java-ee-8-high-performance >> > >> >
