Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 356693

Summary:	Too much of the websocket implementation is exposed to the webapp
Product:	[RT] Jetty	Reporter:	Greg Wilkins <gregw>
Component:	server	Assignee:	Simone Bordet <simone.bordet>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	jetty-inbox
Version:	7.5.0
Target Milestone:	7.5.x
Hardware:	PC
OS:	Linux
Whiteboard:

Description Greg Wilkins

2011-09-04 18:55:28 EDT

Only API classes should be exposed.

Comment 1 Greg Wilkins

2011-09-04 21:25:46 EDT

Simone,

I have committed a fix and tested briefly with cometd.war

can you confirm and resolve this issue if all is OK.

Comment 2 Greg Wilkins

2011-09-04 23:21:39 EDT

hmmm this appears to work for a cometd.war file, but not for the mvn jetty:run in cometd-demo ????

Comment 3 Simone Bordet

2011-09-05 07:48:17 EDT

I have removed WebSocketServlet to be a non-server class, because I think it should always be loaded by the webapp classloader.

I do not see any failure with jetty:run. Can you specify what errors you get ?

Comment 4 Simone Bordet

2011-09-22 06:12:24 EDT

Exposing only org.eclipse.jetty.websocket.WebSocket and org.eclipse.jetty.websocket.WebSocketFactory as system, non-server classes works fine for both war deployment and for the Jetty Maven Plugin.