February 2010 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-5081) Content Assist doesn't work for bundle's messages specified outside tags.

by Denis Maliarevich (JIRA)

Content Assist doesn't work for bundle's messages specified outside tags. ------------------------------------------------------------------------- Key: JBIDE-5081 URL: https://jira.jboss.org/jira/browse/JBIDE-5081 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.1.0.M3 Reporter: Denis Maliarevich Assignee: Maxim Areshkau Fix For: 3.1.0.CR1 Content Assist doesn't work for bundle's messages specified outside tags. Steps to reproduce: 1) Launch JBDS. 2) Create JSF Kickstart project. 3) Open inputUserName.jsp page. 4) Type #{Message.} in any place outside any tag. 5) Press Ctrl+Space. 6) FAILURE: "Content Assist not available at the current location" status message will appear. 7) To check content assist put cursor inside the following tag after dot in #{Message. : <h1><h:outputText value="#{Message.header}"/></h1> 8) Press Ctrl+Space. 9) CORRECTLY: Content Assist for bundle's messages will appear. -- 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, 4 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-3966) Page Design Options don't work for external pages

by Yura Zhishko (JIRA)

Page Design Options don't work for external pages ------------------------------------------------- Key: JBIDE-3966 URL: https://jira.jboss.org/jira/browse/JBIDE-3966 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.0.0.GA Reporter: Yura Zhishko Assignee: Maxim Areshkau 1) DND some page (JSP, XHTML, JSPX) into studio 2) Open Page Design Options 3) Choose any tab (Substituted EL Expression, Include CSS file ...) 4) Set any variables 5) Press OK. 6) Open Page Design Options ASSERT: All variables from previous step should be saved RESULT: All is clear. There are no any variables on tabs. -- 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, 4 months

5
15
0 / 0

[JBoss JIRA] Created: (JBIDE-5107) NPE during setting preferences for VPE

by Yura Zhishko (JIRA)

NPE during setting preferences for VPE -------------------------------------- Key: JBIDE-5107 URL: https://jira.jboss.org/jira/browse/JBIDE-5107 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.1.0.M4 Reporter: Yura Zhishko Assignee: Denis Maliarevich 1) Create JSF KickStart project 2) Open inputUserName.jsp 3) Open Preferences 4) Select "Select the default active editor's tab" and change it to "Source" 5) Press "Ok" 6) Open hello.jsp page 7) Select inputUserName.jsp again 8) Open Preferences 9) Select "Select the default active editor's tab" and change it to "Visual/Source" 10) Press "OK" RESULT: java.lang.NullPointerException at org.jboss.tools.vpe.editor.VpeEditorPart.updatePartAccordingToPreferences(VpeEditorPart.java:1170) at org.jboss.tools.vpe.editor.preferences.VpePreferencesPage.performOk(VpePreferencesPage.java:169) at org.jboss.tools.common.model.ui.preferences.TabbedPreferencesPage.performOk(TabbedPreferencesPage.java:155) at org.eclipse.jface.preference.PreferenceDialog$13.run(PreferenceDialog.java:964) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.runtime.Platform.run(Platform.java:888) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:48) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) at org.eclipse.jface.preference.PreferenceDialog.okPressed(PreferenceDialog.java:944) at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.okPressed(FilteredPreferenceDialog.java:453) at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.okPressed(WorkbenchPreferenceDialog.java:169) at org.eclipse.jface.preference.PreferenceDialog.buttonPressed(PreferenceDialog.java:233) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3880) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3473) 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.dialogs.WorkbenchPreferenceDialog.open(WorkbenchPreferenceDialog.java:211) at org.jboss.tools.vpe.editor.preferences.VpeEditorPreferencesPage.openPreferenceDialog(VpeEditorPreferencesPage.java:41) at org.jboss.tools.vpe.editor.mozilla.MozillaEditor$1.run(MozillaEditor.java:221) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) 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$6.handleEvent(ActionContributionItem.java:452) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3880) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3473) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) 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:368) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) at org.eclipse.equinox.launcher.Main.run(Main.java:1311) at org.eclipse.equinox.launcher.Main.main(Main.java:1287) -- 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, 4 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-5142) Selection isn't updated when visual editor is invisible

by Yura Zhishko (JIRA)

Selection isn't updated when visual editor is invisible ------------------------------------------------------- Key: JBIDE-5142 URL: https://jira.jboss.org/jira/browse/JBIDE-5142 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.1.0.M4 Reporter: Yura Zhishko Assignee: Yura Zhishko Priority: Minor Fix For: 3.1.0.CR1 Attachments: screenshot-1.jpg 1) Open any page with a visual editor 2) Select some component on the source pane 3) Component is selected on the visual pane (screenshot-1) 4) Minimize Visual Pane 5) Select some another component on the source pane. 6) Restore Visual Pane RESULT: Component from the step 3 is still selected (screenshot-2). -- 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, 4 months

2
5
0 / 0

[JBoss JIRA] Created: (JBIDE-5161) There is no cursor on the visual pane during text editing

by Yura Zhishko (JIRA)

There is no cursor on the visual pane during text editing --------------------------------------------------------- Key: JBIDE-5161 URL: https://jira.jboss.org/jira/browse/JBIDE-5161 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.1.0.M4 Reporter: Yura Zhishko Assignee: Yura Zhishko Priority: Minor 1) Create jsp page 2) Insert next source code: <%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %> <%@ taglib uri="http://java.sun.com/jsf/html" prefix="h" %> <f:loadBundle var="Message" basename="demo.Messages"/> <html> <head> <title>Input User Name Page</title> </head> <body> <f:view> Try to edit this text </f:view> </body> </html> 3) Set cursor inside "Try to edit this text" String on the visual pane RESULT: There is no cursor on the visual pane. -- 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, 4 months

2
5
0 / 0

[JBoss JIRA] Created: (JBIDE-5193) NPE if style value equals ":"

by Yura Zhishko (JIRA)

NPE if style value equals ":" ----------------------------- Key: JBIDE-5193 URL: https://jira.jboss.org/jira/browse/JBIDE-5193 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.1.0.CR1 Reporter: Yura Zhishko Assignee: Maxim Areshkau 1) Open any page 2) Choose any tag that supports style attr 3) Enter for example: <input style=":"/> Result: java.lang.NullPointerException at org.jboss.tools.vpe.editor.toolbar.format.css.StyleAttribute.getProperty(StyleAttribute.java:218) at org.jboss.tools.vpe.editor.toolbar.format.FontNameFormatController.setToolbarItemEnabled(FontNameFormatController.java:89) at org.jboss.tools.vpe.editor.toolbar.format.FormatControllerManager.selectionChanged(FormatControllerManager.java:153) at org.jboss.tools.vpe.editor.toolbar.format.FormatControllerManager.selectionChanged(FormatControllerManager.java:106) at org.jboss.tools.vpe.editor.VpeController.selectionChanged(VpeController.java:2551) at org.eclipse.wst.sse.ui.StructuredTextEditor$5.run(StructuredTextEditor.java:627) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.wst.sse.ui.StructuredTextEditor$StructuredSelectionProvider.fireSelectionChanged(StructuredTextEditor.java:625) at org.eclipse.wst.sse.ui.StructuredTextEditor$StructuredSelectionProvider.handleSelectionChanged(StructuredTextEditor.java:717) at org.eclipse.wst.sse.ui.StructuredTextEditor$3.selectionChanged(StructuredTextEditor.java:593) at org.eclipse.jface.viewers.Viewer$2.run(Viewer.java:162) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.runtime.Platform.run(Platform.java:888) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:48) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) at org.eclipse.jface.viewers.Viewer.fireSelectionChanged(Viewer.java:160) at org.eclipse.jface.text.TextViewer.fireSelectionChanged(TextViewer.java:2714) at org.eclipse.jface.text.TextViewer.selectionChanged(TextViewer.java:2693) at org.eclipse.jface.text.TextViewer.setSelectedRange(TextViewer.java:2382) at org.jboss.tools.vpe.editor.util.SelectionUtil.setSourceSelection(SelectionUtil.java:77) at org.jboss.tools.vpe.selbar.SelectionBar.widgetSelected(SelectionBar.java:527) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3880) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3473) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) 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:368) 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:585) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) at org.eclipse.equinox.launcher.Main.run(Main.java:1311) at org.eclipse.equinox.launcher.Main.main(Main.java:1287) -- 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, 4 months

3
5
0 / 0

[JBoss JIRA] Created: (JBDS-977) Wrong JRE used when starting EAP 5.0 JBoss Server after JBDS installation with JRE v. 1.5

by Vlado Pakan (JIRA)

Wrong JRE used when starting EAP 5.0 JBoss Server after JBDS installation with JRE v. 1.5 ----------------------------------------------------------------------------------------- Key: JBDS-977 URL: https://jira.jboss.org/jira/browse/JBDS-977 Project: JBoss Developer Studio Issue Type: Bug Affects Versions: 2.1.1 Environment: Linux 23/64 bit Sun JDK 1.5 and Sun JDK 1.6 EAP 5.0 bundled with JBDS Reporter: Vlado Pakan When JBDS is installed with JDK v. 1.5. or with default JDK which is v. 1.5 then JBoss AS Server v 5.0 (bundled with JBDS installation) is run with default JRE specified within JBDS and not with JRE specified in Server Runtime Configuration. What means that when JBDS default JRE is v.1.5 user is not able to run JBoss Server v 5.0 because this server needs JRE v. 1.6. Even Server Runtime Configuration is still displaying that JRE v. 1.6 is going to be used. Steps to reproduce: 1. Install JBDS with specified JRE v.1.5 and install also bundled EAP 5.0 2. Run JBDS 3. Add JRE v. 1.6 to JBDS Windows > Preferences > Java > Installed JRE's and set is as default JRE 4. Run defined JBoss EAP Server should run with JRE v 1.6 5. Change JBDS JRE to v. 1.5 and restart JBoss EAP Server It will start with JRE 1.5 and lot of errors Everything works fine when during installation is specified JRE v. 1.6 and JRE v 1.5 is added afterwards. There is also small UI issue related to this one: 1. Install JBDS with specified JRE v.1.5 and install also bundled EAP 5.0 2. Run JBDS 3. Open JBoss EAP Server configuration: double click on JBoss EAP Server within JBoss Server View 4. Open Server Runtime Configuration. In the displayed Dialog will be displayed Error Message such "There is no Java 1.6 Runtime..." 5. Close the Dialog 6. Add JRE v 1.6 to JBDS 7. Open Server Runtime Configuration there will be displayed Error Message "No VM Selected...". See attached file. 8. Reopen this Dialog and now everything works fine If you skip step 4. then everything works fine. There is no Error Message "No VM 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, 4 months

2
5
0 / 0

[JBoss JIRA] Created: (JBIDE-5629) Use SWTBot for eclipse v3.5 in JBT build

by Vlado Pakan (JIRA)

Use SWTBot for eclipse v3.5 in JBT build ---------------------------------------- Key: JBIDE-5629 URL: https://jira.jboss.org/jira/browse/JBIDE-5629 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Build/Releng Affects Versions: 3.1.0.CR1 Reporter: Vlado Pakan JBT build should use newer version of SWTBot for Eclipse v3.5. Use latest version for Eclipse v3.5 downloaded from this location: http://www.eclipse.org/swtbot/downloads.php -- 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, 4 months

2
5
0 / 0

[JBoss JIRA] Created: (JBIDE-5664) Unable to specify additional restriction in when part of Drools rule using Guided Rule Editor

by Vlado Pakan (JIRA)

Unable to specify additional restriction in when part of Drools rule using Guided Rule Editor --------------------------------------------------------------------------------------------- Key: JBIDE-5664 URL: https://jira.jboss.org/jira/browse/JBIDE-5664 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0.CR1 Environment: JBDS 3.0.0 CR1 Linux Sun JDK 1.5 SOA-P 5.0 Reporter: Vlado Pakan It's not possible to add literal value to additional restriction on field in when part of Drools rule using Guided Rule Editor. Only combo box with condition is displayed but there is no fill-in to write the literal value. Steps to reproduce: 1. create new Drools project 2. create new Guided Rule 3. add import com.sample.DroolsTest.Message; to drools.package file 4. add new when condition select DroolsTest$Message within Fact Combo-box in Update constraints dialog 5. add condition on status field of Message: to be greater than 1 6. try to add another condition on status field of Message: and less than 10 7. within Select value editor type dialog choose literal value from Field value combo-box. Afterwards whole WHEN part in Guided Rule Editor is empty. After JBDS window is resized restriction appears in WHEN part of Guided Rule Editor. But it's not possible to specify value for and less than condition When trying to save rule file it's saved without any restriction. See attached pictures. -- 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, 4 months

3
7
0 / 0

[JBoss JIRA] Created: (JBIDE-4998) DND doesn't work for some components under XULRunner 1.9

by Yura Zhishko (JIRA)

DND doesn't work for some components under XULRunner 1.9 -------------------------------------------------------- Key: JBIDE-4998 URL: https://jira.jboss.org/jira/browse/JBIDE-4998 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.1.0.M4 Environment: XULRunner 1.9 Reporter: Yura Zhishko Assignee: Maxim Areshkau In this issue I'll list the components that should support DND, but the don't support it at all. List will be filled in future. 1) h:commandButton -- 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, 4 months

5
8
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 2010