[ 
https://issues.apache.org/jira/browse/CAMEL-4405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095712#comment-13095712
 ] 

Willem Jiang commented on CAMEL-4405:
-------------------------------------

"{" and "}" are not URI safe character, we did some work in Camel when it 
parsers endpoint URI to support it.
If you are passing the URI which is encoded to camel, you may face that kind of 
trouble. 
As most user don't do it, we don't get this kind of alarm before.
There is a question just comes into my mind, what if the user just pass a URI 
which is not encoded with UTF-8, or it is not be encoded.


> Invalid URIs used by camel-cxf
> ------------------------------
>
>                 Key: CAMEL-4405
>                 URL: https://issues.apache.org/jira/browse/CAMEL-4405
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-cxf
>    Affects Versions: 2.8.0
>            Reporter: Hadrian Zbarcea
>            Assignee: Hadrian Zbarcea
>            Priority: Critical
>             Fix For: 2.9.0
>
>
> This is a nasty one.
> We currently support URIs of the following form in camel-cxf:
> {code}
> "cxf://http://localhost:9000/CxfEndpointTest/helloworld?wsdlURL=classpath:person.wsdl&serviceName={http://camel.apache.org/wsdl-first}PersonService&portName={http://camel.apache.org/wsdl-first}soap";
> {code}
> As curly brackets are not valid, URIs like above are invalid. Unfortunately I 
> suspect there are too many users who use this format now to just fix it so we 
> need to deprecate this format, find a workaround and a solution.
> The solution I am proposing is to use another parameter: targetNamespace to 
> replace the value between the curlies for the serviceName. The portName 
> should not be a QName actually either. As such, the example above would 
> become:
> {code}
> "cxf://http://localhost:9000/CxfEndpointTest/helloworld?wsdlURL=classpath:person.wsdl&targetNamespace=http://camel.apache.org/wsdl-first&serviceName=PersonService&portName=soap";
> {code}
> I will look for a workaround too, to not break existing code too much.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to