October 2009 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBDS-796) wizard page to select file type is added

by Svetlana mukhina (JIRA)

wizard page to select file type is added ----------------------------------------- Key: JBDS-796 URL: https://jira.jboss.org/jira/browse/JBDS-796 Project: Developer Studio Issue Type: Task Components: Doc - Smooks Affects Versions: 2.0.0.GA Reporter: Svetlana mukhina Assignee: Olga Chukhutsina Fix For: 2.1.0 Describe the page and functionality provided -- 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

16 years, 3 months

4
8
0 / 0

[JBoss JIRA] Created: (JBIDE-1066) JBoss Server don't remove unused war files from deploy folder.

by Aliaksey Nis (JIRA)

JBoss Server don't remove unused war files from deploy folder. -------------------------------------------------------------- Key: JBIDE-1066 URL: http://jira.jboss.com/jira/browse/JBIDE-1066 Project: JBoss Tools Issue Type: Bug Environment: WindowsXP SP2 rhds-win32-1.0.0.beta2.jar Red Hat Developer Studio Version: 1.0.0 BETA2 Build: beta2 JDK 1.5_08 Reporter: Aliaksey Nis Create, run, remove from server and delete different projects. Look into deploy folder of JBoos server. Large amount of old war files, ds files, project folders can be found here. Dunno, if this is an issue, but think server must make some cleaning in deploy folder sometimes. :) -- 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

16 years, 3 months

5
18
0 / 0

[JBoss JIRA] Created: (JBIDE-4875) Various ui issues/suggestions to default file set

by Max Rydahl Andersen (JIRA)

Various ui issues/suggestions to default file set ------------------------------------------------- Key: JBIDE-4875 URL: https://jira.jboss.org/jira/browse/JBIDE-4875 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS Affects Versions: 3.1.0.M3 Reporter: Max Rydahl Andersen Assignee: Rob Stryker Fix For: 3.1.0.M3 Attachments: defaultfilesetfunkyness.png See attached screenshot. + would be good if one could promote an existing fileset to be included in default filterset for all servers/or the specific type since it is more or less impossible to get the filterset right without having a way to test it. -- 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

16 years, 3 months

4
7
0 / 0

[JBoss JIRA] Created: (JBDS-897) JSF 2.0 composition components support is implemented

by Svetlana mukhina (JIRA)

JSF 2.0 composition components support is implemented ------------------------------------------------------ Key: JBDS-897 URL: https://jira.jboss.org/jira/browse/JBDS-897 Project: JBoss Developer Studio Issue Type: Task Components: Doc - VisualWebTools, Doc - RHDS GSG Affects Versions: 2.1.0 Reporter: Svetlana mukhina Assignee: Svetlana mukhina Fix For: 2.1.0-doc VPE supports JSF 2.0 composition components. -- 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

16 years, 3 months

2
6
0 / 0

[JBoss JIRA] Created: (JBIDE-3767) allow single click publish

by arne anka (JIRA)

allow single click publish -------------------------- Key: JBIDE-3767 URL: https://jira.jboss.org/jira/browse/JBIDE-3767 Project: Tools (JBoss Tools) Issue Type: Feature Request Affects Versions: 3.0.0.GA Reporter: arne anka to publish incremental or full, several clicks are necessary: expand server -> select project -> select menu entry -> click. eve if the project is preselected, right click -> select entry -> click is still required. it would be nice, if those task could be solved by a single clik -- like the "publish to server" icon, which could be active even if a project is selected. -- 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

16 years, 3 months

4
25
0 / 0

[JBoss JIRA] Created: (JBDS-575) org.jboss.tools.jsf.vpe.jsf.test.JsfAllTests hangs JBDS build

by Nick Boldt (JIRA)

org.jboss.tools.jsf.vpe.jsf.test.JsfAllTests hangs JBDS build ------------------------------------------------------------- Key: JBDS-575 URL: https://jira.jboss.org/jira/browse/JBDS-575 Project: Developer Studio Issue Type: Bug Components: jsf Affects Versions: 2.0.0.cr1 Reporter: Nick Boldt This test gets stuck and prevents the build from completing (spaces and line breaks added for clarity): /qa/tools/opt/jdk1.5.0_15/jre/bin/java -Dwtp.autotest.noninteractive=true -Djbosstools.test.jboss.home=/home/hudson/hudson_workspace/workspace/devstudio-nightly/jbds-build/2.0.0.CR2/200901220518/tests/jboss/jboss-eap-4.3/jboss-as -Djbosstools.test.seam.1.2.1.eap.home=/home/hudson/hudson_workspace/workspace/devstudio-nightly/jbds-build/2.0.0.CR2/200901220518/tests/jboss/jboss-eap-4.3/seam -Djbosstools.test.seam.2.0.1.GA.home=/home/hudson/hudson_workspace/workspace/devstudio-nightly/jbds-build/requirements/seam-2.0.1.GA/jboss-seam-2.0.1.GA -Djbosstools.test.jboss.home.3.2=/home/hudson/hudson_workspace/workspace/devstudio-nightly/jbds-build/requirements/jbossas/jboss-3.2.8.SP1 -Djbosstools.test.jboss.home.4.0=/home/hudson/hudson_workspace/workspace/devstudio-nightly/jbds-build/requirements/jbossas/jboss-4.0.5.GA -Djbosstools.test.jboss.home.4.2=/home/hudson/hudson_workspace/workspace/devstudio-nightly/jbds-build/requirements/jbossas/jboss-4.2.1.GA -Xms128m -Xmx512m -Xbootclasspath/a:./emma.jar -XX:MaxPermSize=128m -classpath /home/hudson/hudson_workspace/workspace/devstudio-nightly/jbds-build/2.0.0.CR2/200901220518/tests/eclipse/plugins/org.eclipse.equinox.launcher_1.0.101.R34x_v20081125.jar org.eclipse.core.launcher.Main -application org.eclipse.test.uitestapplication -dev bin -data /home/hudson/hudson_workspace/workspace/devstudio-nightly/jbds-build/2.0.0.CR2/200901220518/tests/workspace -plugincustomization /home/hudson/hudson_workspace/workspace/devstudio-nightly/org.jboss.ide.eclipse.releng/builders/tests/plugin_customization.ini formatter=org.apache.tools.ant.taskdefs.optional.junit.XMLJUnitResultFormatter,org.jboss.tools.jsf.vpe.jsf.test.JsfAllTests.xml -testPluginName org.jboss.tools.jsf.vpe.jsf.test -classname org.jboss.tools.jsf.vpe.jsf.test.JsfAllTests -consolelog -nosplash -- 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

16 years, 3 months

3
17
0 / 0

[JBoss JIRA] Created: (JBIDE-3769) More functional CA for Smooks Conf file Editor

by Anton Klimkovich (JIRA)

More functional CA for Smooks Conf file Editor ---------------------------------------------- Key: JBIDE-3769 URL: https://jira.jboss.org/jira/browse/JBIDE-3769 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: smooks Affects Versions: 3.0.0.GA Reporter: Anton Klimkovich EXAMPLE for DataRecorder: <resource-config selector="decoder:DecoderName"> <resource>org.milyn.javabean.decoders.DateDecoder</resource> <param name="{CA}"></param> </resource-config> Proposal list should contain: Main: format Optional: locale-language locale-country verify-locale Is it possible to do or not? Think it will be very uselul. -- 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

16 years, 3 months

4
11
0 / 0

[JBoss JIRA] Created: (JBDS-876) Reverse engineering entities in a Sema project ties you to one database

by Shaun Appleton (JIRA)

Reverse engineering entities in a Sema project ties you to one database ----------------------------------------------------------------------- Key: JBDS-876 URL: https://jira.jboss.org/jira/browse/JBDS-876 Project: JBoss Developer Studio Issue Type: Bug Affects Versions: 2.1.0 Environment: JBDS linux and Windows Reporter: Shaun Appleton When I reverse engineer entities from a database you cannot change the database and reverse engineer different entities. It would appear reverse engineering entities ties you to one database To replicate: Create a Seam project and generate entities as described in http://docs.jboss.org/tools/2.1.0.GA/en/GettingStartedGuide/html_single/i... section 3.5.1 Then select the project and change the database to a different running database by changing the database connection profile in the seam settings. Verify the latest database can be pinged. Select the project and select File new generate entities and follow the dialogs through until you get to the Generate Entities Dialog. A <couldn't connect to database> error is shown in the database schema window. i.e. the new database connection is not picked up. It appears that when the database is changed in the Seam Settings connection profile the hibernate-console.properties are not kept in synch. So when an attempt to reverse engineer the database is tried the old connection settings are used even though they have recently been changed. If this is a technical limitation then there should be some warning in the docs that changing the database after generating the entities won't work. Plus have the connections profile bit greyed-out so it can't be altered. But ideally the hibernate-console.properties file should be synchronised with the Seam Settings connection profile. I tried deleting the hibernate-console.properties to try and force it to create a new hibernate-console.properties file with the correct settings but file but that didn't work either. -- 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

16 years, 3 months

5
14
0 / 0

[JBoss JIRA] Created: (JBIDE-4988) Install jpa-facet on <project-name>-ejb when EAR-deployable Seam project is created.

by Dmitry Geraskov (JIRA)

Install jpa-facet on <project-name>-ejb when EAR-deployable Seam project is created. ------------------------------------------------------------------------------------ Key: JBIDE-4988 URL: https://jira.jboss.org/jira/browse/JBIDE-4988 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Hibernate, Seam Affects Versions: 3.1.0.M3 Reporter: Dmitry Geraskov Assignee: Dmitry Geraskov Fix For: 3.1.0.M4 Jpa facet installed on the <project-name>, but need to be installed on the <project-name>-ejb. -- 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

16 years, 3 months

1
4
0 / 0

[JBoss JIRA] Created: (JBIDE-5033) JUnit Tests fail on Hudson x86_64 platforms

by Denis Golovin (JIRA)

JUnit Tests fail on Hudson x86_64 platforms ------------------------------------------- Key: JBIDE-5033 URL: https://jira.jboss.org/jira/browse/JBIDE-5033 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng Affects Versions: 3.1.0.M4 Reporter: Denis Golovin Assignee: Nick Boldt Fix For: 3.1.0.M4, 3.1.0.CR1 It seems to work for me locally on x86_64 linux but throws exception on hudson [java] !STACK 0 > [java] org.eclipse.swt.SWTError: XPCOM error -2147467259 > [java] at org.eclipse.swt.browser.Mozilla.error(Mozilla.java:2068) > [java] at org.eclipse.swt.browser.Mozilla.create(Mozilla.java:457) > [java] at org.eclipse.swt.browser.Browser.<init>(Browser.java:119) > [java] at org.jboss.tools.vpe.xulrunner.browser.XulRunnerBrowser.<init>(XulRunnerBrowser.java:87) > [java] at org.jboss.tools.vpe.xulrunner.editor.XulRunnerEditor.<init>(XulRunnerEditor.java:135) > [java] at org.jboss.tools.vpe.editor.mozilla.MozillaEditor$10.<init>(MozillaEditor.java:521) > [java] at org.jboss.tools.vpe.editor.mozilla.MozillaEditor.createPartControl(MozillaEditor.java:521) > [java] at org.jboss.tools.vpe.editor.VpeEditorPart.createVisualEditor(VpeEditorPart.java:911) > [java] at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditor.pageChange(JSPMultiPageEditor.java:210) > [java] at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditor.createPages(JSPMultiPageEditor.java:400) > [java] at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditorPart.createPartControl(JSPMultiPageEditorPart.java:125) > [java] at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:662) > [java] at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:462) > [java] at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:595) > [java] at org.eclipse.ui.internal.PartPane.setVisible(PartPane.java:313) > [java] at org.eclipse.ui.internal.presentations.PresentablePart.setVisible(PresentablePart.java:180) > [java] at org.eclipse.ui.internal.presentations.util.PresentablePartFolder.select(PresentablePartFolder.java:270) > [java] at org.eclipse.ui.internal.presentations.util.LeftToRightTabOrder.select(LeftToRightTabOrder.java:65) > [java] at org.eclipse.ui.internal.presentations.util.TabbedStackPresentation.selectPart(TabbedStackPresentation.java:473) > [java] at org.eclipse.ui.internal.PartStack.refreshPresentationSelection(PartStack.java:1256) > [java] at org.eclipse.ui.internal.PartStack.setSelection(PartStack.java:1209) > [java] at org.eclipse.ui.internal.PartStack.showPart(PartStack.java:1608) > [java] at org.eclipse.ui.internal.PartStack.add(PartStack.java:499) > [java] at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:103) > [java] at org.eclipse.ui.internal.PartStack.add(PartStack.java:485) > [java] at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:112) > [java] at org.eclipse.ui.internal.EditorSashContainer.addEditor(EditorSashContainer.java:63) > [java] at org.eclipse.ui.internal.EditorAreaHelper.addToLayout(EditorAreaHelper.java:225) > [java] at org.eclipse.ui.internal.EditorAreaHelper.addEditor(EditorAreaHelper.java:213) > [java] at org.eclipse.ui.internal.EditorManager.createEditorTab(EditorManager.java:778) > [java] at org.eclipse.ui.internal.EditorManager.openEditorFromDescriptor(EditorManager.java:677) > [java] at org.eclipse.ui.internal.EditorManager.openEditor(EditorManager.java:638) > [java] at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2854) > [java] at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2762) > [java] at org.eclipse.ui.internal.WorkbenchPage.access$11(WorkbenchPage.java:2754) > [java] at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2705) > [java] at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) > [java] at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2701) > [java] at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2685) > [java] at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2676) > [java] at org.jboss.tools.vpe.ui.test.VpeTest.openEditor(VpeTest.java:222) > [java] at org.jboss.tools.jsf.vpe.facelets.test.FaceletsComponentTest.performTestForFaceletComponent(FaceletsComponentTest.java:347) > [java] at org.jboss.tools.jsf.vpe.facelets.test.FaceletsComponentTest.testDebug(FaceletsComponentTest.java:54) > [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > [java] at java.lang.reflect.Method.invoke(Method.java:585) > [java] at junit.framework.TestCase.runTest(TestCase.java:164) > [java] at junit.framework.TestCase.runBare(TestCase.java:130) > [java] at junit.framework.TestResult$1.protect(TestResult.java:106) > [java] at junit.framework.TestResult.runProtected(TestResult.java:124) > [java] at junit.framework.TestResult.run(TestResult.java:109) > [java] at junit.framework.TestCase.run(TestCase.java:120) > [java] at junit.framework.TestSuite.runTest(TestSuite.java:230) > [java] at junit.framework.TestSuite.run(TestSuite.java:225) > [java] at junit.framework.TestSuite.runTest(TestSuite.java:230) > [java] at junit.framework.TestSuite.run(TestSuite.java:225) > [java] at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) > [java] at junit.extensions.TestSetup$1.protect(TestSetup.java:21) > [java] at junit.framework.TestResult.runProtected(TestResult.java:124) > [java] at junit.extensions.TestSetup.run(TestSetup.java:25) > [java] at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:354) > [java] at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:206) > [java] at org.eclipse.test.UITestApplication$3.run(UITestApplication.java:195) > [java] at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > [java] at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) > [java] at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3468) > [java] at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3115) > [java] at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405) > [java] at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369) > [java] at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221) > [java] at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) > [java] at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > [java] at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493) > [java] at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) > [java] at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) > [java] at org.eclipse.test.UITestApplication.runApplication(UITestApplication.java:138) > [java] at org.eclipse.test.UITestApplication.run(UITestApplication.java:60) > [java] at org.eclipse.test.UITestApplication.start(UITestApplication.java:210) > [java] at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) > [java] at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) > [java] at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) > [java] at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368) > [java] at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) > [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > [java] at java.lang.reflect.Method.invoke(Method.java:585) > [java] at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559) > [java] at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) > [java] at org.eclipse.equinox.launcher.Main.run(Main.java:1311) > [java] at org.eclipse.equinox.launcher.Main.main(Main.java:1287) > [java] at org.eclipse.core.launcher.Main.main(Main.java:34) -- 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

16 years, 3 months

6
42
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 October 2009