September 2008 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-2684) Component <rich:insert> doesn't work in VPE. Exception appears.

by Dzmitry Sakovich (JIRA)

Component <rich:insert> doesn't work in VPE. Exception appears. --------------------------------------------------------------- Key: JBIDE-2684 URL: https://jira.jboss.org/jira/browse/JBIDE-2684 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.0.0.alpha Reporter: Dzmitry Sakovich Assignee: Dzmitry Sakovich EXECUTE: Import richfaces-demo-3.1.3.GA.war in workspace EXECUTE: Open /WebContent/richfaces/dataTable.xhtml EXCEPTION Appears: java.lang.NullPointerException at org.jboss.tools.jsf.vpe.richfaces.template.RichFacesInsertTemplate.create(RichFacesInsertTemplate.java:112) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:436) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:255) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:601) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:517) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:255) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:576) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:513) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:255) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:576) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:513) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:255) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:601) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:517) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:255) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:601) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:517) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:255) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:576) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:513) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:255) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:601) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:517) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:255) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:576) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:513) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:255) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:576) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:513) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:255) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:576) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:513) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:255) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:576) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:513) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:255) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:576) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:513) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:255) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:576) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:513) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:255) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:601) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:517) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:255) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:576) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:513) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:255) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:576) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.buildDom(VpeVisualDomBuilder.java:217) at org.jboss.tools.vpe.editor.VpeController.init(VpeController.java:284) at org.jboss.tools.vpe.editor.VpeEditorPart$16.load(VpeEditorPart.java:748) at org.jboss.tools.vpe.editor.mozilla.MozillaEditor.onLoadWindow(MozillaEditor.java:510) at org.jboss.tools.vpe.editor.mozilla.MozillaEditor.access$2(MozillaEditor.java:505) at org.jboss.tools.vpe.editor.mozilla.MozillaEditor$4.onLoadWindow(MozillaEditor.java:240) at org.jboss.tools.vpe.xulrunner.browser.XulRunnerBrowser.onStateChange(XulRunnerBrowser.java:403) at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method) at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:1541) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3031) at org.jboss.tools.vpe.editor.mozilla.MozillaEditor.createPartControl(MozillaEditor.java:288) at org.jboss.tools.vpe.editor.VpeEditorPart.createVisualEditor(VpeEditorPart.java:754) at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditor.pageChange(JSPMultiPageEditor.java:223) at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditor.createPages(JSPMultiPageEditor.java:421) at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditorPart.createPartControl(JSPMultiPageEditorPart.java:125) at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:661) at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:428) at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:594) at org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:266) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2820) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2729) at org.eclipse.ui.internal.WorkbenchPage.access$11(WorkbenchPage.java:2721) at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2673) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2668) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2652) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2643) at org.eclipse.ui.ide.IDE.openEditor(IDE.java:646) at org.eclipse.ui.ide.IDE.openEditor(IDE.java:605) at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:318) at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:160) at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:228) at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:207) at org.eclipse.jdt.ui.actions.SelectionDispatchAction.dispatchRun(SelectionDispatchAction.java:274) at org.eclipse.jdt.ui.actions.SelectionDispatchAction.run(SelectionDispatchAction.java:250) at org.eclipse.jdt.internal.ui.packageview.PackageExplorerActionGroup.handleOpen(PackageExplorerActionGroup.java:363) at org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart$5.open(PackageExplorerPart.java:603) at org.eclipse.jface.viewers.StructuredViewer$2.run(StructuredViewer.java:820) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.runtime.Platform.run(Platform.java:880) 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.StructuredViewer.fireOpen(StructuredViewer.java:818) at org.eclipse.jface.viewers.StructuredViewer.handleOpen(StructuredViewer.java:1079) at org.eclipse.jface.viewers.StructuredViewer$6.handleOpen(StructuredViewer.java:1183) at org.eclipse.jface.util.OpenStrategy.fireOpenEvent(OpenStrategy.java:263) at org.eclipse.jface.util.OpenStrategy.access$2(OpenStrategy.java:257) at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:297) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1158) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3401) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3033) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488) 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:193) 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:382) 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:549) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504) at org.eclipse.equinox.launcher.Main.run(Main.java:1236) at org.eclipse.equinox.launcher.Main.main(Main.java:1212) -- 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

17 years, 7 months

2
3
0 / 0

[JBoss JIRA] Commented: (JBIDE-2636) version number for jbossws runtimes are free-form, should be more controlled

by Denny Xu (JIRA)

[ https://jira.jboss.org/jira/browse/JBIDE-2636?page=com.atlassian.jira.plu... ] Denny Xu commented on JBIDE-2636: --------------------------------- we can change the text field to a combo, and all available jbossws runtime versions come from the defined jbossws facet versions(every jbossws facet version maps a type of jbossws runtime) > version number for jbossws runtimes are free-form, should be more controlled > ---------------------------------------------------------------------------- > > Key: JBIDE-2636 > URL: https://jira.jboss.org/jira/browse/JBIDE-2636 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Webservices > Affects Versions: 3.0.0.alpha > Reporter: Max Rydahl Andersen > Assignee: Feng Qian > Fix For: 3.0.0.beta1 > > > I see that I can write anything in the version field of the runtime for jbossws runtimes. > Aren't these supposed to be more specific ones (e.g. a list of supported values) so you can control the behavior of how you do different things depedent on the version / type of jbossws 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

17 years, 7 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBIDE-2632) Facet wizard has inconsistent disabled/enabled server setup on first startup and weird deploy checkbox.

by Denny Xu (JIRA)

[ https://jira.jboss.org/jira/browse/JBIDE-2632?page=com.atlassian.jira.plu... ] Denny Xu commented on JBIDE-2632: --------------------------------- I reproduce the inconsistent issue , will fix it soon. the "deploy" checkbox is checked, all jars of the selected jbossws runtime will also be packaged into the project package while deploying. Put it on a new line is good idea. > Facet wizard has inconsistent disabled/enabled server setup on first startup and weird deploy checkbox. > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-2632 > URL: https://jira.jboss.org/jira/browse/JBIDE-2632 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Webservices > Affects Versions: 3.0.0.alpha > Reporter: Max Rydahl Andersen > Assignee: Feng Qian > Fix For: 3.0.0.beta1 > > > Start on clean workspace, create dynamic web project. > Right click on project and enable JBossWS facet and click on the link for further configuraiton. > On first start the server line is disabled unless you click the checkbox...close the dialog and click further configuraiton - this time the line is enabled even though the checkbox is not checked. > And what is the "deploy" c heckbox for ? Could we put that on a seperate line and with a more informative text? -- 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

17 years, 7 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBIDE-2634) Facet asks for webservice runtime on install but there is no way to edit/change that afterwards

by Denny Xu (JIRA)

[ https://jira.jboss.org/jira/browse/JBIDE-2634?page=com.atlassian.jira.plu... ] Denny Xu commented on JBIDE-2634: --------------------------------- for now, since all operations about the runtime installation are performed in jbossws facet installation, so if you want change target jbossws runtime, you should uninstall the jbossws facet and then reinstall it, when reinstall it, you can change it in jbossws facet installing page, it's really a little complicated. > Facet asks for webservice runtime on install but there is no way to edit/change that afterwards > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-2634 > URL: https://jira.jboss.org/jira/browse/JBIDE-2634 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Webservices > Affects Versions: 3.0.0.alpha > Reporter: Max Rydahl Andersen > Assignee: Feng Qian > Fix For: 3.0.0.beta1 > > > Maybe I just dont know the webservice ui well, but I could not find a way to change the targeted runtime for the project. -- 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

17 years, 7 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBIDE-719) Hibernate Tools should be able to use a named Eclipse provided connection

by Max Rydahl Andersen (JIRA)

[ https://jira.jboss.org/jira/browse/JBIDE-719?page=com.atlassian.jira.plug... ] Max Rydahl Andersen commented on JBIDE-719: ------------------------------------------- When no connection profile is selected the following get stored <stringAttribute key="org.hibernate.eclipse.launch.CONNECT_PROFILE_NAME" value="<Hibernate settings>"/> That makes no sense - there should not be any profile name in this case. > Hibernate Tools should be able to use a named Eclipse provided connection > ------------------------------------------------------------------------- > > Key: JBIDE-719 > URL: https://jira.jboss.org/jira/browse/JBIDE-719 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Hibernate > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Priority: Critical > Fix For: 3.0.0.beta1 > > Attachments: Edit Configuration 3.jpg, Create Hibernate Console Configuration.jpg, Edit Configuration 1.jpg, Edit Configuration 2.jpg, JBIDE-719_20080902.zip > > Original Estimate: 4 days > Remaining Estimate: 4 days > > currently we use the settings specified in hibernate.properties/cfg.xml/persistence.xml > Users should be able to say to use a named WTP provided database connection. -- 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

17 years, 7 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBIDE-719) Hibernate Tools should be able to use a named Eclipse provided connection

by Max Rydahl Andersen (JIRA)

[ https://jira.jboss.org/jira/browse/JBIDE-719?page=com.atlassian.jira.plug... ] Max Rydahl Andersen commented on JBIDE-719: ------------------------------------------- There also seem to be no error handling the case of the connection profile not being available anymore. > Hibernate Tools should be able to use a named Eclipse provided connection > ------------------------------------------------------------------------- > > Key: JBIDE-719 > URL: https://jira.jboss.org/jira/browse/JBIDE-719 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Hibernate > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Priority: Critical > Fix For: 3.0.0.beta1 > > Attachments: Edit Configuration 3.jpg, Create Hibernate Console Configuration.jpg, Edit Configuration 1.jpg, Edit Configuration 2.jpg, JBIDE-719_20080902.zip > > Original Estimate: 4 days > Remaining Estimate: 4 days > > currently we use the settings specified in hibernate.properties/cfg.xml/persistence.xml > Users should be able to say to use a named WTP provided database connection. -- 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

17 years, 7 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBIDE-719) Hibernate Tools should be able to use a named Eclipse provided connection

by Max Rydahl Andersen (JIRA)

[ https://jira.jboss.org/jira/browse/JBIDE-719?page=com.atlassian.jira.plug... ] Max Rydahl Andersen commented on JBIDE-719: ------------------------------------------- The 'Use JPA Project" option is implemented incorrectly. It just copies the current JPA connection profile instead of picking up the current JPA projects connection on initialization. Resulting in it not being in sync with the jpa project plus the "Use JPA Project" setting will not be selected when a user opens the config again so the ui is inconsistent. I'll remove that part so we at least get DTP connection support. > Hibernate Tools should be able to use a named Eclipse provided connection > ------------------------------------------------------------------------- > > Key: JBIDE-719 > URL: https://jira.jboss.org/jira/browse/JBIDE-719 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Hibernate > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Priority: Critical > Fix For: 3.0.0.beta1 > > Attachments: Edit Configuration 3.jpg, Create Hibernate Console Configuration.jpg, Edit Configuration 1.jpg, Edit Configuration 2.jpg, JBIDE-719_20080902.zip > > Original Estimate: 4 days > Remaining Estimate: 4 days > > currently we use the settings specified in hibernate.properties/cfg.xml/persistence.xml > Users should be able to say to use a named WTP provided database connection. -- 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

17 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-1080) Field Destination is not editable by hand in Project archives-> New WAR Wizard.

by Anton Klimkovich (JIRA)

Field Destination is not editable by hand in Project archives-> New WAR Wizard. ------------------------------------------------------------------------------- Key: JBIDE-1080 URL: http://jira.jboss.com/jira/browse/JBIDE-1080 Project: JBoss Tools Issue Type: Bug Affects Versions: 2.0.0.Beta4 Reporter: Anton Klimkovich Priority: Minor Attachments: not editable.PNG Create any project Open Project archives View Move project to war In New WAR Wizard field Field Destination is not editable by hand. Look at Screenshot. -- 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

17 years, 7 months

5
16
0 / 0

[JBoss JIRA] Created: (JBIDE-1271) Visual Editor should use resource bundles for preview

by Gavin King (JIRA)

Visual Editor should use resource bundles for preview ----------------------------------------------------- Key: JBIDE-1271 URL: http://jira.jboss.com/jira/browse/JBIDE-1271 Project: JBoss Tools Issue Type: Feature Request Reporter: Gavin King It would be a really *great* feature for the VE to automatically fill out any EL expressions which refer to resource bundles strings in the visual preview. It would assume the default locale defined in faces-config (or "en" otherwise). It would pull resources integrated via faces-config, f:loadBundle, or Seam "messages" component. -- 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

17 years, 7 months

10
12
0 / 0

[JBoss JIRA] Created: (JBIDE-1892) Error appears when user deletes selected source in source editor.

by Andrei Scherbovich (JIRA)

Error appears when user deletes selected source in source editor. ----------------------------------------------------------------- Key: JBIDE-1892 URL: http://jira.jboss.com/jira/browse/JBIDE-1892 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor Affects Versions: 2.1 Environment: subversion revision 6882. Reporter: Andrei Scherbovich Assigned To: Maxim Areshkau Error appears when user deletes selected source in source editor. See error log in attachment. Steps: 1. EXECUTE: Create JSF KickStart application 2. EXECUTE: Open any file (jsp, xhtml) and press ctrl+A 3. EXECUTE: Press DELETE button 4. FAILURE: error appears -- 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

17 years, 7 months

5
6
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 2008