[jsr356-experts] Re: Server deployment
- From: Greg Wilkins <
- Subject: [jsr356-experts] Re: Server deployment
- Date: Thu, 29 Nov 2012 18:33:15 +1100
I'm moderately phobic of automatic deployment of all discovered
endpoints. I frequently see WAR files with over 100 jars in
WEB-INF/lib and I can imagine the situation where some of these may
have websockets in them that are not know about. A developer could
then add a ServletContainerInitializer to enable his own websockets
and thus accidentally discover and deploy endpoints from some of the
other 99+ jars.
I understand that we don't want to put big hurdles in front of simple
I agree with Mark that the current mechanisms may not be that far off
and I think that bundling will be important. If the default
ServletContainerInitializer that scans and deploys everything is
packaged in a jar called something like
deploy-all-websockets-initializer.jar then it is pretty clear what
that is doing if it is in the WEB-INF lib.
I also agree with Danny that we should have a single mechanism that
works for programatic or POJO endpoints.
Developer advice and support from the Jetty & CometD experts.