cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ed Bras (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CXF-4658) Support for WSDL with a Port name that is the same as the port name.
Date Wed, 28 Nov 2012 12:10:58 GMT
Ed Bras created CXF-4658:
----------------------------

             Summary: Support for WSDL with a Port name that is the same as the port name.
                 Key: CXF-4658
                 URL: https://issues.apache.org/jira/browse/CXF-4658
             Project: CXF
          Issue Type: Improvement
          Components: Core
    Affects Versions: 2.7.0
            Reporter: Ed Bras


Currently you can't use "easy configuration" with a wsdl that has a Service name that is the
same as the Port name.
With easy config I mean config like:
<jaxws:client name="{http://bla.nl/bla/}ServicePort">

Easy config has a lot of advantages when working with SSL and WS-Security in case the wsdl
contains all security infothrough WS-securityPolicy.

The old-fashion way of config is hard these days as not many people use it anymore, many things
changes and it's error sensitive.

I think the above name attribute in jaxws:client should get a suffix like ".port" (just like
with http:conduit) to ensure that it's "unique" and don't conflict with  other Spring config's
that like the Service Spring config.
For the exact details, see: http://stackoverflow.com/questions/13591514/how-to-deal-with-same-service-and-port-name-in-cxf

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message