[
https://issues.apache.org/jira/browse/CAMEL-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009195#comment-13009195
]
William Tam edited comment on CAMEL-3778 at 3/21/11 4:22 PM:
-------------------------------------------------------------
@Aki
I don't think the option is confusing (pls suggest a better name if you can
think of something) or unnecessary. Keep in mind that the proposed option is
specific for PAYLOAD mode only. You don't need set any options to send
arbitrary payloads if you are using MESSAGE mode (which I'd recommend and it is
faster).
In PAYLOAD mode, we need to make sure the XML message parts are properly added
to CXF Message Content List. So, obviously the check should be performed by
default. The "skipPayloadMessagePartCheck" option would allow users to put any
XML elements in the Message Content List if they desire (which I think it is an
abuse). Perhaps, explicit setting the option is a good way to document/remind
users that the endpoint will skip payload message part checking. Does it make
sense?
was (Author: wtam):
@Aki
I don't think the option is confusing (pls suggest a better name if you can
think of something) or unnecessary. Keep in mind that the proposed option is
specific for PAYLOAD mode only. You don't need set any options to send
arbitrary payloads if you are using MESSAGE mode (which I'd recommend and it is
faster).
In PAYLOAD mode, we need to make sure the XML message parts are properly added
to CXF Message Content List. So, obviously the check should be performed by
default. The "skipPayloadMessagePartCheck" option would allow users to put any
XML elements in the Message Content List if they desire (which I think it is an
abuse). Perhaps, explicit setting the option is a good way to document/remind
users that the endpoint will skip payload message part checking. Do it make
sense?
> Support CXF Dispatch mode at CXF Endpoints
> ------------------------------------------
>
> Key: CAMEL-3778
> URL: https://issues.apache.org/jira/browse/CAMEL-3778
> Project: Camel
> Issue Type: New Feature
> Components: camel-cxf
> Affects Versions: 2.6.0
> Reporter: Aki Yoshida
> Assignee: William Tam
> Fix For: 2.8.0
>
> Attachments: CAMEL-3386.patch, CAMEL-3778.patch, patch-20110310.txt,
> tests.zip
>
>
> Hi,
> Sometime ago I asked in this mailing list whether it is possible to use the
> dispatch mode of CXF in the Camel's CXF endpoint. The answer was no. But I
> wanted to have the CXF dispatch mode so that I can run SOAP
> intermediary/gateway scenarios with CXF features enabled and send arbitrary
> SOAP messages from a single endpoint.
> Now I have implemented this feature and I would like to hear what you think.
> In short, I modified CxfSpringEndpoint and CxfEndpoint so that Camel uses the
> CXF dispatch mode when no service class nor WSDL is specified in the endpoint
> configuration. For example, you can configure the endpoint as:
> {code:xml}
> <cxf:cxfEndpoint id="serviceEndpoint"
> address="http://localhost:9000/SoapContext/GreeterPort";
> endpointName="s:GreeterPort"
> serviceName="s:GreeterService"
> bus="#bus">
> <cxf:properties>
> <entry key="dataFormat" value="PAYLOAD"/>
> </cxf:properties>
> </cxf:cxfEndpoint>
> {code}
> In this case, the endpoint is set up for the dispatch mode. The dispatch mode
> supports two operations Invoke and InvokeOneWay and the default operation is
> Invoke. You can change the operation by simply setting the camel header
> operationName.
> I added two unit tests classes to show how the dispatch mode works for both
> PAYLOAD and MESSAGE data format.
> I am attached all the file to this ticket. I would appreciate if you can
> comment on this feature.
> Thanks.
> Regards, Aki
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
