[
https://issues.apache.org/jira/browse/CXF-3517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp resolved CXF-3517.
------------------------------
Resolution: Fixed
Fix Version/s: 2.4.1
Assignee: Daniel Kulp
We cannot use the URIResolver as, per spec, the generated code has to be
completely portable to other JAX-WS implementations. However, when generating
the code, if the wsdlLocation is classpath: variety, I changed the code for the
Service and client to be a bit smarter and use the classes classloader to try
and find the wsdl.
> Generated SoapService class doesn't accept classpath WSDL
> ---------------------------------------------------------
>
> Key: CXF-3517
> URL: https://issues.apache.org/jira/browse/CXF-3517
> Project: CXF
> Issue Type: Improvement
> Components: Tooling
> Affects Versions: 2.4
> Reporter: Igor Nikolaev
> Assignee: Daniel Kulp
> Priority: Minor
> Fix For: 2.4.1
>
>
> Currently {{ServiceGenerator}} generates SoapService classes using
> {{service.vm}} template that loads WSLD in static initializer block the
> following way:
> {code}
> static {
> URL url = null;
> try {
> url = new URL("$wsdlLocation");
> } catch (MalformedURLException e) {
> System.err.println("Can not initialize the default wsdl from
> $wsdlLocation");
> // e.printStackTrace();
> }
> WSDL_LOCATION = url;
> }
> {code}
> This doesn't allow to specify WSDL as classpath resource:
> classpath:path/to/wsdl/service.wsdl
> At the same time, WSDLToJava accepts above mentioned notation.
> I propose using existing {{URIResolver}} if appropriate and allow classpath
> WSDL
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
