[ 
https://issues.apache.org/activemq/browse/SMXCOMP-564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=52200#action_52200
 ] 

Jean-Baptiste Onofré commented on SMXCOMP-564:
----------------------------------------------

I have more understood what it happens exactly.

In fact, the real problem was in my xbean.xml where I use the following 
endpoint definition:
fsb:exchange-rate-soap

For the component, the endpoint is simply a string. The component manages the 
namespace in the service definition (as the service is managed as a QName), but 
the endpoint is simply a string. So basicly, the endpoint doesn't (and 
should't) contain any namespace and prefix.

Basicly, to fix my issue, I have simply change my xbean.xml endpoint as follow:
exchange-rate-soap (without the prefix)

and the WSDL is now valid.

Anyway, I think it can be interesting to raise an exception (or bypass defined 
character) in the HTTP endpoint validate() method.

> Incorrectly generated WSDL
> --------------------------
>
>                 Key: SMXCOMP-564
>                 URL: https://issues.apache.org/activemq/browse/SMXCOMP-564
>             Project: ServiceMix Components
>          Issue Type: Bug
>    Affects Versions: servicemix-http-2008.01
>         Environment: ServiceMix 3.3
> JVM Sun 1.5.0_14
> Linux Debian (2.6.27)
>            Reporter: Jean-Baptiste Onofré
>
> An incorrect WSDL is generated using a HTTP endpoint combined with a CXF-SE 
> one.
> The namespace prefix in the xbean.xml service name is used as-is in the 
> generated WSDL.
> For example, I have the following xbean.xml:
> <http:endpoint service="fsb:exchange-rate-http"
>            endpoint="fsb:exchange-rate-soap" [...]/>
> is translated in:
>  <wsdl:port binding="tns:fsb:exchange-rate-soapBinding" 
> name="fsb:exchange-rate-soap" [...]/>
> So I have:
> 1/ tns:fsb:xxx is not a valid namespace format.
> 2/ the fsb namespace is not even declared in the generated WSDL 
> The problem is certainly in HttpEndpoint#overrideDefinition() or 
> PortTypeDecorator#decorate().

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

Reply via email to