Uploaded image for project: 'CXF'
  1. CXF
  2. CXF-3523

Ability to force java2wsdl approach for javaws:client even if wsdlLocation is set (via populateFromClass property or, at least, custom jaxws:serviceFactory) when using spring integration

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 2.2.12, 2.4, 2.3.4
    • Fix Version/s: None
    • Component/s: Configuration
    • Labels:
      None

      Description

      To put into context: There's "no way" (i think there's one using some spring 'tricks') of using java2wsdl with client endpoints along with ServiceContractResolver functionality (to access an UDDI registry, for example). When using ServiceContractResolver, the wsdlLocation property gets updated, and this property is later used to determine the approach to use when initializing the service model. The same occurs with server endpoints but, at least, a custom jaxws:serviceFactory can be configured with populateFromClass set to true (this flag is checked when deciding how to initialize the model).

      ┬┐Is there a reason for jaxws:client not having the ability to pass a custom serviceFactory like server does? If there's a good reason for that (it seems to me that maybe this is done voluntarily) ┬┐couldn't a populateFromClass property be added to jaxws:client and jaxws:server to handle this when instantiating the default serviceFactory?

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              albert.ruiz Albert Ruiz
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated: