[
https://issues.jboss.org/browse/JBIDE-13414?page=com.atlassian.jira.plugi...
]
Brian Fitzpatrick commented on JBIDE-13414:
-------------------------------------------
I've uploaded what I see with the latest tooling in Luna when I try to generate the
Web Services Client. The error dialog is very prominent and offers an exception trace as
to the actual issue. (This is trying to do a Client using Tomcat and Axis, since we
don't have the specific combination to test in the initial bug report.)
That seems pretty specific and helpful. It's tough to generate a client for an
inaccessible web service. We can't even generate a top-down web service using the Web
Service wizard itself because the service is inaccessible via the WSDL.
{code}
IWAB0399E Error in generating Java from WSDL: java.io.IOException: Emitter failure.
Invalid endpoint address in port EchoPort in service EchoServiceLocator:
REPLACE_WITH_ACTUAL_URL
java.io.IOException: Emitter failure. Invalid endpoint address in port EchoPort in
service EchoServiceLocator: REPLACE_WITH_ACTUAL_URL
at
org.apache.axis.wsdl.toJava.JavaServiceImplWriter.writeFileBody(JavaServiceImplWriter.java:242)
at org.apache.axis.wsdl.toJava.JavaWriter.generate(JavaWriter.java:127)
at org.apache.axis.wsdl.toJava.JavaServiceWriter.generate(JavaServiceWriter.java:112)
at
org.apache.axis.wsdl.toJava.JavaGeneratorFactory$Writers.generate(JavaGeneratorFactory.java:421)
at org.apache.axis.wsdl.gen.Parser.generate(Parser.java:476)
at org.apache.axis.wsdl.gen.Parser.access$000(Parser.java:45)
at org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:362)
at java.lang.Thread.run(Thread.java:745)
{code}
That said, trying with a Wildfly 8.1.0 server and the included JBossWS CXF 4.2.4.Final
runtime, I am able to see the issue reported. I'll see what I can do to make this
better.
No Error reported when WS Client code generation fails
------------------------------------------------------
Key: JBIDE-13414
URL:
https://issues.jboss.org/browse/JBIDE-13414
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: webservices
Reporter: Mustafa Musaji
Assignee: Brian Fitzpatrick
Labels: jax-ws, web_service_client
Fix For: LATER
Attachments: echoService.wsdl, screenshot-1.png
If you have a WSDL which would normally fail because of JAXB collision. From command line
you would get an error like this:
Failed to invoke WSDLToJava
org.apache.cxf.tools.common.ToolException: Thrown by JAXB:
Thrown by JAXB:
Two declarations cause a collision in the ObjectFactory class.
...
However, in JBDS you don't get any error. It just doesn't create any sources and
there is no indication of what the issue is.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)