[jboss-jira] [JBoss JIRA] Commented: (JBREM-723) BisocketClientInvoker.transport() needs to distinguish between push and pull callback connections
Ron Sigal (JIRA)
jira-events at lists.jboss.org
Sun Mar 11 17:18:49 EDT 2007
[ http://jira.jboss.com/jira/browse/JBREM-723?page=comments#action_12355770 ]
Ron Sigal commented on JBREM-723:
---------------------------------
transport() now checks for the presence of an InvokerLocator in the ADDLISTENER InvocationRequest, which indicates that a push callback connection is being created.
Added unit test to org.jboss.test.remoting.transport.bisocket.BisocketTestCase.
Waiting for cruisecontrol results.
> BisocketClientInvoker.transport() needs to distinguish between push and pull callback connections
> -------------------------------------------------------------------------------------------------
>
> Key: JBREM-723
> URL: http://jira.jboss.com/jira/browse/JBREM-723
> Project: JBoss Remoting
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 2.2.0.Beta1 (Bluto)
> Reporter: Ron Sigal
> Assigned To: Ron Sigal
> Fix For: 2.2.0.Beta1 (Bluto)
>
>
> When BisocketClientInvoker.transport() detects an ADDLISTENER internal invocation, it asks the related callback BisocketServerInvoker to create a control connection. But for a pull callback connection, there is no callback BisocketServerInvoker.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list