September 2010 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-6180) Hibernate Configuration editor looses focus sometimes after property is added

by Jiri Peterka (JIRA)

Hibernate Configuration editor looses focus sometimes after property is added ----------------------------------------------------------------------------- Key: JBIDE-6180 URL: https://jira.jboss.org/jira/browse/JBIDE-6180 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.1.0.GA Environment: JBDS 3.0.0 GA #50, Linux 64 Reporter: Jiri Peterka Fix For: 3.1.2 Steps: 1. Create Java project (hibtest) 2. Create Hibernate Configuration File (hibernate.cfg.xml) 3. Open hibernate.cfg.xml in Hibernate Configuration 3.0 XML Editor 4. Click on Properties, Add new property (hibernate.dialect) 5. Add value (org.hibernate.dialect.HSQLDialect) 6. Click Finish Try ty save with Ctrl+S ERROR: Sometimes editor focus is lost and you have to click back on editor or save it by pressing the toolbar button or menu item -- 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

15 years, 4 months

4
7
0 / 0

[JBoss JIRA] Created: (JBIDE-6866) Duplicate entries in XML catalog

by Juergen Zimmermann (JIRA)

Duplicate entries in XML catalog -------------------------------- Key: JBIDE-6866 URL: https://jira.jboss.org/browse/JBIDE-6866 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.2.0.M1 Reporter: Juergen Zimmermann Assignee: Rob Stryker The following .xsd files are already provided by WTP 3.2.1, and additionally JBossTools provides them inside plugins\org.jboss.ide.eclipse.as.core_...jar : javaee_6.xsd ejb-jar_3_1.xsd application_6.xsd web-common_3_0.xsd web-app_3_0.xsd javaee_web_services_client_1_3.xsd -- 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

15 years, 4 months

4
4
0 / 0

[JBoss JIRA] Created: (JBIDE-7080) GWT facet doesn't work correctly with Web Module 2.4

by Snjezana Peco (JIRA)

GWT facet doesn't work correctly with Web Module 2.4 ---------------------------------------------------- Key: JBIDE-7080 URL: https://jira.jboss.org/browse/JBIDE-7080 Project: Tools (JBoss Tools) Issue Type: Bug Components: GWT Affects Versions: 3.2.0.M2 Reporter: Snjezana Peco Attachments: gwt.png Steps to reproduce: - call a new Dynamic Web Project wizard - choose Web module 2.4 - add the GWT facet - set the Java facet to the 1.5 version if that is required - click Finish You will get an error dialog as in the attached screenshot. Solution: Creating the GWT servlet for Web Module 2.4 or changing a declaration of the GWT facet to require Web module >= 2.5 -- 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

15 years, 4 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-6623) [Designer] Using New Metadata Modeling Model Project wizard throws exception if not run in Designer perspective

by Brian Fitzpatrick (JIRA)

[Designer] Using New Metadata Modeling Model Project wizard throws exception if not run in Designer perspective --------------------------------------------------------------------------------------------------------------- Key: JBIDE-6623 URL: https://jira.jboss.org/browse/JBIDE-6623 Project: Tools (JBoss Tools) Issue Type: Bug Components: teiid Affects Versions: 3.2.0.M1 Reporter: Brian Fitzpatrick Assignee: Barry LaFond Fix For: 3.2.x When I created a new Model Project in a perspective other than the Designer perspective, I get an error in the new project wizard in a clean workspace. I was able to cancel out of the project wizard, manually select Open Project on the popup, and open the project to continue, but it would be good if we didn't automatically throw an issue if the wizard is available in other perspectives. Or perhaps pop up a dialog suggesting the user should pop into the Designer perspective for additional functionality (kind of like when Eclipse flips into the Debug perspective when it goes into Debug mode and offers the choice). !ENTRY org.teiid.designer.ui 4 0 2010-07-15 09:56:16.584 !MESSAGE Resource '/MyModelProject' is not open. !STACK 1 org.eclipse.core.internal.resources.ResourceException: Resource '/MyModelProject' is not open. at org.eclipse.core.internal.resources.Project.checkAccessible(Project.java:137) at org.eclipse.core.internal.resources.Project.getDescription(Project.java:379) at com.metamatrix.modeler.ui.wizards.NewModelProjectWizard.performFinish(NewModelProjectWizard.java:94) at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:811) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:430) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:234) 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.Display.runDeferredEvents(Display.java:3552) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3171) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:254) at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:274) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169) at org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:241) at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) 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.Display.runDeferredEvents(Display.java:3552) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3171) 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.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. - 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

15 years, 4 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-6081) Overall scrolling for 'Deployment' tab in JBoss AS Server configuration editor

by Denis Golovin (JIRA)

Overall scrolling for 'Deployment' tab in JBoss AS Server configuration editor ------------------------------------------------------------------------------ Key: JBIDE-6081 URL: https://jira.jboss.org/jira/browse/JBIDE-6081 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Reporter: Denis Golovin Assignee: Rob Stryker Priority: Minor Attachments: jboss-deploy-config-scroll.png Sometimes it happens and there is no place to show deployment settings for modules. We have several options to fix it: 1. Fix text layout on top of the tab to be justified 2. Add vertical scroll bar -- 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

15 years, 4 months

4
9
0 / 0

[JBoss JIRA] Created: (JBDS-612) EGT - BRMS-eclipse tool - properties shows odd syntax for timestamp

by Len DiMaggio (JIRA)

EGT - BRMS-eclipse tool - properties shows odd syntax for timestamp ------------------------------------------------------------------- Key: JBDS-612 URL: https://jira.jboss.org/jira/browse/JBDS-612 Project: Developer Studio Issue Type: Bug Components: visualeditor Affects Versions: 2.0.0.cr1 Environment: Version: 2.0.0.CR1 Build id: R200812221144 Build date: 12/22/2008 11:54 Reporter: Len DiMaggio Priority: Minor See the attached screen-shot - chars "TZ" begin and end the time displayed like this: 2009-02-03T01:42:14Z -- 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

15 years, 4 months

5
11
0 / 0

[JBoss JIRA] Created: (JBIDE-6093) Eclipse Guvnor Tooling causes validation errors on certain file types

by Jeff DeLong (JIRA)

Eclipse Guvnor Tooling causes validation errors on certain file types ---------------------------------------------------------------------- Key: JBIDE-6093 URL: https://jira.jboss.org/jira/browse/JBIDE-6093 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: drools Affects Versions: 3.1.0.CR2 Environment: JBoss Tools Nightly Build - Jboss Drools Guvnor 5.1.0.v20100226213N-H20-31764 Reporter: Jeff DeLong Eclipse Guvnor Tooling creates a new file with the name .filename.ext when a file is added to Guvnor. For xml files (.xml, .xsd, .html, .bpel, etc,) and java files, this causes the validators to report errors. E.g., "Content is not allowed in the prolog" and "Syntax errors on tokens, delete these tokens. This is because these files have the xml or java extension, hence the validator attempts to validate them. I have looking at the Preferences -> Validation, but cannot see a clever way to create a rule to exclude all files with a . at the front of the filename. Also, Eclipse Guvnor Tooling is not able to add files to the new for Guvnor 5.1 GlobalArea. -- 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

15 years, 4 months

6
23
0 / 0

[JBoss JIRA] Created: (JBIDE-6655) ModeShape Servers view Edit Server dialog description misleading

by Brian Fitzpatrick (JIRA)

ModeShape Servers view Edit Server dialog description misleading ---------------------------------------------------------------- Key: JBIDE-6655 URL: https://jira.jboss.org/browse/JBIDE-6655 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: modeshape Affects Versions: 3.2.0.M1 Reporter: Brian Fitzpatrick Assignee: Dan Florian Fix For: 3.2.x On the "Edit Server" dialog, perhaps change the description at the top to be "Define server details for this ModeShape server instance." The existing text is a bit misleading - "Define the server information where the ModeShape repositories are located" hints that you're defining the location for more than one server on this dialog, which is probably an incorrect assumption. -- 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

15 years, 4 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-6979) Published Locations shell for Modeshape is always shown on 1st monitor

by Jiri Peterka (JIRA)

Published Locations shell for Modeshape is always shown on 1st monitor ---------------------------------------------------------------------- Key: JBIDE-6979 URL: https://jira.jboss.org/browse/JBIDE-6979 Project: Tools (JBoss Tools) Issue Type: Bug Components: modeshape Affects Versions: 3.2.0.M2 Environment: JBT 3.2.0.m2 H309, Linux 64, Fedora 13, GKT Reporter: Jiri Peterka Have Eclipse opened on 2nd monitor 1. Create Project 2. Create file 3. Add file to modehape 4. Show published locations of the file Published Locations shell for Modeshape is always shown on 1st monitor. All other separate shells are opened correctly on the monitor where Eclipse is opened. -- 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

15 years, 4 months

4
4
0 / 0

[JBoss JIRA] Created: (JBDS-1180) EGT security dialog presents user with username/password text boxes that can be selected - but do not accept data

by Len DiMaggio (JIRA)

EGT security dialog presents user with username/password text boxes that can be selected - but do not accept data ----------------------------------------------------------------------------------------------------------------- Key: JBDS-1180 URL: https://jira.jboss.org/jira/browse/JBDS-1180 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: integration Affects Versions: 3.0.0.GA Environment: JBDS 3.0 BRMS 5.0.2 CR2 Reporter: Len DiMaggio Priority: Minor See linked JIRA for screenshot. -- 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

15 years, 4 months

7
32
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 September 2010