camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gert-Jan van de Streek (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CAMEL-1848) MockEndPoint yields nullpointer due to mixed up typeconversion
Date Thu, 23 Jul 2009 13:40:33 GMT

     [ https://issues.apache.org/activemq/browse/CAMEL-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Gert-Jan van de Streek updated CAMEL-1848:
------------------------------------------

    Attachment: FixedMockEndPoint.java

The FixedMockEndPoint is a fix/patch. It has some extra code in it, because the values we
needed from MockEndPoint are private. 

I would strongly suggest to look at the naming of the variables (both arguments and local
variables) used in the method expectedHeaderReceived. They were very confusing. I have now
been very explicit in the naming, even a bit overdone, but it clears the fog.

> MockEndPoint yields nullpointer due to mixed up typeconversion
> --------------------------------------------------------------
>
>                 Key: CAMEL-1848
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1848
>             Project: Apache Camel
>          Issue Type: Bug
>    Affects Versions: 2.0-M2
>            Reporter: Gert-Jan van de Streek
>         Attachments: FixedMockEndPoint.java
>
>   Original Estimate: 4 hours
>  Remaining Estimate: 4 hours
>
> MockEndpoint yields a failed unit test with very confusing message:
>         resultEndpointHub.expectedHeaderReceived("portalId", 30);
> Yields: ... expected <null> but got ...
> Of course the expected value of null must never happen if a value is put in there

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


Mime
View raw message