February 2011 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-6537) Helios support for JBT v3.1.1

by Darryl Miles (JIRA)

Helios support for JBT v3.1.1 ----------------------------- Key: JBIDE-6537 URL: https://jira.jboss.org/browse/JBIDE-6537 Project: Tools (JBoss Tools) Issue Type: Task Components: Hibernate, Seam Affects Versions: 3.1.1 Reporter: Darryl Miles Assignee: Max Rydahl Andersen Both the "Hibernate Tools" and "Seam Tools" for JBT v3.1.1 have too narrow version requirements for com.ibm.icu to be compatible with Helios. Helios comes with com.ibm.icu v4.2.1 Currently the version requirements are set to [3.4.4,4.1.0) so this should be changed at a minimum to [3.4.4,4.3.0) to allow both these JBT components to install on top of Helios. However you should consider using an even wider version width of [3.4.4,5) since it is accepted practise that minor version increments are backwardly compatible and a major version change is potentially API breaking. This means that generally JBT should (and is expected to) work on all future versions of com.ibm.icu up until version 5 is released. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

4
7
0 / 0

[JBoss JIRA] Created: (JBDS-1474) List of update sites is extended after first update with eclipse update sites

by Denis Golovin (JIRA)

List of update sites is extended after first update with eclipse update sites ----------------------------------------------------------------------------- Key: JBDS-1474 URL: https://issues.jboss.org/browse/JBDS-1474 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: Build Affects Versions: 4.0.0.CR1 Reporter: Denis Golovin -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

4
10
0 / 0

[JBoss JIRA] Created: (JBIDE-8338) Seam Components View ignores Filter settings for view

by Denis Golovin (JIRA)

Seam Components View ignores Filter settings for view ----------------------------------------------------- Key: JBIDE-8338 URL: https://issues.jboss.org/browse/JBIDE-8338 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.2.0.CR2 (tentative) Reporter: Denis Golovin Assignee: Alexey Kazakov Attachments: Screenshot.png -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

4
14
0 / 0

[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

3
7
0 / 0

[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

7
10
0 / 0

[JBoss JIRA] Created: (JBIDE-2242) Taglib declaration <%@ taglib uri="" is inserted after DnD tags from Pallete on some XHTML pages in default Seam web project.

by Anton Klimkovich (JIRA)

Taglib declaration <%@ taglib uri="" is inserted after DnD tags from Pallete on some XHTML pages in default Seam web project. ----------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-2242 URL: http://jira.jboss.com/jira/browse/JBIDE-2242 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 2.1.0.GA Reporter: Anton Klimkovich Assigned To: Maxim Areshkau Priority: Minor EXECUTE: Create default Seam project EXECUTE: Open menu.xhtml EXECUTE: Make DnD of JBoss Ajax4jsf tag on the page from Palette. FAILURE: <%@ taglib uri="http://java.sun.com/jsf/html" prefix="h"%> inserted instead of xmlns:h="http://java.sun.com/jsf/html" ASSERT: Seam gen should create xhtml pages with declaration that tells it's a XHTML. (<!DOCTYPE composition PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">) All pages w/o declaration are attached. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

6
9
0 / 0

[JBoss JIRA] Created: (JBIDE-6228) "JBoss Maven Seam Integration" modifies web.xml during project import

by Clemens Fuchslocher (JIRA)

"JBoss Maven Seam Integration" modifies web.xml during project import --------------------------------------------------------------------- Key: JBIDE-6228 URL: https://jira.jboss.org/jira/browse/JBIDE-6228 Project: Tools (JBoss Tools) Issue Type: Bug Components: integration, maven, Seam Affects Versions: 3.1.0.GA Environment: Eclipse 3.5.2, m2eclipse 0.10.0, JBoss Tools 3.1.0, 1.6.0-20, Debian GNU/Linux 5.0 Reporter: Clemens Fuchslocher Used software: * Eclipse IDE for Java EE Developers (http://www.eclipse.org/downloads/packages/eclipse-ide-java-ee-developers/...) * m2eclipse 0.10.0.20100209-0800 (http://m2eclipse.sonatype.org/sites/m2e) * JBoss Maven Integration 1.0.0.v201003050540R-H56-GA (http://download.jboss.org/jbosstools/updates/stable/galileo/) * JBoss Maven Seam Integration 1.0.0.v201003050540R-H56-GA (http://download.jboss.org/jbosstools/updates/stable/galileo/) Steps to reproduce: 1. Import the seamIntegration project from http://anonsvn.jboss.org/repos/richfaces/tags/3.3.3.Final/samples/seamInt...: File -> New -> Other... -> Checkout Maven Projects from SCM -> Next -> SCM URL: svn, http://anonsvn.jboss.org/repos/richfaces/tags/3.3.3.Final/samples/seamInt... -> Finish 2. Compare the imported web.xml with the original one: http://anonsvn.jboss.org/repos/richfaces/tags/3.3.3.Final/samples/seamInt.... 3. Problem: The file is completely rewritten. All comments are lost. -- 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

6
10
0 / 0

[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

7
23
0 / 0

[JBoss JIRA] Created: (JBIDE-5720) EAR Libraries in Dynamic Web Project

by Burr Sutter (JIRA)

EAR Libraries in Dynamic Web Project ------------------------------------ Key: JBIDE-5720 URL: https://jira.jboss.org/jira/browse/JBIDE-5720 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: core Environment: jbdevstudio-win32-3.0.0.v201001060655N-H50-CR1 Reporter: Burr Sutter Attachments: EAR_Libraries.jpg Creation of a New Dynamic Web Project adds "EAR Libraries" - that does not make sense because I (the user) am building a WAR and I do not want anything to do with an EAR in this case. -- 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

4
11
0 / 0

[JBoss JIRA] Created: (JBIDE-1354) Runtimes should be configurable with respect to what jars to return for certain runtimes

by Max Andersen (JIRA)

Runtimes should be configurable with respect to what jars to return for certain runtimes ---------------------------------------------------------------------------------------- Key: JBIDE-1354 URL: http://jira.jboss.com/jira/browse/JBIDE-1354 Project: JBoss Tools Issue Type: Feature Request Components: JBossAS Reporter: Max Andersen Fix For: 2.1 deploy only runtime could have preferences to control which jars they would actually return for various facets etc. optimally these would actually work on on any of our runtimes and just use variables/clever-defaults depending and allow users to override them if necessary. The user should be able to point to jars in a project, workspace, filesystem, classpath library, maven/ivy dependency even ...etc. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

6
26
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues February 2011