July 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19734) JAX-RS Validator NPEs with wildcard type arguments

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19734?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-19734: ---------------------------------- Affects Version/s: 4.2.0.Final > JAX-RS Validator NPEs with wildcard type arguments > -------------------------------------------------- > > Key: JBIDE-19734 > URL: https://issues.jboss.org/browse/JBIDE-19734 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.2.0.Final > Environment: Eclipse Mars, JDK 1.7 32-bit > Reporter: Kory Markevich > Assignee: Xavier Coulon > Fix For: 4.3.0.Beta2 > > > JBoss JAX-RS Tools feature version: 1.8.0.Beta1-v20150417-0152-B698 > The JAX-RS validator throws an NPE when using generic types with wildcards. Specifically, the call to typeArgumentBinding.getJavaElement() in SourceType.from(VariableDeclaration) can return null, which the SourceType constructor then tries to use, resulting in the following stack trace. Depending on the code, the validator could trigger this exception as frequently as every pause in typing, resulting in a modal error box popping up constantly. The sample code provided only triggers it on save though. > java.lang.NullPointerException > at org.jboss.tools.ws.jaxrs.core.jdt.SourceType.<init>(SourceType.java:157) > at org.jboss.tools.ws.jaxrs.core.jdt.SourceType.from(SourceType.java:49) > at org.jboss.tools.ws.jaxrs.core.jdt.JdtUtils.resolveMethodSignature(JdtUtils.java:1109) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsResource$Builder.build(JaxrsResource.java:169) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsResource.update(JaxrsResource.java:273) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.processJavaElement(JaxrsMetamodel.java:647) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.processResourceChange(JaxrsMetamodel.java:608) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.processAffectedResources(JaxrsMetamodel.java:574) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.ResourceChangedBuildJob.run(ResourceChangedBuildJob.java:77) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20226) jst/jsf New and Noteworthy for 4.3.0.Beta2

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20226?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-20226: -------------------------------------- Assignee: Victor Rubezhny (was: Alexey Kazakov) Assigning to [~vrubezhny] (cc: [~dgolovin]) to mention upgrading Tern.java/AngularJS Eclipse to the final 0.10 release when it's done. And maybe some important upstream updates in JSDT (if any). We don't have any N&N for beta2 besides that. > jst/jsf New and Noteworthy for 4.3.0.Beta2 > ------------------------------------------ > > Key: JBIDE-20226 > URL: https://issues.jboss.org/browse/JBIDE-20226 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: jsf, jsp/jsf/xml/html source editing > Reporter: Max Rydahl Andersen > Assignee: Victor Rubezhny > Priority: Critical > Fix For: 4.3.0.Beta2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If jst/jsf is not listed here check if there are issues that should be added and add them. > Document the ones relevant for jst/jsf by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19817) Application wizard: v3 application wizard needs to be able to react to changing connections

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19817?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-19817. -------------------------------------- Resolution: Duplicate Issue > Application wizard: v3 application wizard needs to be able to react to changing connections > ------------------------------------------------------------------------------------------- > > Key: JBIDE-19817 > URL: https://issues.jboss.org/browse/JBIDE-19817 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Blocker > Labels: openshift_v3 > Fix For: 4.3.0.Beta2 > > > The current application wizard for OpenShift v3 takes a project in the constructor. It was designed to be launched from the explorer where a v3 connection/project is selected before the wizard is launched. The wizard is not able to react to changing connections. In order for the wizard to be able to get launched from File->New->OpenShift we need the wizard to be able to react to chaning connections. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19817) Application wizard: v3 application wizard needs to be able to react to changing connections

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19817?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-19817. ------------------------------------ > Application wizard: v3 application wizard needs to be able to react to changing connections > ------------------------------------------------------------------------------------------- > > Key: JBIDE-19817 > URL: https://issues.jboss.org/browse/JBIDE-19817 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Blocker > Labels: openshift_v3 > Fix For: 4.3.0.Beta2 > > > The current application wizard for OpenShift v3 takes a project in the constructor. It was designed to be launched from the explorer where a v3 connection/project is selected before the wizard is launched. The wizard is not able to react to changing connections. In order for the wizard to be able to get launched from File->New->OpenShift we need the wizard to be able to react to chaning connections. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20252) refactor setAnnoation to setAnnotation

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20252?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-20252: ------------------------------------------ merged and pushed to upstream/master (and deployed updated client lib) > refactor setAnnoation to setAnnotation > -------------------------------------- > > Key: JBIDE-20252 > URL: https://issues.jboss.org/browse/JBIDE-20252 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Nick Boldt > Assignee: Jeff Cantrill > Fix For: 4.3.0.Beta2 > > > I think you want "setAnnotation" here: > https://github.com/jbosstools/jbosstools-openshift/blob/master/plugins/or... > Please verify all references to this method name are also refactored so no API is broken. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20252) refactor setAnnoation to setAnnotation

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20252?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-20252. ------------------------------------ > refactor setAnnoation to setAnnotation > -------------------------------------- > > Key: JBIDE-20252 > URL: https://issues.jboss.org/browse/JBIDE-20252 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Nick Boldt > Assignee: Jeff Cantrill > Fix For: 4.3.0.Beta2 > > > I think you want "setAnnotation" here: > https://github.com/jbosstools/jbosstools-openshift/blob/master/plugins/or... > Please verify all references to this method name are also refactored so no API is broken. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20085) JEE natures are not listed properly

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20085?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-20085: ----------------------------------- Fix Version/s: 4.3.0.Beta2 > JEE natures are not listed properly > ----------------------------------- > > Key: JBIDE-20085 > URL: https://issues.jboss.org/browse/JBIDE-20085 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport > Affects Versions: 4.3.0.Beta1 > Reporter: Lucia Jelinkova > Fix For: 4.3.0.Beta2 > > Attachments: natures.png, report-dialog.png > > > I tried to import projects from https://github.com/jboss-developer/jboss-sandbox-quickstarts.git > Even though they are JEE examples the only nature listed in the report was Maven nature. After import there are also JEE natures set correctly. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20100) how to make users aware of fuse and other tooling only being available from earlyaccess?

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20100?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-20100: ----------------------------------- Fix Version/s: 4.3.0.CR1 > how to make users aware of fuse and other tooling only being available from earlyaccess? > ----------------------------------------------------------------------------------------- > > Key: JBIDE-20100 > URL: https://issues.jboss.org/browse/JBIDE-20100 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Fix For: 4.3.0.CR1 > > > [~jtyrrell] find it confusing when he cannot see Fuse and other earlyaccess features immediately on the install page. > Some comments: > "I install JBDS 8.1 and click on the JBoss Integration and SOA Development, but where is the Fuse tooling in that list." > "<without earlyaccess> why doesn’t my screen shot tell me to use an older version of JBDS or something." > Suggestion: > "when I picked the Integration Stack a greyed out Fuse IDE thingy in the list of choices, and something like (Select early Access) to enable this feature." > I'm fine exploring options to show early access features more prominently but would prefer we would not need to treat Fuse "special" so maybe we should have a "Early Access" section at the bottom instead of filtered in between everything else ? > and for any connectors that has additional/different features just add a "Extra features available in Early access " comment ? > But what to do when Fuse or others dont even have an earlyaccess out yet ? (like is currently the state for devstudio 9) > [~crobson], [~aileenc] and [~lhein] got any suggestions ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20189) Connection does not properly handle Forbidden exceptions

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20189?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20189: ------------------------------------- Fix Version/s: 4.3.0.Beta2 > Connection does not properly handle Forbidden exceptions > -------------------------------------------------------- > > Key: JBIDE-20189 > URL: https://issues.jboss.org/browse/JBIDE-20189 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Priority: Critical > Fix For: 4.3.0.Beta2 > > Attachments: Notice to user.png > > > While working on JBIDE-20016, trying to create a resource (e.g. project) for which the user does not have those perms, the user is presented with a message they need to get a token instead of advising them they are not allowed to perform such an action. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19850) As a user I want to easily set up port forwarding for my application

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19850?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19850: ------------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-openshift/pull/678 > As a user I want to easily set up port forwarding for my application > -------------------------------------------------------------------- > > Key: JBIDE-19850 > URL: https://issues.jboss.org/browse/JBIDE-19850 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Jeff Cantrill > Priority: Blocker > Labels: openshift_v3, port_forwarding_wizard > Fix For: 4.3.0.Beta2 > > Attachments: hello_world_template.json > > > As a user I want to be able to easily set up port forwarding to my application > Test by: > # Start OpenShift > # Create app from attached template > # Right Click on "Hello-world Pod" > Forward Ports > # Check find open ports > # Start Port forwarding > # In a terminal "curl localhost:<assigned local port>" > # Expect "Hello OpenShift" -- 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