[
https://issues.apache.org/jira/browse/CXF-6439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp resolved CXF-6439.
------------------------------
Resolution: Not A Problem
Fix Version/s: Invalid
Assignee: Daniel Kulp
If this is an issue in Wildfly, it would need to be logged with them.
However, you likely just need to add a wsdlLocation attribute to the
@WebService annotation on the "Impl.java". Basically, CXF would need some way
of locating the wsdl that is to be exposed. The annotation is one way.
"plain" cxf using spring or blueprint has properties in the spring/blueprint
xml. I don't know what Wildfly might have.
> MAVEN WSDL2Java - It does not expose original wsdl
> --------------------------------------------------
>
> Key: CXF-6439
> URL: https://issues.apache.org/jira/browse/CXF-6439
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime, JAXB Databinding, Tooling
> Affects Versions: 3.0.4
> Environment: OSX, Wildfly 9, JDK 7, Maven Plugin CXF WSDL2Java 3.0.4
> Reporter: JEANDERSON CRUZ NASCIMENTO
> Assignee: Daniel Kulp
> Labels: automation, build, maven
> Fix For: Invalid
>
> Attachments: TissFault.java, TissLoteGuias.java,
> TissLoteGuiasPortType.java, TissLoteGuiasPortTypeImpl.java, pom.xml,
> tissLoteGuiasGenered.wsdl, tissLoteGuiasV3_02_01.wsdl
>
>
> I created a webservice using maven plugin cxf wsdl2java.
> I did deploy in wildfly 9. The exposed wsdl is different from that used to
> create the service.
> How do I expose the original wsdl?
> Follows generated and implementation classes; and pom file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
