Skip to main content

[jsr356-experts] Re: Server deployment

  • From: Greg Wilkins < >
  • To:
  • 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
deployment.

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.

cheers


-- 
Greg Wilkins 
< >
http://www.webtide.com
Developer advice and support from the Jetty & CometD experts.


[jsr356-experts] Server deployment

Danny Coward 11/28/2012

[jsr356-experts] Re: Server deployment

Mark Thomas 11/28/2012

[jsr356-experts] Re: Server deployment

Greg Wilkins 11/29/2012

[jsr356-experts] Re: Server deployment

Scott Ferguson 11/29/2012

[jsr356-experts] Re: Server deployment

Danny Coward 11/29/2012

[jsr356-experts] Re: Server deployment

Mark Thomas 11/30/2012

[jsr356-experts] Re: Server deployment

Rémy Maucherat 11/30/2012

[jsr356-experts] Re: [jsr356-users] Re: Server deployment

Jitendra Kotamraju 11/30/2012

[jsr356-experts] Re: [jsr356-users] Re: Server deployment

Mark Thomas 11/30/2012
 
 
Close
loading
Please Confirm
Close