[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [jetty-users] How to prevent No Spring WebApplicationInitializer types detected on classpath?
|
On Wed, Oct 2, 2013 at 4:51 PM, Joakim Erdfelt <joakim@xxxxxxxxxxx> wrote:
> 2) JSR-356 javax.websocket @ServerEndpoint and ServerApplicationConfig
> support.
> When you have websocket endpoints in the mix, they have to be scanned
> for in order to be installed.
This should be more qualified. There is a programmatic registration
alternative. Specifically through the WebSocketContainer's addEndpoint
methods. Ideally it should be possible to turn off the SCI scan
completely (through <absolute-ordering/> in web.xml) and still be able
register WebSocket endpoints.
For example the Spring Framework provides a ServerEndpointExporter
that, when added to the Spring configuration can register specific
endpoints on behalf of the application, as an alternative to the SCI
scan. I can imagine other frameworks could provide similar options.
Rossen