[JBoss JIRA] Created: (JBIDE-3397) Empty visual part for External page which uses rich:calculator
by Yura Zhishko (JIRA)
Empty visual part for External page which uses rich:calculator
--------------------------------------------------------------
Key: JBIDE-3397
URL: https://jira.jboss.org/jira/browse/JBIDE-3397
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor Templates
Affects Versions: 3.0.0.GA
Reporter: Yura Zhishko
Assignee: Sergey Dzmitrovich
Attachments: calendarError.jsp
1) Close all pages
2) DND attached page into workspace
Next exception appears:
java.lang.NullPointerException
at org.jboss.tools.jsf.vpe.richfaces.ComponentUtil.getAbsoluteWorkspacePath(ComponentUtil.java:277)
at org.jboss.tools.jsf.vpe.richfaces.template.RichFacesCalendarTemplate.readAttributes(RichFacesCalendarTemplate.java:653)
at org.jboss.tools.jsf.vpe.richfaces.template.RichFacesCalendarTemplate.create(RichFacesCalendarTemplate.java:242)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:465)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:260)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:655)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:559)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:260)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:628)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:555)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:260)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:628)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:555)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:260)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:628)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.buildDom(VpeVisualDomBuilder.java:222)
at org.jboss.tools.vpe.editor.VpeController.init(VpeController.java:312)
at org.jboss.tools.vpe.editor.VpeEditorPart$16.load(VpeEditorPart.java:767)
at org.jboss.tools.vpe.editor.mozilla.MozillaEditor.onLoadWindow(MozillaEditor.java:553)
at org.jboss.tools.vpe.editor.mozilla.MozillaEditor.access$2(MozillaEditor.java:548)
at org.jboss.tools.vpe.editor.mozilla.MozillaEditor$5.onLoadWindow(MozillaEditor.java:292)
at org.jboss.tools.vpe.xulrunner.browser.XulRunnerBrowser.onStateChange(XulRunnerBrowser.java:407)
at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2371)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3420)
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:386)
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: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
16 years
[JBoss JIRA] Created: (JBIDE-1280) JBoss Tools JSP Editor does not process some problems in vpe templates in a user friendly way
by Viacheslav Kabanovich (JIRA)
JBoss Tools JSP Editor does not process some problems in vpe templates in a user friendly way
---------------------------------------------------------------------------------------------
Key: JBIDE-1280
URL: http://jira.jboss.com/jira/browse/JBIDE-1280
Project: JBoss Tools
Issue Type: Bug
Components: Visual Page Editor
Affects Versions: 2.0.0.Beta4
Reporter: Viacheslav Kabanovich
1. provide an incorrect vpe expression in some vpe template.
(I used <span title="{tagstring()|tagstring()}" /> instead of <span title="{tagstring()}" />
for standard jsf tag templates in vpe-templates-jsf.xml).
2. prepare jsp file that uses the corrupted template.
3. open jsp file with JBoss Tools JSP Editor.
Result: blank visual editor and empty Eclipse log.
4. Select Preview tab
Result: tab is empty and log contains Error
org.jboss.tools.vpe.editor.template.expression.VpeExpressionError: Error of type conversion
at org.jboss.tools.vpe.editor.template.expression.VpeValue.or(VpeValue.java:94)
at org.jboss.tools.vpe.editor.template.expression.VpeOrOperation.exec(VpeOrOperation.java:26)
at org.jboss.tools.vpe.editor.template.VpeAttributeCreator.create(VpeAttributeCreator.java:54)
The Error is caught by Workbench.
The question is: why most problems in vpe expressions throw VpeExpressionBuilderException
and some problems throw VpeExpressionError (which extends java.lang.Error)?
Comment to java.lang.Error says that
"An Error is a subclass of Throwable that indicates serious problems
that a reasonable application should not try to catch"
As shown above, in cases when Studio does not catch VpeExpressionError, user has no idea what is wrong,
and in cases when Eclipse catches it, it would be more proper to use something like
VpeExpressionExecException extending Exception rather than Error.
--
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
16 years
[JBoss JIRA] Created: (JBIDE-1719) Some bugs for <h:selectMany*> components.
by Andrei Scherbovich (JIRA)
Some bugs for <h:selectMany*> components.
-----------------------------------------
Key: JBIDE-1719
URL: http://jira.jboss.com/jira/browse/JBIDE-1719
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor
Affects Versions: 2.0.0.GA
Reporter: Andrei Scherbovich
Assigned To: Maxim Areshkau
Attachments: 1.jpg
<h:selectManyCheckbox>
1) Attributes "dir", "disabled", "disabledClass", "enabledClass" don't work
<h:selectManyListBox> and <h:selectManyMenu>
1) Attributes "dir", "disabled", "disabledClass", "enabledClass", "styleClass", "style" don't work
2) Bad highlighting of selected in VPE elements of these components
<f:selectItem>
1) Attribute "escape" doesn't work
(SEE ATTACHMENT)
--
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
16 years