On 25/03/2013 15:30, Nick Williams wrote: > > On Mar 25, 2013, at 10:01 AM, ma...@apache.org wrote: > >> Author: markt >> Date: Mon Mar 25 15:01:41 2013 >> New Revision: 1460700 >> >> URL: http://svn.apache.org/r1460700 >> Log: >> Fix https://issues.apache.org/bugzilla/show_bug.cgi?id=54740 >> Update SCI scan to reflect changes in spec >> >> Modified: >> tomcat/trunk/java/org/apache/tomcat/websocket/server/WsSci.java >> >> Modified: tomcat/trunk/java/org/apache/tomcat/websocket/server/WsSci.java >> URL: >> http://svn.apache.org/viewvc/tomcat/trunk/java/org/apache/tomcat/websocket/server/WsSci.java?rev=1460700&r1=1460699&r2=1460700&view=diff >> ============================================================================== >> --- tomcat/trunk/java/org/apache/tomcat/websocket/server/WsSci.java >> (original) >> +++ tomcat/trunk/java/org/apache/tomcat/websocket/server/WsSci.java Mon Mar >> 25 15:01:41 2013 >> @@ -16,6 +16,7 @@ >> */ >> package org.apache.tomcat.websocket.server; >> >> +import java.lang.reflect.Modifier; >> import java.util.HashSet; >> import java.util.Set; >> >> @@ -36,7 +37,7 @@ import javax.websocket.server.ServerEndp >> * server. >> */ >> @HandlesTypes({ServerEndpoint.class, ServerEndpointConfig.class, >> - ServerApplicationConfig.class}) >> + Endpoint.class}) > > How does Tomcat handle it (or even know?) when it comes across an Endpoint > class that's meant to be a client Endpoint, not a server Endpoint? Normally > you would use a client Endpoint with > WebSocketContainer#connectToServer(Endpoint, ClientEndpointConfig, URI) or > WebSocketContainer#connectToServer(Class<? extends Endpoint>, > ClientEndpointConfig, URI), but SCI will pick up client Endpoints as well as > server Endpoints cases with this change.
Read a little further down the class. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
