[JBoss JIRA] Created: (JBIDE-9658) jboss remote launch debug have a badly/noninformative preference on launch configuration
by Max Rydahl Andersen (JIRA)
jboss remote launch debug have a badly/noninformative preference on launch configuration
----------------------------------------------------------------------------------------
Key: JBIDE-9658
URL: https://issues.jboss.org/browse/JBIDE-9658
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: common/jst/core
Reporter: Max Rydahl Andersen
Assignee: Snjezana Peco
Priority: Critical
Fix For: 3.3.0.M4
The "JBoss Preferences" / JBoss Remote Configuration under "Remote Java Application" aren't very selfexplanatory or natural.
Need to find a better name or if they are actually relevant to have visible in UI:
Does this preference have to be visible ? Can I use selecting one of them as a way to say it should be considered ?
Then something like "Use for automatically detected applications" could be relevant - and title could be "Autodetection"
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] (JBIDE-10022) Multiple problem markers on the same broken EL
by Alexey Kazakov (Created) (JIRA)
Multiple problem markers on the same broken EL
----------------------------------------------
Key: JBIDE-10022
URL: https://issues.jboss.org/browse/JBIDE-10022
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsp/jsf/xml source editing
Affects Versions: 3.3.0.M4
Reporter: Alexey Kazakov
Assignee: Victor Rubezhny
Priority: Critical
Fix For: 3.3.0.Beta1
EXECUTE: Create a jsf kickstart project (2.0)
EXECUTE: Open greeting.xhtml
EXECUTE: Change #{msgs.greeting} to #{msgs.greeting1}. Save the file.
FAILURE: See Problems View. There are four warning messages instead of the only one.
I see there at lease two problems. First at all it seems that EclipseUIUtil.isOpenInActiveEditor(IFile) doesn't work anymore. It returns false for any file even if it is open in an active editor. So we use the cached page context of the file when we are editing it. This is a bug.
Second issue is that our PageContextFactory returns a context with many duplicated EL references for the same EL. It causes multiple problem markers for the same EL.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] Created: (JBIDE-9587) Obsolete verify-errors of faces-config.xml after classpathchanges
by Peter Rader (JIRA)
Obsolete verify-errors of faces-config.xml after classpathchanges
-----------------------------------------------------------------
Key: JBIDE-9587
URL: https://issues.jboss.org/browse/JBIDE-9587
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Eclipse Migration
Affects Versions: 3.2.1.Final
Reporter: Peter Rader
Assignee: Max Rydahl Andersen
Priority: Minor
The verification of faces-config.xml does not run after Classpathchanges.
On an jsf-project without jsf-librarys, the error occources correctly "error: Attribute converter-class references to XXX that does not implement interface javax.faces.convert.Converter".
Then, if you add the jsf-librarys to the classpath, the "Verification Problem" "error: Attribute converter-class references to XXX that does not implement interface javax.faces.convert.Converter" is NOT removed!
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] (JBIDE-10351) test failure in org.jboss.tools.jsf.vpe.jsf.test
by Nick Boldt (Created) (JIRA)
test failure in org.jboss.tools.jsf.vpe.jsf.test
------------------------------------------------
Key: JBIDE-10351
URL: https://issues.jboss.org/browse/JBIDE-10351
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: JSF
Affects Versions: 3.3.0.M5
Reporter: Nick Boldt
Assignee: Alexey Kazakov
Fix For: 3.3.0.M5
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_3.3.indi...
{code}
org.jboss.tools.jsf.vpe.jsf.test.JsfAllTests.testEditingSourceSelection
Failing for the past 1 build (Since Failed#35 )
Took 4 sec.
add description
Error Message
null
Stacktrace
junit.framework.AssertionFailedError: null
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.assertTrue(Assert.java:20)
at junit.framework.Assert.assertNotNull(Assert.java:214)
at junit.framework.Assert.assertNotNull(Assert.java:207)
at org.jboss.tools.jsf.vpe.jsf.test.jbide.JsfJbide2362Test.testEditingSourceSelection(JsfJbide2362Test.java:190)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at junit.framework.TestCase.runTest(TestCase.java:168)
at junit.framework.TestCase.runBare(TestCase.java:134)
at junit.framework.TestResult$1.protect(TestResult.java:110)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.framework.TestResult.run(TestResult.java:113)
at junit.framework.TestCase.run(TestCase.java:124)
at junit.framework.TestSuite.runTest(TestSuite.java:243)
at junit.framework.TestSuite.run(TestSuite.java:238)
at junit.framework.TestSuite.runTest(TestSuite.java:243)
at junit.framework.TestSuite.run(TestSuite.java:238)
at junit.framework.TestSuite.runTest(TestSuite.java:243)
at junit.framework.TestSuite.run(TestSuite.java:238)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
at junit.extensions.TestSetup$1.protect(TestSetup.java:23)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.extensions.TestSetup.run(TestSetup.java:27)
at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127)
at org.apache.maven.surefire.Surefire.run(Surefire.java:177)
at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:72)
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:135)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3563)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3212)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123)
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:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
at org.eclipse.equinox.launcher.Main.main(Main.java:1386)
Standard Output
full refresh is started
full refresh is finished
full refresh is started
full refresh is finished
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] (JBDS-1958) EDS Teiid Designer Generating a RESTEasy War file returns no value
by Johnathon Lee (Moved) (JIRA)
[ https://issues.jboss.org/browse/JBDS-1958?page=com.atlassian.jira.plugin.... ]
Johnathon Lee moved SOA-3653 to JBDS-1958:
------------------------------------------
Project: Developer Studio (JBoss Developer Studio) (was: JBoss Enterprise SOA Platform)
Key: JBDS-1958 (was: SOA-3653)
Affects Version/s: 4.1.0.GA
(was: 5.2.0 GA)
Assignee: Barry LaFond (was: Johnathon Lee)
Component/s: teiid
(was: Tooling)
(was: EDS)
Security: Public (was: Public)
Fix Version/s: (was: 5.2.0 GA)
> EDS Teiid Designer Generating a RESTEasy War file returns no value
> ------------------------------------------------------------------
>
> Key: JBDS-1958
> URL: https://issues.jboss.org/browse/JBDS-1958
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: teiid
> Affects Versions: 4.1.0.GA
> Reporter: Debbie Steigner
> Assignee: Barry LaFond
> Attachments: org.teiid.designer.dqp.ui.patch
>
>
> When following the published Teiid Designer documentation on generating a RESTEasy War file, a WAR file is produced with no error and deploys successfully. When "hitting" the web service, the HTTP status of 200 is returned with an empty body when there should be a result returned. This looks to be somewhat related to: https://issues.jboss.org/browse/TEIIDDES-1124. However, when checking the generated source code, it appears to be correct. Not sure if the generated src file is the actual generated class file that is being referenced. The procedure being "wrapped" with the RESTful Web Service executes fine from a Java client.
> This WAR file was generated on RHEL 6.1 (CSB) and the latest version of JBDS, 4.1.1.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months