[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
12 years, 1 month
[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
12 years, 1 month
[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
12 years, 1 month
[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
12 years, 1 month
[JBoss JIRA] Created: (JBIDE-3513) Text bodies of tags h:select... are not rendered by VPE
by Yahor Radtsevich (JIRA)
Text bodies of tags h:select... are not rendered by VPE
-------------------------------------------------------
Key: JBIDE-3513
URL: https://jira.jboss.org/jira/browse/JBIDE-3513
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
Attachments: 17_19-22_h_selectX_inner_text.gif
1. Download 'testT1_noVerbatim.zip' from JBIDE-3382 file attachment list and import it into your Eclipse workspace.
2. Open file /richT1/WebContent/pages/emptyTest/emptyTags2.jsp in VPE.
3. Look at items 17,19,20,21,22
Actual Result: VPE DOES NOT render text bodies of the tags h:select... .
Expected Result: VPE DOES render the bodies of the tags. 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
12 years, 1 month