Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Thu, 1 Sep 2011 20:47:10 +0000 (UTC)
From: "Hadrian Zbarcea (JIRA)" <jira@apache.org>
To: dev@camel.apache.org
Message-ID: 
 <1588349819.8338.1314910030053.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (CAMEL-4405) Invalid URIs used by camel-cxf
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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