[jbosstools-issues] [JBoss JIRA] (JBIDE-13414) No Error reported when WS Client code generation fails

[Brian Fitzpatrick (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-13414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12771205#comment-12771205 ] 

Brian Fitzpatrick commented on JBIDE-13414:
-------------------------------------------

That's interesting. With the most recent code on Kepler, I'm seeing an exception pop up in a dialog: 
{code}
Error: Could not import. (use --verbose to see full traces)	
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0	
	at java.util.ArrayList.RangeCheck(ArrayList.java:547)	
	at java.util.ArrayList.get(ArrayList.java:322)	
	at org.apache.cxf.tools.common.ToolException.printStackTrace(ToolException.java:120)	
	at org.apache.cxf.tools.common.ToolException.printThrowable(ToolException.java:126)	
	at org.apache.cxf.tools.common.ToolException.printStackTrace(ToolException.java:121)	
	at org.apache.cxf.tools.common.ToolException.printStackTrace(ToolException.java:104)	
	at org.jboss.wsf.stack.cxf.tools.CXFConsumerImpl.consume(CXFConsumerImpl.java:291)	
	at org.jboss.ws.tools.cmd.WSConsume.importServices(WSConsume.java:279)	
	at org.jboss.ws.tools.cmd.WSConsume.mainInternal(WSConsume.java:104)	
	at org.jboss.ws.tools.cmd.WSConsume.main(WSConsume.java:92)	
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)	
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)	
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)	
	at java.lang.reflect.Method.invoke(Method.java:597)	
	at org.jboss.modules.Module.run(Module.java:262)	
	at org.jboss.modules.Main.main(Main.java:329)	
{code}
                
> 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: web_service_client
>             Fix For: 4.1.0.Beta1
>
>         Attachments: echoService.wsdl
>
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira