July 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19988) Run Docker image wizard does not recognize image that it pulled

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19988?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-19988: ---------------------------------- Fix Version/s: 4.3.0.CR1 (was: 4.3.0.Beta2) > Run Docker image wizard does not recognize image that it pulled > --------------------------------------------------------------- > > Key: JBIDE-19988 > URL: https://issues.jboss.org/browse/JBIDE-19988 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker, upstream > Affects Versions: 4.3.0.Beta1 > Reporter: Martin Malina > Assignee: Xavier Coulon > Fix For: 4.3.0.CR1 > > > When you're in the Run a Docker Image and search for an image that you don't have (e.g. fedora:latest) and then pull it, using the link below the Image field, after the image is pulled, the wizard still says it's not available locally. > Upstream BZ: https://bugs.eclipse.org/bugs/show_bug.cgi?id=469709 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19904) Browse button are stubs in Docker Tooling

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19904?page=com.atlassian.jira.plugi... ] Xavier Coulon resolved JBIDE-19904. ----------------------------------- Resolution: Done Fixed upstream > Browse button are stubs in Docker Tooling > ----------------------------------------- > > Key: JBIDE-19904 > URL: https://issues.jboss.org/browse/JBIDE-19904 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker, upstream > Affects Versions: 4.3.0.Beta1 > Reporter: Arun Gupta > Assignee: Xavier Coulon > Fix For: 4.3.0.Beta2 > > > Latest JBoss Developer Studio nightly with Docker Tooling installed from http://download.eclipse.org/linuxtools/updates-docker-nightly/. > In Docker Explorer, creating a new connection, using custom settings. Clicking on the Browse button for "Unix socket" or "TCP Connection" does nothing. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (LOCUS-44) locus/site/pom.xml first lane is blank

by Denis Golovin (JIRA)

Denis Golovin created LOCUS-44: ---------------------------------- Summary: locus/site/pom.xml first lane is blank Key: LOCUS-44 URL: https://issues.jboss.org/browse/LOCUS-44 Project: JBoss Tools Locus Issue Type: Bug Affects Versions: 1.1.0 Reporter: Denis Golovin This blank lane the reason for exception below: java.lang.Exception: Problem parsing archive:file:/!/home/eskimo/Projects/jbosstools-master3/git/jbosstools-locus/site/pom.xml at org.eclipse.oomph.resources.impl.XMLProjectFactoryImpl.doCreateProject(XMLProjectFactoryImpl.java:101) at org.eclipse.oomph.resources.impl.ProjectFactoryImpl.createProject(ProjectFactoryImpl.java:117) at org.eclipse.oomph.resources.impl.SourceLocatorImpl.loadProject(SourceLocatorImpl.java:492) at org.eclipse.oomph.resources.impl.SourceLocatorImpl.loadProject(SourceLocatorImpl.java:268) at org.eclipse.oomph.setup.maven.impl.MavenImportTaskImpl.processMavenProject(MavenImportTaskImpl.java:398) at org.eclipse.oomph.setup.maven.impl.MavenImportTaskImpl.processMavenProject(MavenImportTaskImpl.java:429) at org.eclipse.oomph.setup.maven.impl.MavenImportTaskImpl.processMavenProject(MavenImportTaskImpl.java:412) at org.eclipse.oomph.setup.maven.impl.MavenImportTaskImpl.processMavenProject(MavenImportTaskImpl.java:379) at org.eclipse.oomph.setup.maven.impl.MavenImportTaskImpl.processMavenProject(MavenImportTaskImpl.java:363) at org.eclipse.oomph.setup.maven.impl.MavenImportTaskImpl.perform(MavenImportTaskImpl.java:326) at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.doPerformNeededSetupTasks(SetupTaskPerformer.java:2906) at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.access$1(SetupTaskPerformer.java:2865) at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer$WorkspaceUtil$1.run(SetupTaskPerformer.java:3950) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2241) at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer$WorkspaceUtil.performNeededSetupTasks(SetupTaskPerformer.java:3944) at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer$WorkspaceUtil.access$0(SetupTaskPerformer.java:3942) at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.performNeededSetupTasks(SetupTaskPerformer.java:2856) at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.performTriggeredSetupTasks(SetupTaskPerformer.java:2831) at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.perform(SetupTaskPerformer.java:2762) at org.eclipse.oomph.setup.ui.wizards.ProgressPage$9.run(ProgressPage.java:542) at org.eclipse.oomph.setup.ui.wizards.ProgressPage$11$1.run(ProgressPage.java:627) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) Caused by: org.xml.sax.SAXParseException; lineNumber: 2; columnNumber: 6; The processing instruction target matching "[xX][mM][lL]" is not allowed. at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:257) at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:348) at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:121) at org.eclipse.oomph.util.XMLUtil.loadDocument(XMLUtil.java:50) at org.eclipse.oomph.util.XMLUtil.loadRootElement(XMLUtil.java:65) at org.eclipse.oomph.resources.impl.XMLProjectFactoryImpl.doCreateProject(XMLProjectFactoryImpl.java:86) ... 21 more -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3461) Creating bottom-up web service with a client result in error

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBDS-3461?page=com.atlassian.jira.plugin.... ] Brian Fitzpatrick commented on JBDS-3461: ----------------------------------------- It appears that the WSDL has to be created before the Client can be generated. 1. Create a dynamic web project, add to an EAR, generate web.xml 2. Create a sample web service using the sample web service wizard 3. Fire up the Web Service wizard, select bottom-up service with the sample service from previous step as implementation 4. Select JBossWS web service runtime, eg. Wildfly as server. 5. Click Next. Check "Generate WSDL file" 6. Click Finish. Let it do its thing. 7. The generated "SayHelloResponse" for me was invalid. I had to change it to make it ok. 8. Re-run the WS wizard and generate the WSDL again. It gets created this time. 9. Fire up the Web Service Client wizard, select WSDL we created in previous step. 10. Select JBossWS web service runtime, eg. Wildfly as server. 11. Click Finish. No error. So there's a workaround. I'm not sure why the response class is being generated with an error, but suspect that's what's holding up the WSDL creation and not allowing us to do this all in one go. But at least there's a workaround. > Creating bottom-up web service with a client result in error > ------------------------------------------------------------ > > Key: JBDS-3461 > URL: https://issues.jboss.org/browse/JBDS-3461 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: webservices > Affects Versions: 9.0.0.Beta1 > Reporter: Jan Richter > Assignee: Brian Fitzpatrick > > When creating a bottom-up web service along with a client using the web service wizard, it will create the service, but on the next step it throws an error saying: 'Selection must be WSDL.' > Note, this does not happen in Eclipse with JBT 4.3.0.Beta1. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18516) JAX-RS Validator should report problem when @DefaultValue is used alone

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18516?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-18516: ---------------------------------- Fix Version/s: 4.3.0.CR1 (was: 4.3.0.Beta2) > JAX-RS Validator should report problem when @DefaultValue is used alone > ----------------------------------------------------------------------- > > Key: JBIDE-18516 > URL: https://issues.jboss.org/browse/JBIDE-18516 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: webservices > Affects Versions: 4.2.0.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Labels: jax-rs > Fix For: 4.3.0.CR1 > > > If a method parameter is annotated with {{@DefaultValue}} but has _no_ {{@QueryParam}} (or similar) annotation, then the application will most certainly fail with an error message such as: > {code} > failed to execute: javax.ws.rs.NotSupportedException: Could not find message body reader for type: int of content type: */* > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18143) Fixing sonar issues in RS (not WS) code

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18143?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-18143: ---------------------------------- Fix Version/s: 4.3.0.CR1 (was: 4.3.0.Beta2) > Fixing sonar issues in RS (not WS) code > --------------------------------------- > > Key: JBIDE-18143 > URL: https://issues.jboss.org/browse/JBIDE-18143 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: webservices > Affects Versions: 4.1.1.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Labels: jax-rs > Fix For: 4.3.0.CR1 > > > Fixing issues found by the sonar pass in the JAX-RS tooling -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18101) API updates

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18101?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-18101: ---------------------------------- Fix Version/s: 4.3.0.CR1 (was: 4.3.0.Beta2) > API updates > ----------- > > Key: JBIDE-18101 > URL: https://issues.jboss.org/browse/JBIDE-18101 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: webservices > Affects Versions: 4.2.0.Beta3 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Labels: jax-rs > Fix For: 4.3.0.CR1 > > > Unify the JaxrsElement builders to provide the same methods: > - buildTransient() > - buildInMetamodel(JaxrsMetamodel) > Also, simplify the JaxrsElement#update() method (code could be simpler, with less if/else blocks) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20124) NPE when removing a returned class in JAX-RS resource method does not exist

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20124?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-20124: ---------------------------------- Fix Version/s: 4.3.0.CR1 (was: 4.3.0.Beta2) > NPE when removing a returned class in JAX-RS resource method does not exist > --------------------------------------------------------------------------- > > Key: JBIDE-20124 > URL: https://issues.jboss.org/browse/JBIDE-20124 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.3.0.Alpha2 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.3.0.CR1 > > > If a project contains a method such as > {code} > @Path("/{id}/comments") > public Foo addComments() { > return null; > } > {code} > while {{Foo}} does not exist, the JAX-RS Metamodel builder will fail with the following exception: > {code} > java.lang.NullPointerException > at org.jboss.tools.ws.jaxrs.core.jdt.JdtUtils.findSubtypes(JdtUtils.java:905) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsEndpointFactory.createEndpointsFromSubresourceLocator(JaxrsEndpointFactory.java:145) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsElementChangedProcessorDelegate.processSubresourceLocatorAddition(JaxrsElementChangedProcessorDelegate.java:285) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsElementChangedProcessorDelegate.processAddition(JaxrsElementChangedProcessorDelegate.java:191) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsElementChangedProcessorDelegate.processEvent(JaxrsElementChangedProcessorDelegate.java:70) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.processElementChange(JaxrsMetamodel.java:751) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.add(JaxrsMetamodel.java:720) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsBaseElement.joinMetamodel(JaxrsBaseElement.java:127) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsResourceMethod$Builder.buildInResource(JaxrsResourceMethod.java:181) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsElementFactory.createElements(JaxrsElementFactory.java:211) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsElementFactory.createElements(JaxrsElementFactory.java:65) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.processJavaElementChange(JaxrsMetamodel.java:420) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.processJavaElementChange(JaxrsMetamodel.java:392) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedBuildJob.run(JavaElementChangedBuildJob.java:73) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20132) Unable to launch Web Service tester from selected JAX-RS endpoint

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20132?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-20132: ---------------------------------- Fix Version/s: 4.3.0.CR1 (was: 4.3.0.Beta2) > Unable to launch Web Service tester from selected JAX-RS endpoint > ----------------------------------------------------------------- > > Key: JBIDE-20132 > URL: https://issues.jboss.org/browse/JBIDE-20132 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.3.0.Beta1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.3.0.CR1 > > > Progress monitor seems blocked at "Launching client" after the selection of the server to deploy/test the webapp was completed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18142) Fixing sonar issues in RS (not WS) code

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18142?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-18142: ---------------------------------- Fix Version/s: 4.3.0.CR1 (was: 4.3.0.Beta2) > Fixing sonar issues in RS (not WS) code > --------------------------------------- > > Key: JBIDE-18142 > URL: https://issues.jboss.org/browse/JBIDE-18142 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: webservices > Affects Versions: 4.1.1.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Labels: jax-rs > Fix For: 4.3.0.CR1 > > > Fixing issues found by the sonar pass in the JAX-RS tooling -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 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 July 2015