[JBoss JIRA] Created: (JBIDE-8008) SeamProjectNewWizardTest.testJiraJbide1111 failure
by Alexey Kazakov (JIRA)
SeamProjectNewWizardTest.testJiraJbide1111 failure
--------------------------------------------------
Key: JBIDE-8008
URL: https://issues.jboss.org/browse/JBIDE-8008
Project: Tools (JBoss Tools)
Issue Type: Bug
Reporter: Alexey Kazakov
junit.framework.AssertionFailedError: Finish button is disabled at first wizard page in spite of created JBoss AS Runtime, Server, DB Connection and Seam Runtime and valid project name.
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.assertTrue(Assert.java:20)
at org.jboss.tools.seam.ui.test.wizard.SeamProjectNewWizardTest.testJiraJbide1111(SeamProjectNewWizardTest.java:130)
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.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 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.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:49)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
at org.eclipse.pde.internal.junit.runtime.RemotePluginTestRunner.main(RemotePluginTestRunner.java:62)
at org.eclipse.pde.internal.junit.runtime.UITestApplication$1.run(UITestApplication.java:116)
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:3527)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3174)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2629)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2593)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2427)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:670)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:663)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115)
at org.eclipse.pde.internal.junit.runtime.UITestApplication.start(UITestApplication.java:47)
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: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:619)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)
at org.eclipse.equinox.launcher.Main.run(Main.java:1407)
at org.eclipse.equinox.launcher.Main.main(Main.java:1383)
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 6 months
[JBoss JIRA] Created: (JBIDE-5284) Warning related to incorrect Seam project name don't appear
by Aliaksey Nis (JIRA)
Warning related to incorrect Seam project name don't appear
-----------------------------------------------------------
Key: JBIDE-5284
URL: https://jira.jboss.org/jira/browse/JBIDE-5284
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam
Affects Versions: 3.1.0.CR1
Environment: WindowsXP SP2
JBoss Tools
Version: 3.1.0.CR1
eclipse-SDK-3.5RC3-win32.zip
Build id: JBossTools-Update-3.1.0.v200911251807N-H130-RC1
JRE 1.6
Reporter: Aliaksey Nis
Priority: Optional
Attachments: NoWarningSeam.JPG
Related to JBIDE-5223
EXECUTE: New Seam project.
EXECUTE: Input name "blahblah+".
EXECUTE: Press next few times.
ASSERT: At step "Web module" button Next is in disable state, due to incorrect project name.
FAILURE: No warning appears. It appears only if you press Back, then Next again.
Screenshot attached.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 6 months
[JBoss JIRA] Created: (JBDS-904) JBDS 2.1 GA, JBPM and Seam
by Gary Lamperillo (JIRA)
JBDS 2.1 GA, JBPM and Seam
--------------------------
Key: JBDS-904
URL: https://jira.jboss.org/jira/browse/JBDS-904
Project: JBoss Developer Studio
Issue Type: Bug
Components: integration
Affects Versions: 2.1.0
Environment: JBDS 2.1 GA, EAP 5 Beta 2, Seam 2.2 , jBPM
Reporter: Gary Lamperillo
The jBPM New Process Definition wizard will not create a process in the EAR level. According to the Seam Reference manual, it should go at the EAR level. The Process Definition created by the wizard creates 3 files in a directory. the components.xml can not use the directory for the process definition, you get the following on deploy:
Caused by: org.jbpm.jpdl.JpdlException: [[ERROR] resource not found: /seam_drools10_15-ejb/jbpm_to_rules]
at org.jbpm.graph.def.ProcessDefinition.parseXmlResource(ProcessDefinition.java:162)
at org.jboss.seam.bpm.Jbpm.deployProcess(Jbpm.java:311)
at org.jboss.seam.bpm.Jbpm.installProcessDefinitions(Jbpm.java:294)
... 85 more
when using a location for the processdefinition.xml in this directory, you will get:
Caused by: java.lang.RuntimeException: could not deploy a process definition
at org.jboss.seam.bpm.Jbpm.installProcessDefinitions(Jbpm.java:300)
at org.jboss.seam.bpm.Jbpm.startup(Jbpm.java:80)
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.jboss.seam.util.Reflections.invoke(Reflections.java:22)
at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:144)
at org.jboss.seam.Component.callComponentMethod(Component.java:2249)
at org.jboss.seam.Component.callCreateMethod(Component.java:2172)
at org.jboss.seam.Component.newInstance(Component.java:2132)
... 75 more
Caused by: org.jbpm.jpdl.JpdlException: [[ERROR] resource not found: /seam_drools10_15-ejb/jbpm_to_rules/processdefinition.xml]
at org.jbpm.graph.def.ProcessDefinition.parseXmlResource(ProcessDefinition.java:162)
at org.jboss.seam.bpm.Jbpm.deployProcess(Jbpm.java:311)
at org.jboss.seam.bpm.Jbpm.installProcessDefinitions(Jbpm.java:294)
... 85 more
Is the plan for this process definition editor to work with Seam? Is there something missing in this setup?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 6 months