[JBoss JIRA] (JBIDE-17738) NPE in org.jboss.tools.common.web.WebUtil
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17738?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-17738:
--------------------------------------
Assignee: Alexey Kazakov
> NPE in org.jboss.tools.common.web.WebUtil
> -----------------------------------------
>
> Key: JBIDE-17738
> URL: https://issues.jboss.org/browse/JBIDE-17738
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core
> Affects Versions: 4.2.0.Beta3
> Reporter: Alexey Kazakov
> Assignee: Alexey Kazakov
> Fix For: 4.2.0.Beta3
>
>
> {code}
> org.jboss.tools.common.validation.JBTValidationException
> at org.jboss.tools.common.validation.ValidatorManager.validate(ValidatorManager.java:123)
> at org.jboss.tools.common.validation.ValidatorManager.validateInJob(ValidatorManager.java:81)
> at org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:78)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> Caused by: java.lang.NullPointerException
> at org.jboss.tools.common.web.WebUtils.getWebRootFolders(WebUtils.java:128)
> at org.jboss.tools.jst.web.WebUtils.getWebRootFolders(WebUtils.java:83)
> at org.jboss.tools.jst.web.WebUtils.getWebRootFolders(WebUtils.java:87)
> at org.jboss.tools.jst.web.kb.internal.validation.WebValidator.shouldFileBeValidated(WebValidator.java:70)
> at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateFile(ELValidator.java:273)
> at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validate(ELValidator.java:204)
> at org.jboss.tools.common.validation.ValidatorManager.validate(ValidatorManager.java:118)
> ... 3 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17735) JAX-RS Application wizard: double comments in generated class
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17735?page=com.atlassian.jira.plugi... ]
Xavier Coulon reassigned JBIDE-17735:
-------------------------------------
Assignee: Xavier Coulon
> JAX-RS Application wizard: double comments in generated class
> -------------------------------------------------------------
>
> Key: JBIDE-17735
> URL: https://issues.jboss.org/browse/JBIDE-17735
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.2.0.Beta2
> Reporter: Radoslav Rábara
> Assignee: Xavier Coulon
> Fix For: 4.2.0.Beta3
>
>
> JAX-RS Application class looks quite unusual, when is generated using JAX-RS Application wizard with option generate comments into default package.
> {code}
> @ApplicationPath("/rest")
> /**
> *
> */
> /**
> * @author rrabara
> *
> */
> public class App extends Application {
> }
> {code}
> When it is generated into user defined package, then there is just one java doc comment:
> {code}
> @ApplicationPath("/rest")
> /**
> * @author rrabara
> *
> */
> public class App extends Application {
> }
> {code}
> However, shouldn't the comment be above the annotation? It seems that it's the preferred way (e.g. see examples http://docs.oracle.com/javase/tutorial/java/annotations/predefined.html)
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17721) Param validation is not changed right after all ParamConverterProviders are removed from the project
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17721?page=com.atlassian.jira.plugi... ]
Xavier Coulon commented on JBIDE-17721:
---------------------------------------
[~rrabara],
I could not reproduce that bug with the latest version of the JAX-RS tooling, and I think I noticed and fixed that problem while working on other issues today (JBIDE-17717, JBIDE-17712 or JBIDE-17711). Can you please verify that the problem is also solved for you ?
Thanks !
> Param validation is not changed right after all ParamConverterProviders are removed from the project
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-17721
> URL: https://issues.jboss.org/browse/JBIDE-17721
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.2.0.Beta3
> Environment: JBoss WebServices Tools 1.7.0.Beta3-v20140628-0157-B555
> Reporter: Radoslav Rábara
> Assignee: Xavier Coulon
> Fix For: 4.2.0.Beta3
>
>
> Once there is at least one registered class, which implements ParamConverterProvider, in the project, the Param Validation (as implemented in JBIDE-15592) is bypassed (implemented in JBIDE-16763). However, after all ParamConverterProviders are unregistered/removed from the project, the Param Validation is still bypassed until the jax-rs validation is invoked by another action.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17717) Validation of @Path annotation with invalid argument cause error
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17717?page=com.atlassian.jira.plugi... ]
Xavier Coulon resolved JBIDE-17717.
-----------------------------------
Assignee: Xavier Coulon
Resolution: Done
Fixed for @Path annotation values on both Resource and Resource Methods
Fixed for missing '{' and '}' brackets.
> Validation of @Path annotation with invalid argument cause error
> ----------------------------------------------------------------
>
> Key: JBIDE-17717
> URL: https://issues.jboss.org/browse/JBIDE-17717
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.2.0.Beta3
> Environment: JBoss WebServices Tools 1.7.0.Beta3-v20140628-0157-B555
> Reporter: Radoslav Rábara
> Assignee: Xavier Coulon
> Priority: Critical
> Fix For: 4.2.0.Beta3
>
>
> An error occurs when the argument of the path annotation is invalid. It occurs not only when the file is saved but also during typing.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17721) Param validation is not changed right after all ParamConverterProviders are removed from the project
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17721?page=com.atlassian.jira.plugi... ]
Xavier Coulon reassigned JBIDE-17721:
-------------------------------------
Assignee: Xavier Coulon
> Param validation is not changed right after all ParamConverterProviders are removed from the project
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-17721
> URL: https://issues.jboss.org/browse/JBIDE-17721
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.2.0.Beta3
> Environment: JBoss WebServices Tools 1.7.0.Beta3-v20140628-0157-B555
> Reporter: Radoslav Rábara
> Assignee: Xavier Coulon
> Fix For: 4.2.0.Beta3
>
>
> Once there is at least one registered class, which implements ParamConverterProvider, in the project, the Param Validation (as implemented in JBIDE-15592) is bypassed (implemented in JBIDE-16763). However, after all ParamConverterProviders are unregistered/removed from the project, the Param Validation is still bypassed until the jax-rs validation is invoked by another action.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17563) Visual part of VPE is blank when JSP page opened
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17563?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov resolved JBIDE-17563.
--------------------------------------------
Resolution: Done
For non-html pages VPE will show error message which ask user to run with GTK2
> Visual part of VPE is blank when JSP page opened
> ------------------------------------------------
>
> Key: JBIDE-17563
> URL: https://issues.jboss.org/browse/JBIDE-17563
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.2.0.Beta2
> Environment: JBDS Beta2-v20140608-1040-B121, Linux
> Reporter: Vlado Pakan
> Assignee: Konstantin Marmalyukov
> Priority: Critical
> Fix For: 4.2.0.Beta3
>
>
> 1. Create JSF12 Kick start project
> 2. Open inputUserName.jsp in JBoss Tools JSP Editor
> ERROR: Visual part of editor is blank
> 3. Add some text to source of page
> ERROR: Visual part of editor is blank
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17455) JBT are not starting when property -Dorg.jboss.tools.vpe.loadxulrunner is set to false
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17455?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov resolved JBIDE-17455.
--------------------------------------------
Resolution: Done
> JBT are not starting when property -Dorg.jboss.tools.vpe.loadxulrunner is set to false
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-17455
> URL: https://issues.jboss.org/browse/JBIDE-17455
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.2.0.Beta2
> Environment: JBDS 8.0.0.Beta2-v20140525-2146-B104 Linux 64 bit Java Oracle 1.7.0_51
> Reporter: Vlado Pakan
> Assignee: Konstantin Marmalyukov
> Priority: Critical
> Fix For: 4.2.0.Beta3
>
>
> 1. Start JBT with -vmargs -Dorg.jboss.tools.vpe.loadxulrunner=false parameters
> 2. Import HTML5 project from JBoss Central
> 3. Open index.html page
> ERROR: Opened editor has empty title and visual part is also empty
> 4. Close JBT with with opened index.html page
> 5. Start JBT
> ERROR: JBT did not start
> There is couple of exceptions in log. This is last one:
> {noformat}
> !ENTRY org.eclipse.ui 4 0 2014-05-27 18:10:56.925
> !MESSAGE Unhandled event loop exception
> !STACK 0
> org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException)
> at org.eclipse.swt.SWT.error(SWT.java:4441)
> at org.eclipse.swt.SWT.error(SWT.java:4356)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:139)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3781)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3419)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1152)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1033)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:635)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:578)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:379)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:233)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> Caused by: java.lang.NullPointerException
> at org.jboss.tools.vpe.preview.editor.VpvEditor.formRequestToServer(VpvEditor.java:608)
> at org.jboss.tools.vpe.preview.editor.VpvEditor.reload(VpvEditor.java:600)
> at org.jboss.tools.vpe.preview.editor.VpvEditorPart.updateVisualEditorVisibility(VpvEditorPart.java:885)
> at org.jboss.tools.vpe.preview.editor.VpvEditorPart$5.controlResized(VpvEditorPart.java:437)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:235)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4462)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1412)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1393)
> at org.eclipse.swt.widgets.Control.setBounds(Control.java:1042)
> at org.eclipse.swt.widgets.Composite.setBounds(Composite.java:1435)
> at org.eclipse.swt.widgets.Control.setBounds(Control.java:879)
> at org.eclipse.swt.custom.SashFormLayout.layout(SashFormLayout.java:190)
> at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1652)
> at org.eclipse.swt.widgets.Composite.layout(Composite.java:1004)
> at org.eclipse.swt.widgets.Composite.layout(Composite.java:962)
> at org.jboss.tools.vpe.editor.xpl.CustomSashForm.layout(CustomSashForm.java:261)
> at org.jboss.tools.vpe.editor.xpl.CustomSashForm$1.handleEvent(CustomSashForm.java:159)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4462)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1412)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1393)
> at org.eclipse.swt.widgets.Control.setBounds(Control.java:1042)
> at org.eclipse.swt.widgets.Composite.setBounds(Composite.java:1435)
> at org.eclipse.swt.widgets.Control.setBounds(Control.java:879)
> at org.eclipse.swt.layout.GridLayout.layout(GridLayout.java:693)
> at org.eclipse.swt.layout.GridLayout.layout(GridLayout.java:197)
> at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1652)
> at org.eclipse.swt.widgets.Composite.setBounds(Composite.java:1438)
> at org.eclipse.swt.widgets.Control.setBounds(Control.java:879)
> at org.eclipse.swt.layout.GridLayout.layout(GridLayout.java:693)
> at org.eclipse.swt.layout.GridLayout.layout(GridLayout.java:197)
> at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1652)
> at org.eclipse.swt.widgets.Composite.setBounds(Composite.java:1438)
> at org.eclipse.swt.widgets.Control.setBounds(Control.java:851)
> at org.eclipse.swt.custom.CTabFolderLayout.layout(CTabFolderLayout.java:116)
> at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1652)
> at org.eclipse.swt.widgets.Composite.setBounds(Composite.java:1438)
> at org.eclipse.swt.widgets.Control.setBounds(Control.java:879)
> at org.eclipse.swt.layout.FillLayout.layout(FillLayout.java:204)
> at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1652)
> at org.eclipse.swt.widgets.Composite.setBounds(Composite.java:1438)
> at org.eclipse.swt.widgets.Control.setBounds(Control.java:879)
> at org.eclipse.swt.layout.FillLayout.layout(FillLayout.java:219)
> at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1652)
> at org.eclipse.swt.widgets.Composite.setBounds(Composite.java:1438)
> at org.eclipse.swt.widgets.Control.setBounds(Control.java:851)
> at org.eclipse.swt.custom.CTabFolderLayout.layout(CTabFolderLayout.java:116)
> at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1652)
> at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1658)
> at org.eclipse.swt.widgets.Composite.layout(Composite.java:1004)
> at org.eclipse.swt.custom.CTabFolder.runUpdate(CTabFolder.java:3755)
> at org.eclipse.swt.custom.CTabFolder$10.run(CTabFolder.java:3741)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
> ... 24 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17696) Enabling Maven Dependency Management job waits forever
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17696?page=com.atlassian.jira.plugi... ]
Denis Golovin edited comment on JBIDE-17696 at 7/1/14 2:55 PM:
---------------------------------------------------------------
It looks like ether GraphUpdateJob issue or JobManager.yieldRule issue for further debugging would be good to see job yielding tracing output, to enable that you need:
# .option file (see attachment)
# run eclipse with '-consoleLog -debug /path/to/the/.option'
Try to replicate the error again and attach console output to this issue.
Thanks.
was (Author: dgolovin):
It looks like ether GraphUpdateJob issue of JobManager.yieldRule issue for further debugging would be good to see job yielding tracing output, to enable that you need:
# .option file (see attachment)
# run eclipse with '-consoleLog -debug /path/to/the/.option'
Try to replicate the error again and attach console output to this issue.
Thanks.
> Enabling Maven Dependency Management job waits forever
> ------------------------------------------------------
>
> Key: JBIDE-17696
> URL: https://issues.jboss.org/browse/JBIDE-17696
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.2.0.Beta2
> Environment: OpenJDK 1.7, 64b
> Ubuntu 12.04, 64b
> Reporter: Rastislav Wagner
> Fix For: 4.2.x
>
> Attachments: .options, jstack1.out, jstack2.out, jstack_mvn.out, mvn.png, wait1.png, wait2.png
>
>
> I dont have exact steps to reproduce because this usually occurs after longer work. I'm testing various configurators (CDI/Seam/JAXRS..) using this scenario:
> 1. Create Dynamic Web Project
> 2. Convert to maven project (using Configure -> Convert to maven..)
> 3. Add some dependency
> 4. check if proper facet was enabled
> 5. delete project and repeat
> After trying this 10-15 times (sometimes more, sometimes less), during step 2 "Enabling Maven Dependency Management" job is waiting and never ends - see screenshot - there's always "Setting classpath containers".
> JVM thread dump attached.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months