camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <>
Subject [jira] Assigned: (CAMEL-2144) A null-Message to a cxf-endpoint (e.g. HTTP-GET) can disable accepting regular requests
Date Tue, 10 Nov 2009 06:35:52 GMT


Claus Ibsen reassigned CAMEL-2144:

    Assignee: Willem Jiang

Willem can you take a look at this later. I have attached a suggestion for a patch. The basic
idea is to return VOID when you cannot convert at this given time, such as when the MessageContextList
contains empty bodies etc.

You may want to work with it a bit and add some unit test, e.g. that send in a HTTP GET with
no XML data and then later do a real webservice call.

> A null-Message to a cxf-endpoint (e.g. HTTP-GET) can disable accepting regular requests
> ---------------------------------------------------------------------------------------
>                 Key: CAMEL-2144
>                 URL:
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-core, camel-cxf
>    Affects Versions: 2.0.0
>            Reporter: Jonny Newald
>            Assignee: Willem Jiang
>             Fix For: 2.1.0
>         Attachments: camel-2144.patch
> Start a fine configured system with came-cxf consumer endpoint using http. Make some
tests with valid SOAP-Messages. Then just send a HTTP-Get-Request to the endpoint (e.g. with
Browser). You'll get some kind of Exception saying
> java.lang.ClassCastException: org.apache.cxf.message.MessageContentsList cannot be cast
to org.w3c.dom.Node
> Ok, this could be interpreted as "There is no content to convert into Node..." as, if
you debug, you'll see, that an empty MessageContentsList is provided by camel-cxf as the body
of the camel message. Of course, if the Request would contain a body, the camel body would
be a non empty MessageContentsList and the type converter mechanism would find a way to convert
the list into a w3c Document, but that's not the point. The Bug is, that this null-body-request
puts the DefaultTypeConverter into a state, that let always return null for bodies of type
MessageContentsList, even if it's not empty (which is normal). I think that there is certain
'misses'-map responsible for that kind of 'miss'-state...

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

View raw message