[jboss-remoting-issues] [JBoss JIRA] Closed: (JBREM-1103) Correct javadoc for Client.invokeOneway()

[Ron Sigal (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBREM-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ron Sigal closed JBREM-1103.
----------------------------

    Resolution: Done


Updated the javadoc and also the oneway invocation example in the Remoting Guide.  Changes made to 2.2 and 2.x branches.

> Correct javadoc for Client.invokeOneway()
> -----------------------------------------
>
>                 Key: JBREM-1103
>                 URL: https://jira.jboss.org/jira/browse/JBREM-1103
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.5.0.SP2 (Flounder) , 2.2.2.SP11
>            Reporter: Ron Sigal
>            Assignee: Ron Sigal
>            Priority: Minor
>             Fix For: 2.5.0.SP3 (Flounder), 2.2.2.SP12
>
>
> The javadoc discussion on org.jboss.remoting.Client.invokeOneway() is no longer correct when the value of clientSide is false.  In particular, it is incorrect for the socket transport, since org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport() returns immediately after sending an invocation when it detects a oneway invocation.  This behavior has been true since the implementation of JBREM-548 "Support one way invocations with no response".

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