You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Tom Purcell (JIRA)" <ji...@apache.org> on 2008/04/09 14:51:32 UTC

[jira] Created: (SM-1309) SmxHttpExchange: Method intended to override HttpExchange not named correctly

SmxHttpExchange: Method intended to override HttpExchange not named correctly
-----------------------------------------------------------------------------

                 Key: SM-1309
                 URL: https://issues.apache.org/activemq/browse/SM-1309
             Project: ServiceMix
          Issue Type: Bug
          Components: servicemix-http
            Reporter: Tom Purcell


SmxHttpExchange overrides some of the onResponse... methods of org.mortbay.jetty.client.HttpExchange. One is not named correctly:

In HttpExchange the method is:
     onResponseHeader(Buffer name, Buffer value)
But in SmxHttpExchange the method is:
     onResponsetHeader(Buffer name, Buffer value)

Note the "t" in onResponsetHeader. As a result the empty HttpExchnage implementation gets called and we do not get the header. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (SM-1309) SmxHttpExchange: Method intended to override HttpExchange not named correctly

Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/SM-1309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Guillaume Nodet updated SM-1309:
--------------------------------

    Fix Version/s: servicemix-http-2008.01

> SmxHttpExchange: Method intended to override HttpExchange not named correctly
> -----------------------------------------------------------------------------
>
>                 Key: SM-1309
>                 URL: https://issues.apache.org/activemq/browse/SM-1309
>             Project: ServiceMix
>          Issue Type: Bug
>          Components: servicemix-http
>            Reporter: Tom Purcell
>            Assignee: Guillaume Nodet
>             Fix For: 3.2.2, 3.3, servicemix-http-2008.01
>
>
> SmxHttpExchange overrides some of the onResponse... methods of org.mortbay.jetty.client.HttpExchange. One is not named correctly:
> In HttpExchange the method is:
>      onResponseHeader(Buffer name, Buffer value)
> But in SmxHttpExchange the method is:
>      onResponsetHeader(Buffer name, Buffer value)
> Note the "t" in onResponsetHeader. As a result the empty HttpExchnage implementation gets called and we do not get the header. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (SM-1309) SmxHttpExchange: Method intended to override HttpExchange not named correctly

Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/SM-1309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Guillaume Nodet resolved SM-1309.
---------------------------------

         Assignee: Guillaume Nodet
    Fix Version/s: 3.2.2
                   3.3
       Resolution: Fixed

URL: http://svn.apache.org/viewvc?rev=646825&view=rev
URL: http://svn.apache.org/viewvc?rev=646830&view=rev


> SmxHttpExchange: Method intended to override HttpExchange not named correctly
> -----------------------------------------------------------------------------
>
>                 Key: SM-1309
>                 URL: https://issues.apache.org/activemq/browse/SM-1309
>             Project: ServiceMix
>          Issue Type: Bug
>          Components: servicemix-http
>            Reporter: Tom Purcell
>            Assignee: Guillaume Nodet
>             Fix For: 3.2.2, 3.3
>
>
> SmxHttpExchange overrides some of the onResponse... methods of org.mortbay.jetty.client.HttpExchange. One is not named correctly:
> In HttpExchange the method is:
>      onResponseHeader(Buffer name, Buffer value)
> But in SmxHttpExchange the method is:
>      onResponsetHeader(Buffer name, Buffer value)
> Note the "t" in onResponsetHeader. As a result the empty HttpExchnage implementation gets called and we do not get the header. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.