[
https://issues.apache.org/jira/browse/CXF-3964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13180454#comment-13180454
]
Owen Farrell commented on CXF-3964:
-----------------------------------
It seems that this enhancement requires the WSDL to be added as an explicit
project dependency. But as a result, transitive dependencies end up being
unnecessarily included.
Here's an example scenario:
I implement a CXF-based web service (named hello-service). CXF will bring
Spring along for the ride. I attach the WSDL as a build artifact (using the
cxf-java2ws-plugin) as part of the build process (hello-service.wsdl).
When I create a web service client via the cxf-codegen-plugin (v2.5.1),
hello-service.wsdl now has to be included as a dependency. After adding the
WSDL as a dependency, Spring gets included as a transitive dependency, even
though my web service client only needs the JAX-WS API. And now my classpath is
bloated with all these libraries which (may) never get used.
> Codegen plugin tries to use classes dir as wsdl
> -----------------------------------------------
>
> Key: CXF-3964
> URL: https://issues.apache.org/jira/browse/CXF-3964
> Project: CXF
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.5
> Reporter: Benson Margulies
> Assignee: Benson Margulies
> Fix For: 2.5.1
>
>
> Under circumstances explained in MSITE-622, the maven-artifact-resolver comes
> up with a bogus answer to resolving the WSDL artifact, and returns a classes
> directory!
> At least, detect this and don't try to use it.
> Better, stop using that artifact-resolver component and call what it calls if
> that gets less ridiculous behavior.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
