[JBoss JIRA] Created: (JBIDE-8983) Move reusable code from ContentAssistantTestCase (jst module) to common module
by Viacheslav Kabanovich (JIRA)
Move reusable code from ContentAssistantTestCase (jst module) to common module
------------------------------------------------------------------------------
Key: JBIDE-8983
URL: https://issues.jboss.org/browse/JBIDE-8983
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: cdi (jsr-299), common, jsp/jsf/xml source editing
Affects Versions: 3.3.0.M1
Reporter: Viacheslav Kabanovich
Assignee: Viacheslav Kabanovich
Fix For: 3.3.0.M2
Content assist in CDI Seam config xml can be tested in the same way as that for EL in jsp.
For tests in the second case there is useful class ContentAssistantTestCase - but cdi module should not depend on jst module and besides ContentAssistantTestCase is bound to JSPMultiPageEditor and AutoContentAssistantProposal which are not used in cdi. Superclass in common module is needed with all the common functionality.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (JBIDE-8977) "Specify CDI Bean for the Injection Point" wizard should show/hide Default qualifier according to JSR-299 §2.3.1
by Daniel Azarov (JIRA)
"Specify CDI Bean for the Injection Point" wizard should show/hide Default qualifier according to JSR-299 §2.3.1
----------------------------------------------------------------------------------------------------------------
Key: JBIDE-8977
URL: https://issues.jboss.org/browse/JBIDE-8977
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdi (jsr-299)
Affects Versions: 3.3.0.M1
Reporter: Daniel Azarov
Assignee: Daniel Azarov
Fix For: 3.3.0.M2
EXECUTE: Create a CDI project (or enable CDI support on some existing project).
EXECUTE: Create
{code:title=FooBean.java|borderStyle=solid}
package org.test;
public class FooBean {
}
{code}
{code:title=FooBeanX.java|borderStyle=solid}
package org.test;
public class FooBeanX extends FooBean {
}
{code}
{code:title=TestBean.java|borderStyle=solid}
package org.test;
import javax.inject.Inject;
public class TestBean {
@Inject FooBean foo;
}
{code}
EXECUTE: Build the project.
ASSERT: There is a problem marker on @Inject FooBean foo: Multiple beans are eligible for injection to the injection point [JSR-299 §5.2.1]
EXECUTE: Click on the problem to show all the available quick fixes.
EXECUTE: Select Specify FooBeanX Bean for the Injection Point.
ASSERT: Specify CDI Bean for the Injection Point wizard appears.
EXECUTE: Click on "Create New Qualifier" button.
EXECUTE: Input "SomeNewQualifier" as a name of the qualifier and press Finish.
{color:red}*FAILURE:*{color} The Default qualifier still in "In The Bean" list
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (JBIDE-8958) Unremovable qualifiers in "Specify CDI Bean for the Injection Point" wizard in "In the Bean" tab should be in light gray color.
by Alexey Kazakov (JIRA)
Unremovable qualifiers in "Specify CDI Bean for the Injection Point" wizard in "In the Bean" tab should be in light gray color.
-------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-8958
URL: https://issues.jboss.org/browse/JBIDE-8958
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: cdi (jsr-299)
Affects Versions: 3.3.0.M1
Reporter: Alexey Kazakov
Assignee: Daniel Azarov
Fix For: 3.3.0.M2
EXECUTE: Create a CDI project (or enable CDI support on some existing project).
EXECUTE: Create
{code:title=FooBean.java|borderStyle=solid}
package org.test;
public class FooBean {
}
{code}
{code:title=FooBeanX.java|borderStyle=solid}
package org.test;
public class FooBeanX extends FooBean {
}
{code}
{code:title=Test.java|borderStyle=solid}
package org.test;
import javax.inject.Inject;
public class TestBean {
@Inject FooBean foo;
}
{code}
EXECUTE: Build the project.
ASSERT: There is a problem marker on @Inject FooBean foo: Multiple beans are eligible for injection to the injection point [JSR-299 §5.2.1]
EXECUTE: Click on the problem to show all the available quick fixes.
EXECUTE: Select Specify FooBeanX Bean for the Injection Point.
ASSERT: Specify CDI Bean for the Injection Point wizard appears.
EXECUTE: Click on "Create New Qualifier" button.
EXECUTE: Input "SomeNewQualifier" as a name of the qualifier and press Finish.
EXECUTE: Add SomeNewQualifier to "In the bean" tab.
{color:red}*FAILURE:*{color} SomeNewQualifier, Any, Default qualifiers are in black color.
{color:red}*ASSERT:*{color} SomeNewQualifier is in black colo but Any and Default are in light gray color since you can't remove them in the wizard.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (JBIDE-8957) If you create a new qualifier in "Specify CDI Bean for the Injection Point" wizard then this qualifier should appear "In the Bean" tab.
by Alexey Kazakov (JIRA)
If you create a new qualifier in "Specify CDI Bean for the Injection Point" wizard then this qualifier should appear "In the Bean" tab.
---------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-8957
URL: https://issues.jboss.org/browse/JBIDE-8957
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdi (jsr-299)
Affects Versions: 3.3.0.M1
Reporter: Alexey Kazakov
Assignee: Daniel Azarov
Fix For: 3.3.0.M2
EXECUTE: Create a CDI project (or enable CDI support on some existing project).
EXECUTE: Create
{code:title=FooBean.java|borderStyle=solid}
package org.test;
public class FooBean {
}
{code}
{code:title=FooBeanX.java|borderStyle=solid}
package org.test;
public class FooBeanX extends FooBean {
}
{code}
{code:title=Test.java|borderStyle=solid}
package org.test;
import javax.inject.Inject;
public class TestBean {
@Inject FooBean foo;
}
{code}
EXECUTE: Build the project.
ASSERT: There is a problem marker on @Inject FooBean foo: Multiple beans are eligible for injection to the injection point [JSR-299 §5.2.1]
EXECUTE: Click on the problem to show all the available quick fixes.
EXECUTE: Select Specify FooBeanX Bean for the Injection Point.
ASSERT: Specify CDI Bean for the Injection Point wizard appears.
EXECUTE: Click on "Create New Qualifier" button.
EXECUTE: Input "SomeNewQualifier" as a name of the qualifier and press Finish.
{color:red}*FAILURE:*{color} The SomeNewQualifier appears in "Available" tab instead of "In the bean" tab.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (JBIDE-8729) WS junit tests missing Greeter wsdl
by Brian Fitzpatrick (JIRA)
WS junit tests missing Greeter wsdl
-----------------------------------
Key: JBIDE-8729
URL: https://issues.jboss.org/browse/JBIDE-8729
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Webservices
Affects Versions: 3.3.0.M1
Reporter: Brian Fitzpatrick
Assignee: Feng Qian
Priority: Critical
Fix For: 3.2.0.M1
When running the automated tests for the WS component, an assertion is failing to find Greeter.wsdl
Error Message
http://127.0.0.1:8080/JBossWSTestProject/Greeter?wsdl
Stacktrace
java.io.FileNotFoundException: http://127.0.0.1:8080/JBossWSTestProject/Greeter?wsdl
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at sun.net.www.protocol.http.HttpURLConnection$6.run(HttpURLConnection.java:1491)
at java.security.AccessController.doPrivileged(Native Method)
at sun.net.www.protocol.http.HttpURLConnection.getChainedException(HttpURLConnection.java:1485)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1139)
at java.net.URLConnection.getContent(URLConnection.java:688)
at org.jboss.tools.ws.creation.core.test.command.JBossWSTopDownCommandTest.testDeployResult(JBossWSTopDownCommandTest.java:76)
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:232)
at junit.framework.TestSuite.run(TestSuite.java:227)
at junit.framework.TestSuite.runTest(TestSuite.java:232)
at junit.framework.TestSuite.run(TestSuite.java:227)
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.codehaus.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:75)
at org.codehaus.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:25)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3543)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3192)
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.codehaus.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:21)
at org.codehaus.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:109)
at org.codehaus.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:27)
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)
Caused by: java.io.FileNotFoundException: http://127.0.0.1:8080/JBossWSTestProject/Greeter?wsdl
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1434)
at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:379)
at java.net.HttpURLConnection.getResponseMessage(HttpURLConnection.java:445)
at org.jboss.tools.ws.creation.core.test.command.JBossWSTopDownCommandTest.testDeployResult(JBossWSTopDownCommandTest.java:75)
... 49 more
Standard Output
3
Retrieving document at 'file:/mnt/hudson_workspace/workspace/jbosstools-3.3_trunk.component--ws/sources/tests/org.jboss.tools.ws.creation.core.test/target/work/data/JBossWSTestProject/hello_world.wsdl
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (JBIDE-8943) SAXParseException is thrown during editing seam-beans.xml
by Alexey Kazakov (JIRA)
SAXParseException is thrown during editing seam-beans.xml
---------------------------------------------------------
Key: JBIDE-8943
URL: https://issues.jboss.org/browse/JBIDE-8943
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdi (jsr-299)
Affects Versions: 3.3.0.M1
Reporter: Alexey Kazakov
Assignee: Viacheslav Kabanovich
Fix For: 3.3.0.M2
org.xml.sax.SAXParseException: The content of elements must consist of well-formed character data or markup.
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.jboss.tools.cdi.seam.config.core.xml.SAXParser.parse(SAXParser.java:66)
at org.jboss.tools.cdi.seam.config.core.scanner.SeamDefinitionBuilder.createDefinition(SeamDefinitionBuilder.java:71)
at org.jboss.tools.cdi.seam.config.core.CDISeamConfigExtension.buildDefinitions(CDISeamConfigExtension.java:103)
at org.jboss.tools.cdi.core.CDICoreBuilder.build(CDICoreBuilder.java:196)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:717)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:191)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:228)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:281)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:284)
at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:340)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:363)
at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143)
at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (JBIDE-8307) There is no context menu for ${Project}->Project Archives->${Archive} node in Project Explorer
by Denis Golovin (JIRA)
There is no context menu for ${Project}->Project Archives->${Archive} node in Project Explorer
----------------------------------------------------------------------------------------------
Key: JBIDE-8307
URL: https://issues.jboss.org/browse/JBIDE-8307
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Archives
Affects Versions: 3.2.0.CR1
Reporter: Denis Golovin
Assignee: Rob Stryker
Fix For: 3.3.0.M1
Exception is reported in eclipse Error Log view when user requests context menu with right mouse click on actual archive:
java.lang.IllegalArgumentException: can't find IDorg.jboss.ide.eclipse.archives.ui.providers.initialSeparator
at org.eclipse.jface.action.ContributionManager.insertAfter(ContributionManager.java:334)
at org.eclipse.jface.action.ContributionManager.insertAfter(ContributionManager.java:325)
at org.jboss.ide.eclipse.archives.ui.providers.ArchivesActionProvider.menuAboutToShow2(ArchivesActionProvider.java:117)
at org.jboss.ide.eclipse.archives.ui.providers.ArchivesActionProvider.fillContextMenu(ArchivesActionProvider.java:92)
at org.eclipse.ui.navigator.NavigatorActionService$2.run(NavigatorActionService.java:221)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.navigator.NavigatorActionService.addCommonActionProviderMenu(NavigatorActionService.java:216)
at org.eclipse.ui.navigator.NavigatorActionService.fillContextMenu(NavigatorActionService.java:173)
at org.eclipse.ui.navigator.CommonNavigatorManager.fillContextMenu(CommonNavigatorManager.java:260)
at org.eclipse.ui.navigator.CommonNavigatorManager$4.menuAboutToShow(CommonNavigatorManager.java:275)
at org.eclipse.jface.action.MenuManager.fireAboutToShow(MenuManager.java:338)
at org.eclipse.jface.action.MenuManager.handleAboutToShow(MenuManager.java:469)
at org.eclipse.jface.action.MenuManager.access$1(MenuManager.java:465)
at org.eclipse.jface.action.MenuManager$2.menuShown(MenuManager.java:491)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:241)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1282)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1263)
at org.eclipse.swt.widgets.Menu._setVisible(Menu.java:199)
at org.eclipse.swt.widgets.Display.runPopups(Display.java:3581)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3158)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115)
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:369)
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:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)
at org.eclipse.equinox.launcher.Main.run(Main.java:1407)
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months