[JBoss JIRA] (JBIDE-19734) JAX-RS Validator NPEs with wildcard type arguments
by Kory Markevich (JIRA)
Kory Markevich created JBIDE-19734:
--------------------------------------
Summary: 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
Environment: Eclipse Mars, JDK 1.7 32-bit
Reporter: Kory Markevich
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)
11 years, 1 month
[JBoss JIRA] (JBIDE-19645) Remove seam 3 features from JBDS, JBT default install; add new connector to Central
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19645?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen resolved JBIDE-19645.
-----------------------------------------
Resolution: Won't Fix
After discussion with [~akazakov] we've come to the conclusion the overhead and packaging of seam3 CDI extensions are minimal thus deciding to keep them in.
We will open a separate Jira for seeing if there are reasons to support the deltaspike alternatives for these features.
> Remove seam 3 features from JBDS, JBT default install; add new connector to Central
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-19645
> URL: https://issues.jboss.org/browse/JBIDE-19645
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi-extensions, central, updatesite
> Affects Versions: 4.3.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Fix For: 4.3.0.Beta1
>
> Attachments: jbds8alpha2-features-cdi-seam.png, jbds8alpha2-plugins-cdi.png, jbds8alpha2-plugins-seam.png, jbt43alpha2-features-cdi.png, jbt43alpha2-features-seam.png, jbt43alpha2-plugins-cdi.png, jbt43alpha2-plugins-seam-3-and-seam3.png, validation.png
>
>
> Burr has requested we also remove Seam 3. So I've assumed we'll do it the same way we did for Seam 2:
> * remove from CoreTools categories on update sites
> * remove from JBDS core.feature
> * create new connectors in JBT and JBDS Central
> [~burrsutter] [~maxandersen] please confirm this is the path you want taken for all the renaming features with "seam" in their name.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 1 month
[JBoss JIRA] (JBIDE-19645) Remove seam 3 features from JBDS, JBT default install; add new connector to Central
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19645?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-19645:
----------------------------------------
Sprint: Sprint #2 April 2015
> Remove seam 3 features from JBDS, JBT default install; add new connector to Central
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-19645
> URL: https://issues.jboss.org/browse/JBIDE-19645
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi-extensions, central, updatesite
> Affects Versions: 4.3.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Fix For: 4.3.0.Beta1
>
> Attachments: jbds8alpha2-features-cdi-seam.png, jbds8alpha2-plugins-cdi.png, jbds8alpha2-plugins-seam.png, jbt43alpha2-features-cdi.png, jbt43alpha2-features-seam.png, jbt43alpha2-plugins-cdi.png, jbt43alpha2-plugins-seam-3-and-seam3.png, validation.png
>
>
> Burr has requested we also remove Seam 3. So I've assumed we'll do it the same way we did for Seam 2:
> * remove from CoreTools categories on update sites
> * remove from JBDS core.feature
> * create new connectors in JBT and JBDS Central
> [~burrsutter] [~maxandersen] please confirm this is the path you want taken for all the renaming features with "seam" in their name.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 1 month
[JBoss JIRA] (JBIDE-17103) No warning/error is shown when detected runtime fails to be added
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17103?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-17103:
--------------------------------
Attachment: JBIDE-17103.png
Screenshot of how the error appears.
To verify this screenshot exists:
1) Go to JBoss Runtime Detection page
2) Add a path pointing to a WF installation
3) Wait for dialog indicating 1 new runtime found
4) Delete the entire folder from your HD
5) Press "OK" in the "searching for runtimes..." page
6) See error dialog appear.
> No warning/error is shown when detected runtime fails to be added
> -----------------------------------------------------------------
>
> Key: JBIDE-17103
> URL: https://issues.jboss.org/browse/JBIDE-17103
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.0.Beta1
>
> Attachments: JBIDE-17103.png
>
>
> When there is a new version of a runtime, e.g. WildFly 8.1, that is not yet supported by the tooling, runtime detection usually detects it alright, but when you then click OK, the runtime+server are not added. And there is no error anywhere at all - we should fix that.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 1 month