[JBoss JIRA] (JBIDE-17700) Cannot deploy jsf war with eclipse luna and jboss 7.1.x
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17700?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-17700:
---------------------------------------------
oliver - when you see 0% publishing and its stuck - please try run jstack against the eclipse process and get the stacktrace/threaddump.
We've seen the issue before but never been able to replicate it thus we are very keen on understanding what is going on and finding the cause.
The JBTValidationException looks like a different error unfortunately ;/
> Cannot deploy jsf war with eclipse luna and jboss 7.1.x
> -------------------------------------------------------
>
> Key: JBIDE-17700
> URL: https://issues.jboss.org/browse/JBIDE-17700
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Environment: Win 7, Eclilpse Luna, JBoss Tools (via market place)
> Reporter: Oliver Pfau
> Priority: Critical
>
> When I publish my war to jboss 7.1 the following error occurs:
> An internal error occurred during: "Publishing to JBoss AS 7.1...".
> Could not initialize class de.schlichtherle.io.ArchiveControllers
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years
[JBoss JIRA] (JBIDE-17737) org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionAllTests failure
by Daniel Azarov (JIRA)
Daniel Azarov created JBIDE-17737:
-------------------------------------
Summary: org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionAllTests failure
Key: JBIDE-17737
URL: https://issues.jboss.org/browse/JBIDE-17737
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: seam2
Affects Versions: 4.2.0.Beta3
Reporter: Daniel Azarov
Attachments: org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionAllTests.txt
{code}
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionAllTests
0
0
Tests run: 8, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 0.265 sec <<< FAILURE!
Results :
Failed tests: testJBossAs42(org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionTest): expected:<1> but was:<0>
testJBossAs51(org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionTest): expected:<1> but was:<0>
testJBossAs70(org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionTest): expected:<1> but was:<0>
Tests run: 8, Failures: 3, Errors: 0, Skipped: 0
{code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years
[JBoss JIRA] (JBIDE-17737) org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionAllTests failure
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17737?page=com.atlassian.jira.plugi... ]
Daniel Azarov updated JBIDE-17737:
----------------------------------
Attachment: org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionAllTests.txt
> org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionAllTests failure
> --------------------------------------------------------------------------------
>
> Key: JBIDE-17737
> URL: https://issues.jboss.org/browse/JBIDE-17737
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: seam2
> Affects Versions: 4.2.0.Beta3
> Reporter: Daniel Azarov
> Attachments: org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionAllTests.txt
>
>
> {code}
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionAllTests
> 0
> 0
> Tests run: 8, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 0.265 sec <<< FAILURE!
> Results :
> Failed tests: testJBossAs42(org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionTest): expected:<1> but was:<0>
> testJBossAs51(org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionTest): expected:<1> but was:<0>
> testJBossAs70(org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionTest): expected:<1> but was:<0>
> Tests run: 8, Failures: 3, Errors: 0, Skipped: 0
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years
[JBoss JIRA] (JBIDE-17624) (un)checking Early Access while refreshing the connector logs an org.eclipse.swt.SWTException
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17624?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-17624:
---------------------------------------
The issue happens if you click the "Show Early access" action while the Central editor is refreshing the page.
The issue isn't OS specific. All you need to do is to click the action quickly.
The PR fixes the issue by disabling the "Show Early access" action (as well as "Select All"/"Deselect all" actions) during refreshing.
> (un)checking Early Access while refreshing the connector logs an org.eclipse.swt.SWTException
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-17624
> URL: https://issues.jboss.org/browse/JBIDE-17624
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.2.0.Beta2
> Reporter: Fred Bricon
> Assignee: Snjezana Peco
> Priority: Minor
> Fix For: 4.2.0.Beta3
>
>
> In Central > Software/Update page, (un)checking Early Access while refreshing the connector logs the following exception :
> {noformat}
> org.eclipse.swt.SWTException: Graphic is disposed
> at org.eclipse.swt.SWT.error(SWT.java:4441)
> at org.eclipse.swt.SWT.error(SWT.java:4356)
> at org.eclipse.swt.SWT.error(SWT.java:4327)
> at org.eclipse.swt.graphics.Image.getBounds(Image.java:1164)
> at org.eclipse.swt.widgets.Label.computeSize(Label.java:149)
> at org.eclipse.swt.layout.GridData.computeSize(GridData.java:491)
> at org.eclipse.swt.layout.GridLayout.layout(GridLayout.java:221)
> at org.eclipse.swt.layout.GridLayout.computeSize(GridLayout.java:164)
> at org.eclipse.swt.widgets.Composite.computeSize(Composite.java:234)
> at org.eclipse.swt.layout.GridData.computeSize(GridData.java:491)
> at org.eclipse.swt.layout.GridLayout.layout(GridLayout.java:221)
> at org.eclipse.swt.layout.GridLayout.computeSize(GridLayout.java:164)
> at org.eclipse.swt.widgets.Composite.computeSize(Composite.java:234)
> at org.eclipse.swt.layout.GridData.computeSize(GridData.java:491)
> at org.eclipse.swt.layout.GridLayout.layout(GridLayout.java:221)
> at org.eclipse.swt.layout.GridLayout.computeSize(GridLayout.java:164)
> at org.eclipse.swt.widgets.Composite.computeSize(Composite.java:234)
> at org.eclipse.swt.layout.GridData.computeSize(GridData.java:491)
> at org.eclipse.swt.layout.GridLayout.layout(GridLayout.java:221)
> at org.eclipse.swt.layout.GridLayout.layout(GridLayout.java:197)
> at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1290)
> at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1276)
> at org.eclipse.swt.widgets.Composite.layout(Composite.java:665)
> at org.jboss.tools.central.editors.xpl.DiscoveryViewer.updateFilters(DiscoveryViewer.java:628)
> at org.jboss.tools.central.editors.SoftwarePage.handleEarlyAccessChanged(SoftwarePage.java:536)
> at org.jboss.tools.central.editors.SoftwarePage.access$8(SoftwarePage.java:486)
> at org.jboss.tools.central.editors.SoftwarePage$5.widgetSelected(SoftwarePage.java:229)
> {noformat}
> scrolledContents is checked for disposed state, but the error occurs within layout()
> {code}
> if (this.scrolledContents != null && !this.scrolledContents.isDisposed()) {
> this.scrolledContents.layout(true, true); //crashes here
> ...
> }
> {code}
> I don't know how we can prevent that
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years
[JBoss JIRA] (JBIDE-17736) org.jboss.tools.seam.xml.test.SeamXMLAllTests failure
by Daniel Azarov (JIRA)
Daniel Azarov created JBIDE-17736:
-------------------------------------
Summary: org.jboss.tools.seam.xml.test.SeamXMLAllTests failure
Key: JBIDE-17736
URL: https://issues.jboss.org/browse/JBIDE-17736
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: seam2
Affects Versions: 4.2.0.Beta3
Reporter: Daniel Azarov
{code}
-------------------------------------------------------------------------------
Test set: org.jboss.tools.seam.xml.test.SeamXMLAllTests
-------------------------------------------------------------------------------
Tests run: 5, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 3.651 sec <<< FAILURE!
testDebugAttribute(org.jboss.tools.seam.xml.test.SeamXMLModelTest) Time elapsed: 1.878 sec <<< FAILURE!
junit.framework.AssertionFailedError: Validator failed to report an error in component org.jboss.seam.core.init1
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.assertTrue(Assert.java:22)
at junit.framework.TestCase.assertTrue(TestCase.java:192)
at org.jboss.tools.seam.xml.test.SeamXMLModelTest.testDebugAttribute(SeamXMLModelTest.java:108)
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:601)
at junit.framework.TestCase.runTest(TestCase.java:176)
at junit.framework.TestCase.runBare(TestCase.java:141)
at junit.framework.TestResult$1.protect(TestResult.java:122)
at junit.framework.TestResult.runProtected(TestResult.java:142)
at junit.framework.TestResult.run(TestResult.java:125)
at junit.framework.TestCase.run(TestCase.java:129)
at junit.framework.TestSuite.runTest(TestSuite.java:255)
at junit.framework.TestSuite.run(TestSuite.java:250)
at junit.framework.TestSuite.runTest(TestSuite.java:255)
at junit.framework.TestSuite.run(TestSuite.java:250)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:23)
at junit.extensions.TestSetup$1.protect(TestSetup.java:23)
at junit.framework.TestResult.runProtected(TestResult.java:142)
at junit.extensions.TestSetup.run(TestSetup.java:27)
at junit.framework.TestSuite.runTest(TestSuite.java:255)
at junit.framework.TestSuite.run(TestSuite.java:250)
at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104)
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:601)
at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164)
at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110)
at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175)
at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:123)
at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:86)
at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:35)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3806)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3444)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
at org.eclipse.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31)
at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:114)
at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37)
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:382)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236)
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:601)
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)
testComponentFile(org.jboss.tools.seam.xml.test.SeamXMLModelTest) Time elapsed: 0.001 sectestNavigationPagesComponent(org.jboss.tools.seam.xml.test.SeamXMLModelTest) Time elapsed: 0.001 sectestXMLModel(org.jboss.tools.seam.xml.test.SeamXMLModelTest) Time elapsed: 0.001 sectestXML23Model(org.jboss.tools.seam.xml.test.SeamXMLModelTest) Time elapsed: 0.033 sec
{code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years
[JBoss JIRA] (JBIDE-17624) (un)checking Early Access while refreshing the connector logs an org.eclipse.swt.SWTException
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17624?page=com.atlassian.jira.plugi... ]
Snjezana Peco reassigned JBIDE-17624:
-------------------------------------
Assignee: Snjezana Peco (was: Mickael Istria)
> (un)checking Early Access while refreshing the connector logs an org.eclipse.swt.SWTException
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-17624
> URL: https://issues.jboss.org/browse/JBIDE-17624
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.2.0.Beta2
> Reporter: Fred Bricon
> Assignee: Snjezana Peco
> Priority: Minor
> Fix For: 4.2.0.Beta3
>
>
> In Central > Software/Update page, (un)checking Early Access while refreshing the connector logs the following exception :
> {noformat}
> org.eclipse.swt.SWTException: Graphic is disposed
> at org.eclipse.swt.SWT.error(SWT.java:4441)
> at org.eclipse.swt.SWT.error(SWT.java:4356)
> at org.eclipse.swt.SWT.error(SWT.java:4327)
> at org.eclipse.swt.graphics.Image.getBounds(Image.java:1164)
> at org.eclipse.swt.widgets.Label.computeSize(Label.java:149)
> at org.eclipse.swt.layout.GridData.computeSize(GridData.java:491)
> at org.eclipse.swt.layout.GridLayout.layout(GridLayout.java:221)
> at org.eclipse.swt.layout.GridLayout.computeSize(GridLayout.java:164)
> at org.eclipse.swt.widgets.Composite.computeSize(Composite.java:234)
> at org.eclipse.swt.layout.GridData.computeSize(GridData.java:491)
> at org.eclipse.swt.layout.GridLayout.layout(GridLayout.java:221)
> at org.eclipse.swt.layout.GridLayout.computeSize(GridLayout.java:164)
> at org.eclipse.swt.widgets.Composite.computeSize(Composite.java:234)
> at org.eclipse.swt.layout.GridData.computeSize(GridData.java:491)
> at org.eclipse.swt.layout.GridLayout.layout(GridLayout.java:221)
> at org.eclipse.swt.layout.GridLayout.computeSize(GridLayout.java:164)
> at org.eclipse.swt.widgets.Composite.computeSize(Composite.java:234)
> at org.eclipse.swt.layout.GridData.computeSize(GridData.java:491)
> at org.eclipse.swt.layout.GridLayout.layout(GridLayout.java:221)
> at org.eclipse.swt.layout.GridLayout.layout(GridLayout.java:197)
> at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1290)
> at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1276)
> at org.eclipse.swt.widgets.Composite.layout(Composite.java:665)
> at org.jboss.tools.central.editors.xpl.DiscoveryViewer.updateFilters(DiscoveryViewer.java:628)
> at org.jboss.tools.central.editors.SoftwarePage.handleEarlyAccessChanged(SoftwarePage.java:536)
> at org.jboss.tools.central.editors.SoftwarePage.access$8(SoftwarePage.java:486)
> at org.jboss.tools.central.editors.SoftwarePage$5.widgetSelected(SoftwarePage.java:229)
> {noformat}
> scrolledContents is checked for disposed state, but the error occurs within layout()
> {code}
> if (this.scrolledContents != null && !this.scrolledContents.isDisposed()) {
> this.scrolledContents.layout(true, true); //crashes here
> ...
> }
> {code}
> I don't know how we can prevent that
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years
[JBoss JIRA] (JBIDE-17658) NPE in jax-rs as-you-type validation
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17658?page=com.atlassian.jira.plugi... ]
Xavier Coulon commented on JBIDE-17658:
---------------------------------------
no worries ;-)
> NPE in jax-rs as-you-type validation
> ------------------------------------
>
> Key: JBIDE-17658
> URL: https://issues.jboss.org/browse/JBIDE-17658
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.2.0.Beta3
> Reporter: Alexey Kazakov
> Assignee: Xavier Coulon
> Fix For: 4.2.0.Beta3
>
>
> I have a bunch of projects in my workspace and recently I noticed that there is a lot of the following exceptions in the log:
> {code}org.jboss.tools.common.validation.JBTValidationException
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:188)
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateString(AsYouTypeValidatorManager.java:205)
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateString(AsYouTypeValidatorManager.java:200)
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:254)
> at org.eclipse.wst.sse.ui.internal.reconcile.validator.ReconcileStepForValidator.validate(ReconcileStepForValidator.java:381)
> at org.eclipse.wst.sse.ui.internal.reconcile.validator.ReconcileStepForValidator.reconcileModel(ReconcileStepForValidator.java:259)
> at org.eclipse.jface.text.reconciler.AbstractReconcileStep.reconcile(AbstractReconcileStep.java:95)
> at org.eclipse.wst.sse.ui.internal.reconcile.validator.ValidatorStrategy.reconcile(ValidatorStrategy.java:269)
> at org.eclipse.wst.sse.ui.internal.reconcile.DocumentRegionProcessor.process(DocumentRegionProcessor.java:321)
> at org.eclipse.wst.sse.ui.internal.reconcile.StructuredRegionProcessor.process(StructuredRegionProcessor.java:258)
> at org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcessor$BackgroundThread.run(DirtyRegionProcessor.java:691)
> Caused by: java.lang.NullPointerException
> at org.jboss.tools.ws.jaxrs.ui.internal.validation.JaxrsMetamodelValidator.validate(JaxrsMetamodelValidator.java:426)
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:183)
> ... 10 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years
[JBoss JIRA] (JBDS-2844) Management API Server Adapter
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBDS-2844?page=com.atlassian.jira.plugin.... ]
Rob Stryker commented on JBDS-2844:
-----------------------------------
Also "Also related, not having the actual server code locally installed, " is accomplished. Servers with no runtimes is a working "thing" now.
> Management API Server Adapter
> -----------------------------
>
> Key: JBDS-2844
> URL: https://issues.jboss.org/browse/JBDS-2844
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: requirements, server
> Reporter: Burr Sutter
> Assignee: Max Rydahl Andersen
> Priority: Minor
> Fix For: 8.0.0.Beta3
>
>
> Related to JBIDE-14073 and EAP6-1
> The current EAP/JBossAS/Wildfly Server Adapter often interacts with the underlying file-system of the app server. Users have asked that the following scenarios be supported:
> - Remote Server Start/Stop
> - Remote Server Deployment/Undeployment
> - Remote Server single file update (e.g. html, js, jsp, xhtml, etc) with hot-deployment (to be worked out with the Wildfly team)
> - Remote Server Log Viewing
> and while the focus here in on remote servers, it should work just as well with localhost-based servers.
> Also related, not having the actual server code locally installed, being able to work wholly with a remote server (comes up in the Data Virt/Teiid world).
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years
[JBoss JIRA] (JBIDE-17658) NPE in jax-rs as-you-type validation
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17658?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-17658:
----------------------------------------
Oops, I reported the same issue twise. Sorry for that ;)
> NPE in jax-rs as-you-type validation
> ------------------------------------
>
> Key: JBIDE-17658
> URL: https://issues.jboss.org/browse/JBIDE-17658
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.2.0.Beta3
> Reporter: Alexey Kazakov
> Assignee: Xavier Coulon
> Fix For: 4.2.0.Beta3
>
>
> I have a bunch of projects in my workspace and recently I noticed that there is a lot of the following exceptions in the log:
> {code}org.jboss.tools.common.validation.JBTValidationException
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:188)
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateString(AsYouTypeValidatorManager.java:205)
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateString(AsYouTypeValidatorManager.java:200)
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:254)
> at org.eclipse.wst.sse.ui.internal.reconcile.validator.ReconcileStepForValidator.validate(ReconcileStepForValidator.java:381)
> at org.eclipse.wst.sse.ui.internal.reconcile.validator.ReconcileStepForValidator.reconcileModel(ReconcileStepForValidator.java:259)
> at org.eclipse.jface.text.reconciler.AbstractReconcileStep.reconcile(AbstractReconcileStep.java:95)
> at org.eclipse.wst.sse.ui.internal.reconcile.validator.ValidatorStrategy.reconcile(ValidatorStrategy.java:269)
> at org.eclipse.wst.sse.ui.internal.reconcile.DocumentRegionProcessor.process(DocumentRegionProcessor.java:321)
> at org.eclipse.wst.sse.ui.internal.reconcile.StructuredRegionProcessor.process(StructuredRegionProcessor.java:258)
> at org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcessor$BackgroundThread.run(DirtyRegionProcessor.java:691)
> Caused by: java.lang.NullPointerException
> at org.jboss.tools.ws.jaxrs.ui.internal.validation.JaxrsMetamodelValidator.validate(JaxrsMetamodelValidator.java:426)
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:183)
> ... 10 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years