Skip to main content

[websocket-spec issues] [JIRA] Updated: (WEBSOCKET_SPEC-104) Session - javadoc/error reporting

  • From: "dannycoward (JIRA)" < >
  • To:
  • Subject: [websocket-spec issues] [JIRA] Updated: (WEBSOCKET_SPEC-104) Session - javadoc/error reporting
  • Date: Sat, 2 Feb 2013 02:33:53 +0000 (GMT+00:00)
  • Auto-submitted: auto-generated


     [ 
http://java.net/jira/browse/WEBSOCKET_SPEC-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

dannycoward updated WEBSOCKET_SPEC-104:
---------------------------------------

    Due Date: 08/Feb/13  (was: 25/Jan/13)

> Session - javadoc/error reporting
> ---------------------------------
>
>                 Key: WEBSOCKET_SPEC-104
>                 URL: http://java.net/jira/browse/WEBSOCKET_SPEC-104
>             Project: websocket-spec
>          Issue Type: Bug
>            Reporter: Pavel Bucek
>            Priority: Minor
>
> Session class documentation does not mention how it should work after 
> Session.close(...) is called. What should happen when Session.getRemote() 
> is called?
> Similar case can happen in annotated endpoint scenario - consider following:
> {code}        @WebSocketMessage
>         public String message(String message, Session session) {
>             try {
>                 session.close();
>                 return ...; // ???
>             } catch (IOException e) {
>             }
>             return "message";
>         }{code}
> line "return ...;" is important here.
> What should be returned?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://java.net/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


[websocket-spec issues] [JIRA] Updated: (WEBSOCKET_SPEC-104) Session - javadoc/error reporting

dannycoward (JIRA) 02/02/2013
 
 
Close
loading
Please Confirm
Close