[
https://issues.apache.org/activemq/browse/SM-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ron Gavlin reopened SM-1279:
----------------------------
At a minimum, I don't think the CXF-SE should throw a NPE in this case. A more
meaningful error that identifies that "CXF-SE targeting routing requires an
operation" would be more appropriate. Also, since the operation is usually
optional for JBI routing, shouldn't the CXF-SE be smarter about auto-selecting
the operation if possible?
- Ron
> CXF SE throws NPE on receipt of message from an EIP component
> -------------------------------------------------------------
>
> Key: SM-1279
> URL: https://issues.apache.org/activemq/browse/SM-1279
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-cxf-se
> Affects Versions: 3.2.1
> Reporter: Ron Gavlin
> Assignee: Freeman Fang
> Priority: Critical
>
> CXF SE throws NPE on receipt of message from an EIP component. In order to
> reproduce easily, modify the cxf-wsdl-first sample application by adding a
> servicemix-file SU with a poller/sender and a servicemix-eip:pipeline SU.
> Wire the file:poller to the eip:pipeline to both the cxf-se endpoint and the
> file:sender. Then create a file in the file:poller whose contents contains a
> jbi-wrapped cxf-wsdl-first request. The error generated is identical to the
> error generated by the following scenario: cxf-bc -> eip:staticRecipientList
> -> cxf-se. That scenario is described in the following mailing list entry
> http://www.nabble.com/cxfbc-eip-cxfse-problem-td16026202s12049.html.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
