[JBoss JIRA] Created: (JBIDE-1531) Editors not shown at first when an xhtml file is opened in the jboss editor (but does after toggling another tab)
by Ernout vd Waard (JIRA)
Editors not shown at first when an xhtml file is opened in the jboss editor (but does after toggling another tab)
-----------------------------------------------------------------------------------------------------------------
Key: JBIDE-1531
URL: http://jira.jboss.com/jira/browse/JBIDE-1531
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor
Affects Versions: 2.0.0.GA
Environment: We use the following versions:
- Eclipse 3.3.1.1
- JBoss Tools 2.0.0.GA
- Java JDK6 64 bit
Reporter: Ernout vd Waard
When we open a xhtml file in the jboss html editor, the first time there isn't anything show, just a grey background.
The tabs at the bottom of the pane are shown, and if you click another tab the editor is shown and you can use all different edit modes.
I can close the editor and open a new one and it works again after toggling the tab.
We are running Eclipse on Windows Vista 64, and maybe this has something to do with it. When we copied the configuration to a Vista 32 bit machine, the problem went away.
It would be great if someone could point us in the right direction of where to continue our search!
Another hint may be that the settings pane for the visual editor also is blank after we used the editor once.
What we've tried so far (but did not succeed):
- update to nightly build of jboss tools
- searched the jira
- searched the forums
- edit the code ourselves
- tried running this eclipse configuration with JDK 5 (both 64 as 32 bit)
- tried setting another default editor
--
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-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] Resolved: (JBDS-1110) reconfigure .htaccess rules for devstudio.jboss.com
by Nick Boldt (JIRA)
[ https://jira.jboss.org/jira/browse/JBDS-1110?page=com.atlassian.jira.plug... ]
Nick Boldt resolved JBDS-1110.
------------------------------
Fix Version/s: 3.0.0.GA
(was: 3.0.1.GA)
Resolution: Done
Assignee: Nick Boldt (was: prakash aradhya)
Thanks to Scott Henson <shenson(a)redhat.com>, I now have full control over .htaccess on devstudio.jboss.com, so we can implement/remove passwords on dirs as needed.
> reconfigure .htaccess rules for devstudio.jboss.com
> ---------------------------------------------------
>
> Key: JBDS-1110
> URL: https://jira.jboss.org/jira/browse/JBDS-1110
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Components: updatesite
> Affects Versions: 3.0.0.CR3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 3.0.0.GA
>
>
> Problem
> -----------
> Currently we host update site files and some Early Access (EA) JBoss Dev Studio (JBDS) installers (.jar) on http(s)://devstudio.jboss.com.
> Everyone using the site shares the same access, which is somewhat painful for several reasons:
> a) No one can "discover" what's on the site because the root folder is restricted.
> b) EA users and existing registered JBDS users may not be the same folks; in fact, we may want to provide *FREE* EA access to encourage people to try-before-buy the forthcoming JBDS release, independent of possibly being an existing subscriber.
> c) Each annual release of JBDS gets a year of updates, but only for the product for which they subscribed; thus each year's update site should be differently restricted rather than using the shared across-the-board login.
> Ideally, username/password restriction would be fed by information in the CSP so that users would only need a single login, which would expire the minute their subscription expired, rather than using shared passwords via .htaccess; however, that requires significantly (?) more effort than the solution proposed below.
> Solution
> -----------
> a) remove .htaccess username/password restriction for these folders:
> http://devstudio.jboss.com/
> http://devstudio.jboss.com/updates/
> http://devstudio.jboss.com/earlyaccess/
> b) add .htaccess username/password restriction for these folders:
> http://devstudio.jboss.com/updates/2.1/ (use existing username/password)
> http://devstudio.jboss.com/updates/3.0/ (create new username/password)
> http://devstudio.jboss.com/earlyaccess/builds/ (use existing username/password + create second new username/password)
> I will send the current login details & proposed new ones along in an email to helpdesk@ so that they're not copied publicly here.
> Note that JBDS 3.0 is scheduled to be released March 10, and we need to get these changes in place before then.
--
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