May 2015 - jbosstools-issues - Jboss List Archives

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

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13414?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick updated JBIDE-13414: -------------------------------------- Attachment: new-error.png > 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, new-error.png, 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)

10 years, 11 months

1
0
0 / 0

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

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13414?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-13414: ------------------------------------------- I can add a new error check - it's not ideal, but looks like the attached error dialog. > 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, new-error.png, 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)

10 years, 11 months

1
0
0 / 0

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

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13414?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-13414: ------------------------------------------- Tracing into this I am seeing this show up after running wsconsume... {code} Could not find log4j.xml configuration, logging to console. JBWS024003: Unsupported value '2.0' for target, using default value '2.2' TODO! Cheek SOAP 1.2 extension Loading FrontEnd jaxws ... Loading DataBinding jaxb ... wsdl2java -compile -exsh false -d E:\workspaces\runtime-New_configuration-04-MAY-2015\echo\src -verbose -classdir E:\workspaces\runtime-New_configuration-04-MAY-2015\echo\build\classes -allowElementReferences file:/E:/workspaces/runtime-New_configuration-04-MAY-2015/echo/WebContent/echoService.wsdl wsdl2java - Apache CXF 2.7.11 JBWS024002: Failed to invoke org.apache.cxf.tools.wsdlto.WSDLToJava org.apache.cxf.tools.common.ToolException: file:/E:/workspaces/runtime-New_configuration-04-MAY-2015/echo/WebContent/echoService.wsdl [12,2]: Two declarations cause a collision in the ObjectFactory class. file:/E:/workspaces/runtime-New_configuration-04-MAY-2015/echo/WebContent/echoService.wsdl [13,2]: (Related to above error) This is the other declaration. at org.apache.cxf.tools.common.ToolErrorListener.throwToolException(ToolErrorListener.java:87) at org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:166) at org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:412) at org.apache.cxf.tools.common.toolspec.ToolRunner.runTool(ToolRunner.java:103) at org.apache.cxf.tools.wsdlto.WSDLToJava.run(WSDLToJava.java:113) at org.jboss.wsf.stack.cxf.tools.CXFConsumerImpl.consume(CXFConsumerImpl.java:301) at org.jboss.ws.tools.cmd.WSConsume.importServices(WSConsume.java:289) at org.jboss.ws.tools.cmd.WSConsume.mainInternal(WSConsume.java:106) at org.jboss.ws.tools.cmd.WSConsume.main(WSConsume.java:94) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.jboss.modules.Module.run(Module.java:312) at org.jboss.modules.Main.main(Main.java:460) Suppressed: org.apache.cxf.tools.common.ToolException: file:/E:/workspaces/runtime-New_configuration-04-MAY-2015/echo/WebContent/echoService.wsdl [12,2]: Two declarations cause a collision in the ObjectFactory class. ... 15 more Caused by: com.sun.istack.SAXParseException2publicId: file:/E:/workspaces/runtime-New_configuration-04-MAY-2015/echo/WebContent/echoService.wsdl; systemId: file:/E:/workspaces/runtime-New_configuration-04-MAY-2015/echo/WebContent/echoService.wsdl; lineNumber: 12; columnNumber: 2; Two declarations cause a collision in the ObjectFactory class. at com.sun.tools.xjc.ErrorReceiver.error(ErrorReceiver.java:86) at com.sun.tools.xjc.generator.bean.ObjectFactoryGeneratorImpl.populate(ObjectFactoryGeneratorImpl.java:191) at com.sun.tools.xjc.generator.bean.PublicObjectFactoryGenerator.populate(PublicObjectFactoryGenerator.java:59) at com.sun.tools.xjc.generator.bean.BeanGenerator.<init>(BeanGenerator.java:267) at com.sun.tools.xjc.generator.bean.BeanGenerator.generate(BeanGenerator.java:166) at com.sun.tools.xjc.model.Model.generateCode(Model.java:290) at com.sun.tools.xjc.api.impl.s2j.SchemaCompilerImpl.bind(SchemaCompilerImpl.java:283) at com.sun.tools.xjc.api.impl.s2j.SchemaCompilerImpl.bind(SchemaCompilerImpl.java:94) at org.apache.cxf.tools.wsdlto.databinding.jaxb.JAXBDataBinding.initialize(JAXBDataBinding.java:462) at org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.generateTypes(WSDLToJavaContainer.java:714) at org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.processWsdl(WSDLToJavaContainer.java:270) at org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:164) ... 13 more Suppressed: org.apache.cxf.tools.common.ToolException: file:/E:/workspaces/runtime-New_configuration-04-MAY-2015/echo/WebContent/echoService.wsdl [13,2]: (Related to above error) This is the other declaration. ... 15 more Caused by: com.sun.istack.SAXParseException2publicId: file:/E:/workspaces/runtime-New_configuration-04-MAY-2015/echo/WebContent/echoService.wsdl; systemId: file:/E:/workspaces/runtime-New_configuration-04-MAY-2015/echo/WebContent/echoService.wsdl; lineNumber: 13; columnNumber: 2; (Related to above error) This is the other declaration. at com.sun.tools.xjc.ErrorReceiver.error(ErrorReceiver.java:86) at com.sun.tools.xjc.generator.bean.ObjectFactoryGeneratorImpl.populate(ObjectFactoryGeneratorImpl.java:193) at com.sun.tools.xjc.generator.bean.PublicObjectFactoryGenerator.populate(PublicObjectFactoryGenerator.java:59) at com.sun.tools.xjc.generator.bean.BeanGenerator.<init>(BeanGenerator.java:267) at com.sun.tools.xjc.generator.bean.BeanGenerator.generate(BeanGenerator.java:166) at com.sun.tools.xjc.model.Model.generateCode(Model.java:290) at com.sun.tools.xjc.api.impl.s2j.SchemaCompilerImpl.bind(SchemaCompilerImpl.java:283) at com.sun.tools.xjc.api.impl.s2j.SchemaCompilerImpl.bind(SchemaCompilerImpl.java:94) at org.apache.cxf.tools.wsdlto.databinding.jaxb.JAXBDataBinding.initialize(JAXBDataBinding.java:462) at org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.generateTypes(WSDLToJavaContainer.java:714) at org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.processWsdl(WSDLToJavaContainer.java:270) at org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:164) ... 13 more {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: 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)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19772) Update fails with No repository found containing: osgi.bundle, org.apache.commons.io, 2.4.0

by Martin Schröder (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19772?page=com.atlassian.jira.plugi... ] Martin Schröder commented on JBIDE-19772: ----------------------------------------- Whatever it was, it's solved. I - tried every repository aside from the JBoss's seperately; this gave me updates for egit and subclipse and ... - then I tried only the jboss repos; this updated JBoss - now with all repos (sans the obsolete JBoss) everything is up-to-date Thanks for the help and sorry for the noise > Update fails with No repository found containing: osgi.bundle,org.apache.commons.io,2.4.0 > ----------------------------------------------------------------------------------------- > > Key: JBIDE-19772 > URL: https://issues.jboss.org/browse/JBIDE-19772 > Project: Tools (JBoss Tools) > Issue Type: Bug > Affects Versions: 4.2.3.Final > Reporter: Martin Schröder > Assignee: Denis Golovin > Attachments: .log, bookmarks.xml, jbosstools-diagnostics-20150506142332.zip > > > I'm trying to update my installed plugins in my Eclipse 4.4.2. This wants to update a lot of JBoss Tools components, but ultimately fails with > No repository found containing: osgi.bundle,org.apache.commons.io,2.4.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19776) Create and use Mars M7 target-platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19776?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19776: ------------------------------------ I've regenerated the egit mirror [1] and now the p2diffs include one additional IU / updated IU: [1] http://download.jboss.org/jbosstools/updates/requirements/egit/v4.0.0.201... {code}> org.eclipse.egit.ui.importer [0.0.1.201505070847] {code} > Create and use Mars M7 target-platform > -------------------------------------- > > Key: JBIDE-19776 > URL: https://issues.jboss.org/browse/JBIDE-19776 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: target-platform > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.3.0.Beta1 > > Attachments: jbdevstudio.p2diff.txt, jbosstools.p2diff.txt > > > Mars M7 was released and contains interesting changes. > We need to start using it ASAP to leverage new functionalities and adapt to the most important changes. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19750) Install grinder fails to run on RHEL7: No more handles!

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19750?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19750: ---------------------------------------- I requested installation of Webkit on CI infrastructure: https://engineering.redhat.com/rt/Ticket/Display.html?id=350706 > Install grinder fails to run on RHEL7: No more handles! > ------------------------------------------------------- > > Key: JBIDE-19750 > URL: https://issues.jboss.org/browse/JBIDE-19750 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Mickael Istria > > {code} > 16:48:30 Installing org.eclipse.swtbot.eclipse.test.junit.feature.group 2.2.1.201402241301. > ... > 13:39:08 !MESSAGE Internal browser is not available: No more handles [Browser style SWT.MOZILLA and Java system property org.eclipse.swt.browser.DefaultType=mozilla are not supported with GTK 3 as XULRunner is not ported for GTK 3 yet] > 13:43:18 Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 253.079 sec > 13:43:18 > 13:43:18 Testcase: testInstall took 252.166 sec > {code} - https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > I tried to run using `-Dorg.eclipse.swt.browser.DefaultType=webkit` as a script param for `testInstall.groovy` but it must not have passed through to the eclipse install process, as the above error suggests. > Wondering if ... > a) passing through a different *swt.browser.DefaultType*, &/or > b) using a newer SWTBot (which works with Luna [1] now?) > ... might help. > [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=464619 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

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

by Brian Fitzpatrick (JIRA)

[ 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)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19772) Update fails with No repository found containing: osgi.bundle, org.apache.commons.io, 2.4.0

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19772?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-19772: --------------------------------------- would be also good to have list of features installed or screenshot from Help->About Eclipse [Installation Details]->[Installed Software] . > Update fails with No repository found containing: osgi.bundle,org.apache.commons.io,2.4.0 > ----------------------------------------------------------------------------------------- > > Key: JBIDE-19772 > URL: https://issues.jboss.org/browse/JBIDE-19772 > Project: Tools (JBoss Tools) > Issue Type: Bug > Affects Versions: 4.2.3.Final > Reporter: Martin Schröder > Assignee: Denis Golovin > Attachments: .log, bookmarks.xml, jbosstools-diagnostics-20150506142332.zip > > > I'm trying to update my installed plugins in my Eclipse 4.4.2. This wants to update a lot of JBoss Tools components, but ultimately fails with > No repository found containing: osgi.bundle,org.apache.commons.io,2.4.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19772) Update fails with No repository found containing: osgi.bundle, org.apache.commons.io, 2.4.0

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19772?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-19772: --------------------------------------- JBoss Tools Has no references to commons IO 2.4.0. Lets assume something else drags it in and see if having only JBoss Tools Related update sites and official Luna update site enabled in preference eliminate commons.io 2.4.0 related errors. There should be only 4 update sites enabled: 1. <site url="http://download.eclipse.org/eclipse/updates/4.4" selected="true" name="The Eclipse Project Updates"/> 2. <site url="http://download.eclipse.org/releases/luna" selected="true" name="Luna"/> 3. <site url="http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/luna/" selected="true" name="JBoss Tools Target Platform - Luna"/> 4. <site url="http://download.jboss.org/jbosstools/updates/stable/luna/" selected="true" name="JBoss Tools 4.2 - Core - Stable Release Update Site"/> > Update fails with No repository found containing: osgi.bundle,org.apache.commons.io,2.4.0 > ----------------------------------------------------------------------------------------- > > Key: JBIDE-19772 > URL: https://issues.jboss.org/browse/JBIDE-19772 > Project: Tools (JBoss Tools) > Issue Type: Bug > Affects Versions: 4.2.3.Final > Reporter: Martin Schröder > Assignee: Denis Golovin > Attachments: .log, bookmarks.xml, jbosstools-diagnostics-20150506142332.zip > > > I'm trying to update my installed plugins in my Eclipse 4.4.2. This wants to update a lot of JBoss Tools components, but ultimately fails with > No repository found containing: osgi.bundle,org.apache.commons.io,2.4.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

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

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13414?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick updated JBIDE-13414: -------------------------------------- Attachment: screenshot-1.png > 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)

10 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues May 2015