[JBoss JIRA] (JBIDE-15304) NullPointerExceptions in JAX-RS doesn't report what project is affected
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15304?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-15304:
---------------------------------------
Was it reopened because there is no description how to replicate this issue?
> 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: Denis Golovin
> 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
[JBoss JIRA] (JBIDE-15304) NullPointerExceptions in JAX-RS doesn't report what project is affected
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15304?page=com.atlassian.jira.plugi... ]
Denis Golovin reassigned JBIDE-15304:
-------------------------------------
Assignee: Denis Golovin (was: Nick Boldt)
> 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: Denis Golovin
> 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
[JBoss JIRA] (JBIDE-15622) Automatically open/send report when log has error
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15622?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-15622:
----------------------------------------
About Precondition 1 " We need to create “special” project in JIRA to primary report issue to with anonymous (or dedicated) user.":
Do we really need a new project? What about reporting to JBT or JBDS project without any component set, and then the bug reviewer would route the project to the right component, and may assign a Fix Version.
About Action 7 "Return link to created JIRA":
What about directly opening JIRA URL in the internal browser?
> Automatically open/send report when log has error
> -------------------------------------------------
>
> Key: JBIDE-15622
> URL: https://issues.jboss.org/browse/JBIDE-15622
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: common/jst/core
> Affects Versions: 4.1.1.Alpha1
> Reporter: Mickael Istria
>
> *Where to:*
> 1. Error Dialog – when problem occurs Error Dialog appears and provides opportunity to report a bug
> 2. Error Log View (Tool-bar, Menu, Context menu) – report problem for selected stack-trace
> 3. Help->Report Problem Dialog – report problem which may be not related with any exceptions
> 1. and 2. should create issues in “special” project (see Preconditions). 3. may create issues directly to project Tools (JBoss Tools)?
> *Feature list:*
> 1. Log in/Anonymous bug reporting (If the user has login to JIRA he can report issues with it. Or he can do it anonymously)
> 2. Check Exception Stack-trace for duplicate
> 3. Report should contain all needed (useful) information about user's environment (JDK/JRE version, eclipse version, OS version, configuration, etc)
> 4. As much as possible fields should be filled up automatically (project, issue type, priority, component/s, affects version/s, environment) may be some of them should be filled up later by Administrator
> 5. User should be able to see all the data he is going to send
> 6. Show communication errors
> 7. Return link to created JIRA
> 8. Inform user about the general/common process of bug reporting (see Work-flow)
> 9. Option to attach log file
> 10. Option to attach screen-shot
> *Preconditions:*
> 1. We need to create “special” project in JIRA to primary report issue to with anonymous (or dedicated) user.
> 2. We need person as Administrator (QE-?) to periodically verifying issue from “special” project.
> *Work-flow:*
> 1. User decides/agrees to report the problem (see list Where to)
> 2. Report Problem dialog appears, user fills up the form
> 2. Dialog checks for existing exception stack-traces (when stack-trace available) or by key-words from field summary.
> 3. If validation passes dialog creates issue in “special” project of JIRA (see Preconditions)
> 4. User gets link to created issue and short description of what will happen next. (features 7. 8.)
> 5. Administrator should periodically check “special” project and verify all issues. Administrator may reject issue or correct (versions, components etc, if needed) and move to project Tools (JBoss Tools).
> *Primary Description:*
> JBT should set up an ILogListener on the Eclipse log and send an error report whenever something is logged as error.
> As it's probably not possible to send the error report without asking users, it should show the "Report problem" page.
> NetBeans does that and has reported an actual quality benefit.
--
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
[JBoss JIRA] (JBIDE-15605) Validation problem in faces-config.xml for JSF 2.2 projects
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15605?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-15605:
---------------------------------------------
+1 for the PR to remove redundant shcemas.
> Validation problem in faces-config.xml for JSF 2.2 projects
> -----------------------------------------------------------
>
> Key: JBIDE-15605
> URL: https://issues.jboss.org/browse/JBIDE-15605
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Affects Versions: 4.2.0.Alpha1
> Reporter: Alexey Kazakov
> Assignee: Viacheslav Kabanovich
> Fix For: 4.2.0.Alpha1
>
>
> 1. Create a JSF 2.2 KickStart project (or a dynamic web project with JSF 2.2. facet).
> 2. There is an error in problems view:
> Referenced file contains errors (file:/home/igels/Projects/jbt-4.0/contribution/jbosstools-jst/plugins/org.jboss.tools.jst.web/catalog/web-facesconfig_2_2.xsd). For more information, right click on the message in the Problems View and select "Show Details..."
> Is it a real problem in the web-facesconfig_2_2.xsd we bundle with JBT or maybe it's an upstream problem with WTP XML validation?
> BTW, http://xmlns.jcp.org/xml/ns/javaee/web-facesconfig_2_2.xsd is already registered in XML Catalog by WTP. There is no need to keep our own version in XML Catalog:
> {code}
> Entry element: URI
> Location: dtdsAndSchemas/web-facesconfig_2_2.xsd in jar file home/igels/Java/eclipse-4.3/workspace/designtime/contribution/.metadata/.plugins/org.eclipse.pde.core/.bundle_pool/plugins/org.eclipse.jst.standard.schemas_1.2.100.v201305161752.jar
> URI: jar:file:/home/igels/Java/eclipse-4.3/workspace/designtime/contribution/.metadata/.plugins/org.eclipse.pde.core/.bundle_pool/plugins/org.eclipse.jst.standard.schemas_1.2.100.v201305161752.jar!/dtdsAndSchemas/web-facesconfig_2_2.xsd
> Key type: Namespace name
> Key: http://xmlns.jcp.org/xml/ns/javaee/web-facesconfig_2_2.xsd
> {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
[JBoss JIRA] (JBIDE-16071) Duplicate cheat sheet options in Project Examples Preferences
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16071?page=com.atlassian.jira.plugi... ]
Michelle Murray updated JBIDE-16071:
------------------------------------
Attachment: Central_cheatsheet.png
> Duplicate cheat sheet options in Project Examples Preferences
> -------------------------------------------------------------
>
> Key: JBIDE-16071
> URL: https://issues.jboss.org/browse/JBIDE-16071
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 4.1.1.CR1
> Reporter: Michelle Murray
> Attachments: Central_cheatsheet.png
>
>
> Click Window > Preferences > JBoss Tools > Project Examples.
> The check box options include 'show readme/cheatsheet file' and then further down specifically for cheat sheets radio buttons for cheat sheet behavior.
> !Central_cheatsheet.png!
> I think the labelling of 'show readme/cheatsheet file' is left over from earlier. With the new cheat sheet functionality, I think that option should just read 'show readme file'. And then the radio button 'Always show' etc. deal with cheat sheets.
--
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
[JBoss JIRA] (JBIDE-16071) Duplicate cheat sheet options in Project Examples Preferences
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16071?page=com.atlassian.jira.plugi... ]
Michelle Murray updated JBIDE-16071:
------------------------------------
Affects: Documentation (Ref Guide, User Guide, etc.)
> Duplicate cheat sheet options in Project Examples Preferences
> -------------------------------------------------------------
>
> Key: JBIDE-16071
> URL: https://issues.jboss.org/browse/JBIDE-16071
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 4.1.1.CR1
> Reporter: Michelle Murray
> Attachments: Central_cheatsheet.png
>
>
> Click Window > Preferences > JBoss Tools > Project Examples.
> The check box options include 'show readme/cheatsheet file' and then further down specifically for cheat sheets radio buttons for cheat sheet behavior.
> !Central_cheatsheet.png!
> I think the labelling of 'show readme/cheatsheet file' is left over from earlier. With the new cheat sheet functionality, I think that option should just read 'show readme file'. And then the radio button 'Always show' etc. deal with cheat sheets.
--
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
[JBoss JIRA] (JBIDE-16071) Duplicate cheat sheet options in Project Examples Preferences
by Michelle Murray (JIRA)
Michelle Murray created JBIDE-16071:
---------------------------------------
Summary: Duplicate cheat sheet options in Project Examples Preferences
Key: JBIDE-16071
URL: https://issues.jboss.org/browse/JBIDE-16071
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: project-examples
Affects Versions: 4.1.1.CR1
Reporter: Michelle Murray
Attachments: Central_cheatsheet.png
Click Window > Preferences > JBoss Tools > Project Examples.
The check box options include 'show readme/cheatsheet file' and then further down specifically for cheat sheets radio buttons for cheat sheet behavior.
!Central_cheatsheet.png!
I think the labelling of 'show readme/cheatsheet file' is left over from earlier. With the new cheat sheet functionality, I think that option should just read 'show readme file'. And then the radio button 'Always show' etc. deal with cheat sheets.
--
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