January 2010 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-5418) Provide xulrunner eclipse bundle for OSX cocoa x86_64

by Maxim Areshkau (JIRA)

Provide xulrunner eclipse bundle for OSX cocoa x86_64 ----------------------------------------------------- Key: JBIDE-5418 URL: https://jira.jboss.org/jira/browse/JBIDE-5418 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Visual Page Editor core Reporter: Maxim Areshkau Assignee: Maxim Areshkau Fix For: 3.2.next Visual Page Editor doesn't work with Eclipse 3.5 OSX Cocoa 64 bit To get it worked we need xulrunner bundle for it. -- 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

13 years, 6 months

10
41
0 / 0

[JBoss JIRA] Created: (JBIDE-2183) Ctrl+shift+G binding causing warnings - can it be avoided ?

by Max Rydahl Andersen (JIRA)

Ctrl+shift+G binding causing warnings - can it be avoided ? ----------------------------------------------------------- Key: JBIDE-2183 URL: http://jira.jboss.com/jira/browse/JBIDE-2183 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 2.1.0.CR1 Reporter: Max Rydahl Andersen Fix For: 2.1.0.GA in latest cr1 I get the following in the Error log at startup: eclipse.buildId=1.1.0.CR1 java.version=1.6.0_04 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=da_DK Command-line arguments: -os win32 -ws win32 -arch x86 Warning Tue May 06 15:03:32 CEST 2008 Keybinding conflicts occurred. They may interfere with normal accelerator operation. Warning Tue May 06 15:03:32 CEST 2008 A conflict occurred for CTRL+SHIFT+G: -- 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

13 years, 6 months

6
26
0 / 0

[JBoss JIRA] Created: (JBIDE-1674) Hibernate Properties - like was in Exadel ORM

by Vitali Yemialyanchyk (JIRA)

Hibernate Properties - like was in Exadel ORM --------------------------------------------- Key: JBIDE-1674 URL: http://jira.jboss.com/jira/browse/JBIDE-1674 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Hibernate Reporter: Vitali Yemialyanchyk Assigned To: Vitali Yemialyanchyk Priority: Minor Attachments: screenshot-1.jpg Hibernate Configuration Wizard (screenshot1) has very convinient way to setup properties for hibernate.cfg.xml (screenshot2). -- 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

13 years, 6 months

4
38
0 / 0

[JBoss JIRA] Created: (JBIDE-3225) Components should render usual text inside

by Yura Zhishko (JIRA)

Components should render usual text inside ------------------------------------------ Key: JBIDE-3225 URL: https://jira.jboss.org/jira/browse/JBIDE-3225 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor Templates Affects Versions: 3.0.0.cr1 Reporter: Yura Zhishko Assignee: Maxim Areshkau Priority: Minor 1) DND or create any component from the list below 2) Print usual text inside component ASSERT: Text should be rendered in VPE RESULT: Text isn't rendered Here is list of components with the same behavior: <rich:inplaceInput> <rich:inplaceSelect> <rich:inputNumberSlider> <rich:inputNumberSpinner> <rich:paint2D> <rich:spacer> <a4j:actionparam> <a4j:commandButton> <a4j:push> <a4j:log> <h:commandButton> <h:inputHidden> <h:inputText> <h:inputTextarea> <h:messages> <h:selectBooleanCheckbox> -- 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

13 years, 6 months

6
22
0 / 0

[JBoss JIRA] Created: (JBIDE-4857) Mapping Diagram viewer should display all db tables which is visible for Hibernate Console conf tree

by Vitali Yemialyanchyk (JIRA)

Mapping Diagram viewer should display all db tables which is visible for Hibernate Console conf tree ---------------------------------------------------------------------------------------------------- Key: JBIDE-4857 URL: https://jira.jboss.org/jira/browse/JBIDE-4857 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Hibernate Affects Versions: 3.1.0.M4 Reporter: Vitali Yemialyanchyk Assignee: Vitali Yemialyanchyk Priority: Minor Fix For: 3.1.0.M4 there is a sence to display all available tables and relations between tables, even if there is no mapping class for some particular table. -- 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

13 years, 6 months

4
9
0 / 0

[JBoss JIRA] Created: (JBIDE-5768) ui:include and f:facet header/footer don't render

by Menashe (JIRA)

ui:include and f:facet header/footer don't render ------------------------------------------------- Key: JBIDE-5768 URL: https://jira.jboss.org/jira/browse/JBIDE-5768 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0.CR1 Reporter: Menashe i have this code inside <rich:dataTable> <ui:include src="paginator.xhtml"/> when paginator.xhtml <f:facet name="footer"> <s:span>TEXT</s:span> </f:facet> the TEXT is not rendered in the Visual/Source and Preview panels. however when <f:facet> tag is removed it renders fine. Same is true with <f:facet name="header"> -- 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

13 years, 6 months

5
21
0 / 0

[JBoss JIRA] Created: (JBIDE-4523) Visual Page Editor doesn't work with Eclipse 3.5 OSX Cocoa

by Cesar Perez (JIRA)

Visual Page Editor doesn't work with Eclipse 3.5 OSX Cocoa ---------------------------------------------------------- Key: JBIDE-4523 URL: https://jira.jboss.org/jira/browse/JBIDE-4523 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.1.0.M1 Environment: Mac OSX 10.5.7, Eclipse 3.5 JEE Cocoa, JBoss Tools 3.1.0.M1 Reporter: Cesar Perez The Visual Page Editor does not work under the final version of Eclipse 3.5 JEE Cocoa for Mac OSX and JBoss Tools 3.1.0.M1, the error is due to a missing cocoa version of XUL runner as you can see in the following stacktrace: org.jboss.tools.vpe.xulrunner.XulRunnerException: Bundle org.mozilla.xulrunner.cocoa.macosx is not found. at org.jboss.tools.vpe.xulrunner.browser.XulRunnerBrowser.getXulRunnerPath(XulRunnerBrowser.java:219) at org.jboss.tools.vpe.xulrunner.browser.XulRunnerBrowser.initXulRunner(XulRunnerBrowser.java:114) at org.jboss.tools.vpe.xulrunner.browser.XulRunnerBrowser.<init>(XulRunnerBrowser.java:85) at org.jboss.tools.vpe.xulrunner.editor.XulRunnerEditor.<init>(XulRunnerEditor.java:135) at org.jboss.tools.vpe.editor.mozilla.MozillaPreview$1.<init>(MozillaPreview.java:59) at org.jboss.tools.vpe.editor.mozilla.MozillaPreview.createPartControl(MozillaPreview.java:59) at org.jboss.tools.vpe.editor.VpeEditorPart.createPreviewBrowser(VpeEditorPart.java:921) at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditor.pageChange(JSPMultiPageEditor.java:248) at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditorPart$2.widgetSelected(JSPMultiPageEditorPart.java:106) 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.Display.sendEvent(Display.java:3542) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1247) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1270) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1255) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1076) at org.eclipse.swt.custom.CTabFolder.setSelection(CTabFolder.java:3256) at org.eclipse.swt.custom.CTabFolder.onMouse(CTabFolder.java:2045) at org.eclipse.swt.custom.CTabFolder$1.handleEvent(CTabFolder.java:323) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:3542) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1247) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1270) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1255) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1076) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3440) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3099) 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) -- 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

13 years, 7 months

10
34
0 / 0

[JBoss JIRA] Created: (JBIDE-3708) Add possibilities of components' rendering inside body of some ajax tags.

by Yura Zhishko (JIRA)

Add possibilities of components' rendering inside body of some ajax tags. ------------------------------------------------------------------------- Key: JBIDE-3708 URL: https://jira.jboss.org/jira/browse/JBIDE-3708 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Visual Page Editor Templates Affects Versions: 3.0.0.CR2 Reporter: Yura Zhishko Assignee: Maxim Areshkau 1) Import attached project into workspace 2) Run it on server ASSERT: Some of these components do not have visual representation, but body content is rendered OK. On pages you will find comments with a real behavior of components (in all components, not marked as "Here is OK", components of a body are rendered at first by turn and then component is rendered itself and appears if it has visual representation). Also pay attention to components marked as jira's issues. P. S. This is not a full list of components, others components will be tested soon. -- 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

13 years, 7 months

5
22
0 / 0

[JBoss JIRA] Created: (JBIDE-3511) Text body of h:outputText and h:outputFormat is rendered in incorrect sequence

by Yahor Radtsevich (JIRA)

Text body of h:outputText and h:outputFormat is rendered in incorrect sequence ------------------------------------------------------------------------------ Key: JBIDE-3511 URL: https://jira.jboss.org/jira/browse/JBIDE-3511 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: Visual Page Editor Templates Affects Versions: 3.0.0.cr1 Reporter: Yahor Radtsevich Assignee: Maxim Areshkau Fix For: 3.0.1.GA Download 'testT1_noVerbatim.zip' from JBIDE-3382 file attachment list and import it into your Eclipse workspace. Open file /richT1/WebContent/pages/emptyTest/emptyTags2.jsp in VPE. Actual Result: VPE renders attribute 'value' of the tags BEFORE their body. Expected Result: VPE renders attribute 'value' of the tags AFTER their body, as in browser. See screenshot [1]. -- 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

13 years, 7 months

3
16
0 / 0

[JBoss JIRA] Created: (JBIDE-5663) improved WYSIWYG editor experience

by Igor Jacy Lino Campista (JIRA)

improved WYSIWYG editor experience ------------------------------------ Key: JBIDE-5663 URL: https://jira.jboss.org/jira/browse/JBIDE-5663 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JSF, jsp/jsf/xml source editing, Visual Page Editor core, Visual Page Editor Templates, XML Structured Editor Reporter: Igor Jacy Lino Campista I normally use the jboss tools 3 and it could be really really useful and productive if the visual editor would be more intelligent and user friendly when working on top of it. With that I mean not only resize some visible components or change a few properties but really the consistency how one has a workflow working mostly visually for all JSF components (i.e. Richfaces). For example creating a table from scratch is actually not that a simple task. and At some point you cannot even drag and drop a column since the editor won't allowing (showing the red icon). The Netbeans JSP editor when drag-n-droping a table, it will show a dummy nice-looking table with 3 sample columns ready to modify them. Adding extra columns visually in the netbeans editor also fits quite well, etc. I recently came across a nice DITA WYSIWYG editor (Serna) in the technical documentation domain (You may editor docbook or DITA content totally visual). see http://www.syntext.com/products/serna-free/ and also http://www.syntext.com/images/screenshots/serna-free-on-vista.png In the Serna editor, the easiness of adding new elements working on the visual part is really amazing. It shows quite well where you are (for example you know when you are before, within or after an element) and adding extra elements feels also quite good (ctrl-enter gives you a dialog of elements you can add based on where you are. INSIDE THE VISUAL PART of the editor). Totally a charm to use. -- 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

13 years, 7 months

4
11
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 January 2010