July 2008 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-2420) Exception appears on "<ctrl>+z" combination in jsp page.

by Andrei Scherbovich (JIRA)

Exception appears on "<ctrl>+z" combination in jsp page. --------------------------------------------------------- Key: JBIDE-2420 URL: http://jira.jboss.com/jira/browse/JBIDE-2420 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor Affects Versions: 3.0.0.alpha Environment: subversion revision 8913 windows xp Reporter: Andrei Scherbovich Assigned To: Maxim Areshkau Exception appears on "<ctrl>+z" combination in jsp page. Steps: EXECUTE: Use content assist to enter any tag on jsp page (<f:facet> e.g.) EXECUTE: Press "<ctrl>+z" to undo last action FAILURE: Exception appears java.lang.RuntimeException: java.lang.IllegalStateException: already in a rewrite session at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.startRewriteSession(JobSafeStructuredDocument.java:224) at org.eclipse.wst.sse.core.internal.undo.StructuredTextUndoManager.undo(StructuredTextUndoManager.java:636) at org.eclipse.wst.sse.ui.StructuredTextViewerUndoManager.undo(StructuredTextViewerUndoManager.java:183) at org.eclipse.jface.text.TextViewer.doOperation(TextViewer.java:3718) at org.eclipse.jface.text.source.SourceViewer.doOperation(SourceViewer.java:891) at org.eclipse.jface.text.source.projection.ProjectionViewer.doOperation(ProjectionViewer.java:1423) at org.eclipse.wst.sse.ui.internal.StructuredTextViewer.doOperation(StructuredTextViewer.java:595) at org.jboss.tools.jst.jsp.jspeditor.JSPTextEditor$JSPStructuredTextViewer.doOperation(JSPTextEditor.java:675) at org.eclipse.ui.texteditor.TextOperationAction$1.run(TextOperationAction.java:131) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ui.texteditor.TextOperationAction.run(TextOperationAction.java:129) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.ui.commands.ActionHandler.execute(ActionHandler.java:185) at org.eclipse.ui.internal.handlers.LegacyHandlerWrapper.execute(LegacyHandlerWrapper.java:109) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.executeCommand(WorkbenchKeyboard.java:471) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.press(WorkbenchKeyboard.java:822) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.processKeyEvent(WorkbenchKeyboard.java:880) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.filterKeySequenceBindings(WorkbenchKeyboard.java:569) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.access$3(WorkbenchKeyboard.java:511) at org.eclipse.ui.internal.keys.WorkbenchKeyboard$KeyDownFilter.handleEvent(WorkbenchKeyboard.java:126) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.filterEvent(Display.java:1184) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1002) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1027) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1012) at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1040) at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1036) at org.eclipse.swt.widgets.Widget.wmChar(Widget.java:1352) at org.eclipse.swt.widgets.Control.WM_CHAR(Control.java:3894) at org.eclipse.swt.widgets.Canvas.WM_CHAR(Canvas.java:341) at org.eclipse.swt.widgets.Control.windowProc(Control.java:3787) at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:337) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4528) at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method) at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2370) 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:382) 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) Caused by: java.lang.IllegalStateException: already in a rewrite session at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.internalStartRewriteSession(BasicStructuredDocument.java:2775) at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument$3.run(JobSafeStructuredDocument.java:204) at org.eclipse.wst.sse.ui.EditorExecutionContext.execute(EditorExecutionContext.java:42) at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.startRewriteSession(JobSafeStructuredDocument.java:216) ... 59 more -- 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

15 years, 7 months

6
5
0 / 0

[JBoss JIRA] Created: (JBIDE-2063) java.lang.NullPointerException when open file w/o extension in JBoss Tools JSP/HTML editors.

by Anton Klimkovich (JIRA)

java.lang.NullPointerException when open file w/o extension in JBoss Tools JSP/HTML editors. -------------------------------------------------------------------------------------------- Key: JBIDE-2063 URL: http://jira.jboss.com/jira/browse/JBIDE-2063 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor Affects Versions: 2.1.0.beta1 Reporter: Anton Klimkovich Priority: Minor Attachments: exception1.txt, exception2.txt EXECUTE: Create jsf project EXECUTE: Open Web Projects view EXECUTE: New-> File ->Any Extension... EXECUTE: Input file name w/o input any extensio ASSERT: File will be opened in Default editor EXECUTE: Open file with the help of JBoss Tools JSP/HTML editors. FAILURE: File won't be opened and some exceptions occured. Log attached. Error occures if open file w/o extension also with the help of Web Page Editor. (WTP) -- 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

15 years, 7 months

5
5
0 / 0

[JBoss JIRA] Created: (JBIDE-2433) org.mozilla.xpcom.XPCOMException occured when edit xhtml pages in specific way.

by Anton Klimkovich (JIRA)

org.mozilla.xpcom.XPCOMException occured when edit xhtml pages in specific way. ------------------------------------------------------------------------------- Key: JBIDE-2433 URL: http://jira.jboss.com/jira/browse/JBIDE-2433 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor Affects Versions: 2.1.2 Environment: 200806231717-nightly Reporter: Anton Klimkovich Assigned To: Maxim Areshkau EXECUTE: Create jsf kickstart project EXECUTE: Create Xhtml page with template FaceletBlank (FaceletBlank.xhtml) EXECUTE: Create Xhtml page with template FaceletCommon (FaceletCommon.xhtml) EXECUTE: Create Xhtml page with template FaceletForm (FaceletForm.xhtml) EXECUTE: Open FaceletBlank.xhtml and set path to FaceletCommon.xhtml in <ui:composition template="" and do not save the file EXECUTE: Open FaceletForm.xhtml and set path to FaceletBlank.xhtml EXECUTE: Save page and close the Editor EXECUTE: Save FaceletBlank.xhtml EXECUTE: Open FaceletForm.xhtml and press Ctrl+z and do not save the file EXECUTE: Set path to FaceletBlank.xhtml in <ui:composition template=""> EXECUTE: Save page and close the Editor FAILURE: org.mozilla.xpcom.XPCOMException: The function "removeSelectionListener" returned an error condition (0x80004005) EXECUTE: Reopen FaceletForm.xhtml and edit something FAILURE: Some exceptions occured. -- 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

15 years, 7 months

5
10
0 / 0

[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

15 years, 7 months

7
17
0 / 0

[JBoss JIRA] Created: (JBIDE-2124) The Deadlock occures during the text editing

by Victor Rubezhny (JIRA)

The Deadlock occures during the text editing -------------------------------------------- Key: JBIDE-2124 URL: http://jira.jboss.com/jira/browse/JBIDE-2124 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Victor Rubezhny Attachments: DeadLock.txt The deadlock occures during the text editing while performing the code formatting. Steps to reproduce: - create a large Seam project (as described in http://jira.jboss.com/jira/browse/JBIDE-1105#action_12394448 , for instance) - open a few files in the VPE editor - select the WebContent directory and choose Source>Format - edit files during the code formatting See the stacktrace (DeadLock.txt) -- 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

15 years, 7 months

4
8
0 / 0

[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

15 years, 7 months

8
9
0 / 0

[JBoss JIRA] Created: (JBIDE-2541) Show java-doc for EL content assist item

by Denis Golovin (JIRA)

Show java-doc for EL content assist item ---------------------------------------- Key: JBIDE-2541 URL: https://jira.jboss.org/jira/browse/JBIDE-2541 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Denis Golovin Assignee: Alexey Kazakov Attachments: java-doc-for-java-ca.png Show documentation for EL proposals as java does for methods see attached screen shots -- 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

15 years, 7 months

5
19
0 / 0

[JBoss JIRA] Created: (JBIDE-2394) Seam EL is absent in proposal list of CA if there is no space between { and end of tag.

by Anton Klimkovich (JIRA)

Seam EL is absent in proposal list of CA if there is no space between { and end of tag. ---------------------------------------------------------------------------------------- Key: JBIDE-2394 URL: http://jira.jboss.com/jira/browse/JBIDE-2394 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing, Visual Page Editor Affects Versions: 2.1.2 Reporter: Anton Klimkovich Attachments: CAwithoutSeamEL.PNG EXECUTE: Create Seam web project EXECUTE: Open any .xhtml EXECUTE: Type <h:outputText value="#{/> EXECUTE: Set cursor between { and end of tag (<h:outputText value="#{|cursor|/>) EXECUTE: call CA FAILURE: There is no Seam EL in proposal list. -- 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

15 years, 7 months

6
18
0 / 0

[JBoss JIRA] Created: (JBDS-267) Jboss tools on Wiki description

by Svetlana mukhina (JIRA)

Jboss tools on Wiki description -------------------------------- Key: JBDS-267 URL: http://jira.jboss.com/jira/browse/JBDS-267 Project: Developer Studio Issue Type: Task Components: documentation Affects Versions: 1.0.0.GA Reporter: Svetlana mukhina Assigned To: Svetlana mukhina Fix For: 1.0.1 I think we should look through wiki, decided what else could be added there and then in guides give links to this resource. also it will be good to give a link there - http://labs.jboss.com/projects/docs -- 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

15 years, 7 months

3
18
0 / 0

[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

15 years, 8 months

9
40
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2008