[GitHub] [camel-quarkus] ppalaga commented on issue #4746: CXF generates different WSDL files with JVM/Native modes

["ppalaga (via GitHub)" <gi...@apache.org>]

ppalaga commented on issue #4746:
URL: https://github.com/apache/camel-quarkus/issues/4746#issuecomment-1509194372

   I am not finding any WSDL test in https://github.com/llowinge/camel-quarkus-examples/tree/cxf-soap-example/cxf-soap 
   Could you please add it there or even better directly in CQ under `integration-test-groups/cxf-soap/cxf-soap-server`?
   
   Along reviewing and polishing the [java2ws PR](https://github.com/quarkiverse/quarkus-cxf/pull/815) in QCXF I wrote a test that compares the WSDL produced by java2ws with the served one. 
   I can confirm that the two WSDLs were not equal unless I added `@WebService(name = "HelloService", serviceName = "HelloService")` to the service interface - that's for JVM mode. I also had to remove the `<soap:address location="">` node because the URL was set to some default `:9090` one in the java2ws document. 
   For native mode, I am seeing a correct document being served, but it is indeed slightly different than with JVM mode. The difference is in namespace prefixes. Where JVM has 
   
   `xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"` 
   
   native has 
   
   `xmlns:ns1="http://schemas.xmlsoap.org/wsdl/soap/"` 
   
   Then all occurrences of those prefixes also differ - e.g. 
   
   `<soap:binding .../>`
   
   vs. 
   
   `<ns1:binding .../>`
   
   This should not happen, but I would not say it is a serious bug. The native WSDL correct and mutatis mutandis also equal with the JVM one. 
   
   Is this what you also see in the quickstart?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org