November 2009 - jbosstools-issues

[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, 2 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, 2 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, 2 months

1
4
0 / 0

[JBoss JIRA] Created: (JBIDE-5224) Some Plugins and Features has wrong or missing License or Copyright text.

by Vlado Pakan (JIRA)

Some Plugins and Features has wrong or missing License or Copyright text. ------------------------------------------------------------------------- Key: JBIDE-5224 URL: https://jira.jboss.org/jira/browse/JBIDE-5224 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0.M4 Reporter: Vlado Pakan Some of the plugins and features has wrong or missing License and Copyright text. Details: Features ( Choose Menu Help > About > Installation Details > Features Tab. > License Button): JBoss Archive Tools - org.jboss.ide.eclipse.archives.feature JBoss AS Tools - org.jboss.ide.eclipse.as.feature Hibernate Tools - org.hibernate.eclispe.feature JBoss Tools Rich Faces - org.jboss.tools.richfaces.feature Installed software (Choose Menu Help > About > Installation Details > Installed Software Tab. > Properties Button): wrong or missing copyright and license text: Common tools for jBPM 3 and jBPM - org.jboss.tools.jbpm.common.feature.feature.group Common tools for jBPM 3 and jBPM 4 Sources - org.jboss.tools.jbpm.common.source.feature.feature.group Flow Language Common Tools Sources - org.jboss.tools.flow.common.source.feature.feature.group JBoss BPEL Editor Sources - org.jboss.tools.bpel.source.feature.feature.group JBoss Maven Integration Source - org.jboss.tools.maven.source.feature.feature.group JBoss Maven Seam Integration Source - org.jboss.tools.maven.seam.source.feature.feature.group JBoss WebServices Tools - org.jboss.tools.ws.feature.feature.group jBPM 4 Graphical Editor and Tools Sources - org.jboss.tools.flow.jpdl4.source.feature.feature.group jBPM Convert - org.jboss.tools.jbpm.convert.feature.feature.group Project Examples - org.jboss.tools.project.examples.feature.feature.group Smooks Tools - org.jboss.tools.smooks.feature.feature.group wrong or missing license text Flow Languages Common Tools - org.jboss.tools.flow.common.feature.feature.group JBoss BPEL Editor - org.jboss.tools.bpel.feature.feature.group JBoss BPEL Editor SDK - org.jboss.tools.bpel.sdk.feature.feature.group JBoss ESB Tools - org.jboss.tools.esb.feature.feature.group JBoss Portlet - org.jboss.tools.portlet.feature.feature.group jBPM 4 Graphical Editor and Tools - org.jboss.tools.flow.jpdl4.feature.feature.group jBPM 4 Tools SDK - org.jboss.tools.jbpm4.sdk.feature.feature.group JMX Console - org.jboss.tools.jmx.feature.feature.group JMX Console SDK - org.jboss.tools.jmx.sdk.feature.feature.group JMX Console Source - org.jboss.tools.jmx.source.feature.feature.group Struts Tools - org.jboss.tools.struts_feature.feature.group wrong or missing copyright text JBoss Profiler - org.jboss.tools.profiler.feature.feature.group jBPM jPDL Tools - org.jbpm.gd.jpdl.feature.feature.group -- 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, 2 months

3
14
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, 2 months

6
42
0 / 0

[JBoss JIRA] Created: (JBDS-868) Add XSLT tooling to JBDS

by Max Rydahl Andersen (JIRA)

Add XSLT tooling to JBDS ------------------------ Key: JBDS-868 URL: https://jira.jboss.org/jira/browse/JBDS-868 Project: JBoss Developer Studio Issue Type: Feature Request Components: integration Affects Versions: 3.0.0.M2 Reporter: Max Rydahl Andersen Priority: Critical Fix For: 3.0.0.M3 The XSLT tooling from Galileo should be included to assist the SOA runtimes that has xslt support. -- 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, 2 months

4
5
0 / 0

[JBoss JIRA] Created: (JBIDE-5308) New JBPM3 Project - sample process definition missing

by Dominik Pospisil (JIRA)

New JBPM3 Project - sample process definition missing ----------------------------------------------------- Key: JBIDE-5308 URL: https://jira.jboss.org/jira/browse/JBIDE-5308 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0.M4 Environment: Linux x86_64 Reporter: Dominik Pospisil When creating new JBPM3 Project with sample process definiton, test case for process execution is created but the referenced process definition simple/processdefinition.xml is missing. The referenced file is not created at all. -- 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, 2 months

4
5
0 / 0

[JBoss JIRA] Created: (JBIDE-5309) JBPM 3.2.6 runtime - missing lib/activation.jar

by Dominik Pospisil (JIRA)

JBPM 3.2.6 runtime - missing lib/activation.jar ----------------------------------------------- Key: JBIDE-5309 URL: https://jira.jboss.org/jira/browse/JBIDE-5309 Project: Tools (JBoss Tools) Issue Type: Bug Components: jbpm Affects Versions: 3.1.0.M4 Environment: Linux x86_64 Reporter: Dominik Pospisil A JBPM3 project configured with JBPM 3.2.6 runtime can not be compiled, since the required lib/activation.jar is missing in JBPM 3.2.6 runtime. -- 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, 2 months

4
7
0 / 0

[JBoss JIRA] Created: (JBDS-648) Distribution should support updatesite or install into base eclipse

by Mark Diskin (JIRA)

Distribution should support updatesite or install into base eclipse -------------------------------------------------------------------- Key: JBDS-648 URL: https://jira.jboss.org/jira/browse/JBDS-648 Project: Developer Studio Issue Type: Feature Request Components: installer Environment: Windows Reporter: Mark Diskin The JBOSS tools is not not offered under development support options, but JBOSS Developer Studio is only provided as a standalone product. As a user of the base eclipse and Spring STS eclipse I'm used to be able to install JBOSS tools into those environments, but this is not covered by support for issues/patching. Could Developer Studio be provided as an update site offering or as a archive that could be installed into an existing eclipse environment. -- 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, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (JBDS-628) WTP's 3.0.3 EAR lib support is broken, need 3.0.4 to work

by Max Rydahl Andersen (JIRA)

WTP's 3.0.3 EAR lib support is broken, need 3.0.4 to work --------------------------------------------------------- Key: JBDS-628 URL: https://jira.jboss.org/jira/browse/JBDS-628 Project: Developer Studio Issue Type: Task Components: 3rdParty Affects Versions: 2.0.0.GA Reporter: Max Rydahl Andersen Priority: Blocker Fix For: 2.0.0.GA https://bugs.eclipse.org/bugs/show_bug.cgi?id=255243 prevents users from having empty and clean manifest.mf files https://bugs.eclipse.org/bugs/show_bug.cgi?id=263918 is related but not as bad since there is a workaround. -- 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, 2 months

3
9
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 November 2009