November 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-15772) Remove referenced juno sites in integration-tests site pom

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15772?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-15772: --------------------------------------- Removed features/: https://github.com/jbosstools/jbosstools-integration-tests/pull/433 > Remove referenced juno sites in integration-tests site pom > ---------------------------------------------------------- > > Key: JBIDE-15772 > URL: https://issues.jboss.org/browse/JBIDE-15772 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: qa > Affects Versions: 4.1.1.Beta1 > Reporter: Martin Malina > Assignee: Martin Malina > Fix For: 4.1.1.CR1 > > > https://github.com/jbosstools/jbosstools-integration-tests/blob/master/si... > {code} > <associateSite>http://download.jboss.org/jbosstools/updates/juno/soa-tooling/</associateSite> > <associateSite>http://download.jboss.org/jbosstools/updates/juno/</associateSite> > <associateSite>http://download.jboss.org/jbosstools/updates/stable/juno/</associateSite> > <associateSite>http://download.jboss.org/jbosstools/updates/development/juno/soa-tooling/</associateSite> > {code} > These are added when you add the integration-tests update site to Eclipse to resolve dependencies. > We most probably don't need them. Or if we do, we should update to kepler links. -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15908) Problem decorator is not removed after error was fixed

by Radoslav Rábara (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15908?page=com.atlassian.jira.plugi... ] Radoslav Rábara closed JBIDE-15908. ----------------------------------- Verified in JBDS 7.1.0 CR1-v20131116-1929-B543 > Problem decorator is not removed after error was fixed > ------------------------------------------------------- > > Key: JBIDE-15908 > URL: https://issues.jboss.org/browse/JBIDE-15908 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.1.1.Beta1 > Reporter: Xavier Coulon > Assignee: Max Rydahl Andersen > Fix For: 4.1.1.CR1 > > > Create a JAX-RS validation error such as > {code} > @GET > @Path("/{id}") > public AttendeeRepresentation getAttendee(@PathParam("ide") final int id) { > ... > } > {code} > ASSERT: an error decorator appears on the JAX-RS Endpoint in the project explorer. > Fix the problem (change "ide" -> "id") > ASSERT: the error decorator should disappear > FAIL the error decorator remains visible. -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15772) Remove referenced juno sites in integration-tests site pom

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15772?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-15772: --------------------------------------- [~nickboldt] yeah, you're right, I will remove that. > Remove referenced juno sites in integration-tests site pom > ---------------------------------------------------------- > > Key: JBIDE-15772 > URL: https://issues.jboss.org/browse/JBIDE-15772 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: qa > Affects Versions: 4.1.1.Beta1 > Reporter: Martin Malina > Assignee: Martin Malina > Fix For: 4.1.1.CR1 > > > https://github.com/jbosstools/jbosstools-integration-tests/blob/master/si... > {code} > <associateSite>http://download.jboss.org/jbosstools/updates/juno/soa-tooling/</associateSite> > <associateSite>http://download.jboss.org/jbosstools/updates/juno/</associateSite> > <associateSite>http://download.jboss.org/jbosstools/updates/stable/juno/</associateSite> > <associateSite>http://download.jboss.org/jbosstools/updates/development/juno/soa-tooling/</associateSite> > {code} > These are added when you add the integration-tests update site to Eclipse to resolve dependencies. > We most probably don't need them. Or if we do, we should update to kepler links. -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15600) MatrixParam and QueryParam field names are used instead of the annotation values

by Radoslav Rábara (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15600?page=com.atlassian.jira.plugi... ] Radoslav Rábara closed JBIDE-15600. ----------------------------------- Resolution: Duplicate Issue > MatrixParam and QueryParam field names are used instead of the annotation values > -------------------------------------------------------------------------------- > > Key: JBIDE-15600 > URL: https://issues.jboss.org/browse/JBIDE-15600 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.1.0.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.1.1.Beta1 > > Attachments: urlTemplateWithoutQueryParam.jpg > > > Take the following classes: > {code} > @Path("/products") > public class ProductResourceLocator { > @QueryParam("foo1") > private String foo2; > @Path("/{productType}") > public Object getProductResourceLocator() { > return new BookResource(); > } > } > {code} > and > {code} > @Produces({ MediaType.APPLICATION_XML, "application/json" }) > public class BookResource { > @GET > @Path("/{id}") > @Produces({ "application/xml", "application/json" }) > public Book getProduct(@PathParam("id") Integer id) { > return null; > } > } > {code} > ASSERT: the URL Template for the Endpoint should be something like > {code} > /products/{productType}/{id}?foo1={String} > {code} > FAIL: the URL Template for the Endpoint should be something like > {code} > /products/{productType}/{id}?foo2={String} > {code} -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13405) Deploying a RAR with JAR inside fails using remote systems via SSH

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13405?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-13405. --------------------------------- Reproduced the issue in JBDS 7.1.0.Beta1, verified the fix in JBDS 7.1.0.CR1 B543. > Deploying a RAR with JAR inside fails using remote systems via SSH > ------------------------------------------------------------------ > > Key: JBIDE-13405 > URL: https://issues.jboss.org/browse/JBIDE-13405 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.0.0.Final > Environment: JBoss AS 7.1.1 Final, Eclipse Juno SR1, JBoss Tools 4.0.0 Final > Reporter: Chris Roberts > Assignee: Rob Stryker > Fix For: 4.1.1.CR1 > > Attachments: maven-broken.tar.gz > > > Exploding dependant jars seems to have issues for rars. I didn't work out if this is a problem in JBoss Tools or RSE. I suspect a little of both. It seems looking at the source that only the 'Local' RSE adapter correctly explodes deployments? > 1) Create a maven project, set the packaging to rar > 2) Create a second maven project, set the packaging to jar > 3) Include the jar as a maven compile dependency of the rar > 4) Import both into eclipse > 5) Deploy to a remote (JBoss AS) server via RSE SSH/dstore/FTP fails > It seems the JBoss Server Adapter (I think) creates the directory: > xxxxx-1.0.rar/xxxxx-1.0.jar/ > on deployment. It then requests upload for the jar over the top of the directory which fails. With FTP this looks like: > CD xxxxx-1.0.rar/ > MKD xxxxx-1.0.jar > STOR xxxxx-1.0.jar <fails because directory exists> > This is my first bug opened on JBoss/eclipse, so please point me on if you think this should be opened on RSE, but I think looking at the source it belongs here. -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15599) Changes on a subresource locator fields are not propagated to the JAX-RS Explorer

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15599?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-15599: ---------------------------------- Fix Version/s: 4.2.0.Alpha1 (was: 4.1.1.Beta1) > Changes on a subresource locator fields are not propagated to the JAX-RS Explorer > --------------------------------------------------------------------------------- > > Key: JBIDE-15599 > URL: https://issues.jboss.org/browse/JBIDE-15599 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.1.0.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.2.0.Alpha1 > > > Take the following classes: > {code} > @Path("/products") > public class ProductResourceLocator { > @QueryParam("foo") > private String foo; > @Path("/{productType}") > public Object getProductResourceLocator() { > return new BookResource(); > } > } > {code} > and > {code} > @Produces({ MediaType.APPLICATION_XML, "application/json" }) > public class BookResource { > @GET > @Path("/{id}") > @Produces({ "application/xml", "application/json" }) > public Book getProduct(@PathParam("id") Integer id) { > return null; > } > } > {code} > and modify the @QueryParam value of the "foo" field. > ASSERT: the changes appear in the Project Explorer > FAIL: the old @QueryParam annotation value is still used > WORKAROUND: Refresh the JAX-RS Web Services node. -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15304) NullPointerExceptions in JAX-RS doesn't report what project is affected

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15304?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-15304: --------------------------------------- [~dgolovin], can you verify if the problem appears again and if so, if you have more information on where it came from ? thanks. > NullPointerExceptions in JAX-RS doesn't report what project is affected > ----------------------------------------------------------------------- > > Key: JBIDE-15304 > URL: https://issues.jboss.org/browse/JBIDE-15304 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.1.0.Final > Reporter: Denis Golovin > Assignee: Max Rydahl Andersen > Fix For: 4.1.1.Alpha2, 4.2.0.Alpha1 > > > I've seen this exception happens many times when I have several projects imported out of JBoss Central: > {code}java.lang.NullPointerException > at org.jboss.tools.ws.jaxrs.core.jdt.JavaMethodSignaturesVisitor.visit(JavaMethodSignaturesVisitor.java:105) > at org.eclipse.jdt.core.dom.MethodDeclaration.accept0(MethodDeclaration.java:489) > at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2514) > at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2585) > at org.eclipse.jdt.core.dom.TypeDeclaration.accept0(TypeDeclaration.java:484) > at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2514) > at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2585) > at org.eclipse.jdt.core.dom.CompilationUnit.accept0(CompilationUnit.java:220) > at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2514) > at org.jboss.tools.ws.jaxrs.core.jdt.JdtUtils.resolveMethodSignatures(JdtUtils.java:674) > at org.jboss.tools.ws.jaxrs.core.jdt.CompilationUnitsRepository.mergeAST(CompilationUnitsRepository.java:113) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementDeltaScanner.scanDelta(JavaElementDeltaScanner.java:119) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementDeltaScanner.scanAndFilterEvent(JavaElementDeltaScanner.java:71) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedBuildJob.run(JavaElementChangedBuildJob.java:54) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedBuildJob.execute(JavaElementChangedBuildJob.java:41) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedListener.elementChanged(JavaElementChangedListener.java:69) > at org.eclipse.jdt.internal.core.DeltaProcessor$4.run(DeltaProcessor.java:1682) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.jdt.internal.core.DeltaProcessor.notifyListeners(DeltaProcessor.java:1672) > at org.eclipse.jdt.internal.core.DeltaProcessor.fireReconcileDelta(DeltaProcessor.java:1524) > at org.eclipse.jdt.internal.core.DeltaProcessor.fire(DeltaProcessor.java:1483) > at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:769) > at org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:788) > at org.eclipse.jdt.internal.core.CompilationUnit.reconcile(CompilationUnit.java:1247) > at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.reconcile(JavaReconcilingStrategy.java:126) > at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.access$0(JavaReconcilingStrategy.java:108) > at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy$1.run(JavaReconcilingStrategy.java:89) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.reconcile(JavaReconcilingStrategy.java:87) > at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.initialReconcile(JavaReconcilingStrategy.java:178) > at org.eclipse.jdt.internal.ui.text.CompositeReconcilingStrategy.initialReconcile(CompositeReconcilingStrategy.java:114) > at org.eclipse.jdt.internal.ui.text.JavaCompositeReconcilingStrategy.initialReconcile(JavaCompositeReconcilingStrategy.java:136) > at org.eclipse.jface.text.reconciler.MonoReconciler.initialProcess(MonoReconciler.java:105) > at org.eclipse.jdt.internal.ui.text.JavaReconciler.initialProcess(JavaReconciler.java:406) > at org.eclipse.jface.text.reconciler.AbstractReconciler$BackgroundThread.run(AbstractReconciler.java:173) > {code} > couldn't catch exact steps to replicate, because I have many projects in workspace and log entry doesn't provide additional info about project. -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15808) openshift-java-client: "Tail files" cannot not load application gear list for recently created scaling apps

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15808?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-15808: ---------------------------------- Summary: openshift-java-client: "Tail files" cannot not load application gear list for recently created scaling apps (was: "Tail files" cannot not load application gear list for recently created scaling apps) > openshift-java-client: "Tail files" cannot not load application gear list for recently created scaling apps > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15808 > URL: https://issues.jboss.org/browse/JBIDE-15808 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: respin-b > Fix For: 4.1.1.Beta1 > > Attachments: could-not-load-application-gears.png > > -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15808) openshift-java-client: "Tail files" cannot not load application gear list for recently created scaling apps

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15808?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-15808: ---------------------------------- Labels: openshift-java-client respin-b (was: respin-b) > openshift-java-client: "Tail files" cannot not load application gear list for recently created scaling apps > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15808 > URL: https://issues.jboss.org/browse/JBIDE-15808 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift-java-client, respin-b > Fix For: 4.1.1.Beta1 > > Attachments: could-not-load-application-gears.png > > -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15930) Misleading shell title for Environment Variables

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15930?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-15930. --------------------------------- Was same problem as in JBIDE-15899 thus was rejected as "duplicate". JBIDE-15899 already fix and verified in JBDS 7.1.0.CR1 Build id: CR1-v20131116-1929-B543 > Misleading shell title for Environment Variables > ------------------------------------------------ > > Key: JBIDE-15930 > URL: https://issues.jboss.org/browse/JBIDE-15930 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.Beta1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.1.1.CR1, 4.2.0.Alpha1 > > Attachments: env_vars.png > > > Edit environment variables shell has missleading shell title - "Select Domain". See attached image. There should be something like "Manage environment variables" or "Edit environment variables". -- 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

12 years, 5 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 November 2013