December 2007 - jbosstools-issues

[JBoss JIRA] Updated: (JBIDE-1226) Various bugs in visual previews of richfaces components

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-1226?page=all ] Max Andersen updated JBIDE-1226: -------------------------------- Fix Version/s: (was: 2.0.1) nothing critical enough for 2.0.1 > Various bugs in visual previews of richfaces components > ------------------------------------------------------- > > Key: JBIDE-1226 > URL: http://jira.jboss.com/jira/browse/JBIDE-1226 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Visual Page Editor > Reporter: Gavin King > Assigned To: Sergey Vasilyev > Fix For: 2.1 > > Attachments: calendar.png, calendar_ve.png, dataDefinitionList.png, dataDefinitionList_ve.png, dataTable.png, dataTable_ve.png, dropDownMenu.png, dropDownMenu_ve.png, inputNumberSlider.png, inputNumberSlider_ve.png, modalPanel.png, modalPanel_ve.png, panelBar.png, panelBar_ve.png, panelMenu.png, panelMenu_ve.png, status.png, status_ve.png, toolTip.png, toolTip_ve.png, tree.png, tree_ve.png > > > Here's a list of previews that need fixing: > rich:calendar won't popup, and puts the button in the wrong place > rich:dataDefinitionList broken > rich:dropDownMenu nonfunctional > rich:panelMenu nonfunctional > rich:panelBar functional, but rendering is broken > rich:toolTip nonfunctional > rich:modalPanel nonfunctional > rich:dataTable broken > rich:tree sorta works, but the nodes are not functional and don't render as links > rich:inputNumberSlider and other sliders are ugly > a4j:status should show some kind of preview -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBIDE-779) JSF 1.2 with Facelets KickStart error

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-779?page=all ] Max Andersen updated JBIDE-779: ------------------------------- Fix Version/s: LATER (was: 2.0.1) not sure what we can do to make this better... > JSF 1.2 with Facelets KickStart error > ------------------------------------- > > Key: JBIDE-779 > URL: http://jira.jboss.com/jira/browse/JBIDE-779 > Project: Tools (JBoss Tools) > Issue Type: Bug > Affects Versions: 2.0.0.Beta3 > Environment: WindowsXP SP2 > rhds-win32-1.0.0.ALPHA.jar > Red Hat Developer Studio > Version: 1.0.0 > Build id: 1.0.0 > Reporter: Aliaksey Nis > Assigned To: Alexey Kazakov > Fix For: LATER > > Attachments: WarningsScreen.JPG > > > 1. Web projects View -> New JSF Project > 2. Enter as JSF Environment JSF 1.2 with Facelets, as template - FaceletsKickStart, Press Finish > 3. Open inputname.jsp > 5 warnings appear at lines: > 17(jsfc="h:form"), 19(jsfc="h:inputText"), 19(required="true"), 20(jsfc="h:commandButton"), 21(action="greeting"). > So KickStart project can't be runned at server. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (RHDS-231) RHDS crashes when editing in XHTML (facelet) file

by Wolfgang Chico Toepfer (JIRA)

RHDS crashes when editing in XHTML (facelet) file ------------------------------------------------- Key: RHDS-231 URL: http://jira.jboss.com/jira/browse/RHDS-231 Project: Red Hat Developer Studio Issue Type: Bug Components: jsf Affects Versions: 1.0.0.beta2 Environment: RHDS Beta 2, Facelets 1.1.12, Trinidad 1.2.3, RichFaces 3.1.1GA Reporter: Wolfgang Chico Toepfer Priority: Critical While editing in an XHTML (facelet) file the system reaches a NullPointerException, then the whole IDE stall and it remains for you to quite task-manager-wise.. Here is the latest log (the whole thing is repeatable as you like, but I uninstalled RHDS Beta 2 and reverted to Beta 1, now everything's fine ;): !ENTRY org.jboss.tools.vpe 4 0 2007-10-15 08:15:45.671 !MESSAGE !STACK 0 java.lang.NullPointerException at org.jboss.tools.jst.jsp.editor.TLDRegisterHelper.registerTld(TLDRegisterHelper.java:54) at org.jboss.tools.jst.jsp.editor.TLDRegisterHelper.registerTld(TLDRegisterHelper.java:38) at org.jboss.tools.vpe.editor.context.VpePageContext.registerTaglibs(VpePageContext.java:415) at org.jboss.tools.vpe.editor.context.VpePageContext.rebuildTaglibMap(VpePageContext.java:179) at org.jboss.tools.vpe.editor.context.VpePageContext.setTaglib(VpePageContext.java:154) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addTaglib(VpeVisualDomBuilder.java:1716) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createXmlns(VpeVisualDomBuilder.java:1679) at org.jboss.tools.vpe.editor.VpePreviewDomBuilder.createNode(VpePreviewDomBuilder.java:71) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:229) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:457) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.buildDom(VpeVisualDomBuilder.java:198) at org.jboss.tools.vpe.editor.mozilla.MozillaPreview.buildDom(MozillaPreview.java:464) at org.jboss.tools.vpe.editor.VpeEditorPart$6.load(VpeEditorPart.java:512) at org.jboss.tools.vpe.editor.mozilla.MozillaPreview.onLoadWindow(MozillaPreview.java:357) at org.jboss.tools.vpe.editor.mozilla.MozillaPreview.access$0(MozillaPreview.java:352) at org.jboss.tools.vpe.editor.mozilla.MozillaPreview$1.onLoadWindow(MozillaPreview.java:132) at org.jboss.tools.vpe.mozilla.browser.MozillaBrowser.OnStateChange(MozillaBrowser.java:1812) at org.jboss.tools.vpe.mozilla.browser.MozillaBrowser$4.method3(MozillaBrowser.java:777) at org.jboss.tools.vpe.mozilla.internal.swt.xpl.XPCOMObject.callback3(XPCOMObject.java:263) at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method) at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2265) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3291) at org.eclipse.ui.application.WorkbenchAdvisor.openWindows(WorkbenchAdvisor.java:801) at org.eclipse.ui.internal.Workbench$25.runWithException(Workbench.java:1342) at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3659) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3296) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2309) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219) at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:169) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176) 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:508) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447) at org.eclipse.equinox.launcher.Main.run(Main.java:1173) What is also worthnoting: 1) the Content assist does not work amymore with the Trinidad lib (tr and trh) 2) so I added the TLDs of Trinidad to the JBOSS Tools pane by drag and drop to that pane, which worked -- 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, 11 months

5
8
0 / 0

[JBoss JIRA] Updated: (JBDS-178) DocBook Investigation

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBDS-178?page=all ] Max Andersen updated JBDS-178: ------------------------------ Affects Version/s: 1.0.0.GA > DocBook Investigation > ---------------------- > > Key: JBDS-178 > URL: http://jira.jboss.com/jira/browse/JBDS-178 > Project: Developer Studio > Issue Type: Task > Components: documentation > Affects Versions: 1.0.0.GA > Reporter: Svetlana mukhina > Assigned To: Anatoly Fedosik > > Learn more about DocBook, the tags that we use in our xml, the attributes of the main tags, etc. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBDS-153) Red Hat Developer Studio Feature List chapter

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBDS-153?page=all ] Max Andersen updated JBDS-153: ------------------------------ Affects Version/s: 1.0.0.GA > Red Hat Developer Studio Feature List chapter > --------------------------------------------- > > Key: JBDS-153 > URL: http://jira.jboss.com/jira/browse/JBDS-153 > Project: Developer Studio > Issue Type: Task > Components: documentation > Affects Versions: 1.0.0.GA > Reporter: Svetlana mukhina > Assigned To: Svetlana mukhina > Original Estimate: 1 day, 4 hours > Remaining Estimate: 1 day, 4 hours > > This chapter should be rewritten according with change in RHDS -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBDS-149) New RHDS build instalation

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBDS-149?page=all ] Max Andersen updated JBDS-149: ------------------------------ Affects Version/s: 1.0.0.GA > New RHDS build instalation > -------------------------- > > Key: JBDS-149 > URL: http://jira.jboss.com/jira/browse/JBDS-149 > Project: Developer Studio > Issue Type: Task > Components: documentation > Affects Versions: 1.0.0.GA > Reporter: Svetlana mukhina > Assigned To: Anatoly Fedosik > > Install new RHDS builds, report the problems to jira if there are some -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBDS-181) RHNetwork delivery/updates

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBDS-181?page=all ] Max Andersen resolved JBDS-181. ------------------------------- Fix Version/s: 1.0.0.GA Resolution: Done manual download possible for GA. > RHNetwork delivery/updates > -------------------------- > > Key: JBDS-181 > URL: http://jira.jboss.com/jira/browse/JBDS-181 > Project: Developer Studio > Issue Type: Task > Reporter: Max Andersen > Fix For: 1.0.0.GA > > -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBDS-16) RHDS Uninstaller doesn't remove RHDS/Uninstaller folder

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBDS-16?page=all ] Max Andersen updated JBDS-16: ----------------------------- Component/s: installer Affects Version/s: 1.0.0.GA > RHDS Uninstaller doesn't remove RHDS/Uninstaller folder > ------------------------------------------------------- > > Key: JBDS-16 > URL: http://jira.jboss.com/jira/browse/JBDS-16 > Project: Developer Studio > Issue Type: Bug > Components: installer > Affects Versions: 1.0.0.GA > Environment: WindowsXP SP2 > rhds-win32-1.0.0.ALPHA.jar > Red Hat Developer Studio > Version: 1.0.0 > Build id: 1.0.0 > Reporter: Aliaksey Nis > Assigned To: Vladimir Ralev > Priority: Trivial > > RHDS was installed at <RHDS> folder > When u uninstall RHDS, empty folder RHDS/Uninstaller remain undeleted. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBDS-17) Next button should be disabled If the installation folder was not selected .

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBDS-17?page=all ] Max Andersen updated JBDS-17: ----------------------------- Component/s: installer Affects Version/s: 1.0.0.GA > Next button should be disabled If the installation folder was not selected . > ----------------------------------------------------------------------------- > > Key: JBDS-17 > URL: http://jira.jboss.com/jira/browse/JBDS-17 > Project: Developer Studio > Issue Type: Bug > Components: installer > Affects Versions: 1.0.0.GA > Reporter: Anton Klimkovich > Assigned To: Vladimir Ralev > Priority: Optional > > Run installation of RHDS > Go to step 3 > Clean field with installation path > Next button should be enabled. > If clean field with installation path and press Next the warning message will appear. ("You have not specified a target location. Is this correct ? "). If you press OK button The path to Folder where Installation was run will be inserted to installation path field. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBDS-92) Save the installation path for RHDS after Previous button was pressed.

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBDS-92?page=all ] Max Andersen updated JBDS-92: ----------------------------- Component/s: installer Affects Version/s: 1.0.0.GA > Save the installation path for RHDS after Previous button was pressed. > ----------------------------------------------------------------------- > > Key: JBDS-92 > URL: http://jira.jboss.com/jira/browse/JBDS-92 > Project: Developer Studio > Issue Type: Feature Request > Components: installer > Affects Versions: 1.0.0.GA > Reporter: Anton Klimkovich > Assigned To: Vladimir Ralev > Priority: Optional > > Run installation af RHDS > Go to step 3 > Select the installation path (C:\Red Hat Developer Studio - for example) > Press Previous button (step 2 will be) > Press Next button (again step 3) > The installation path will be default again (C:\Program Files\Red Hat Developer Studio) instead of selected path before pressing Previous button. -- 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, 11 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues December 2007