[JBoss JIRA] Commented: (JBIDE-675) Large JSF file are too slow to handle, making editor useless for them
by Sergey Vasilyev (JIRA)
[ http://jira.jboss.com/jira/browse/JBIDE-675?page=comments#action_12406711 ]
Sergey Vasilyev commented on JBIDE-675:
---------------------------------------
For solve troubles with key pressing a new issue was created http://jira.jboss.com/jira/browse/JBIDE-1986.
This issue should be used only to solve trouble with the includes.
> Large JSF file are too slow to handle, making editor useless for them
> ---------------------------------------------------------------------
>
> Key: JBIDE-675
> URL: http://jira.jboss.com/jira/browse/JBIDE-675
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JSF, Visual Page Editor
> Affects Versions: ExadelStudioPro4
> Environment: Eclipse 3.2.2
> Exadel Studio 4.0.4
> Kubuntu Feisty Fawn
> 1G RAM
> CPU Intel(R) Pentium(R) 4 CPU 2.80GHz, HyperThreading activated
> Reporter: David Delbecq
> Assigned To: Maxim Areshkau
> Priority: Critical
> Fix For: 2.2.x
>
> Attachments: .classpath, copy_dump.txt, edit_dump1.txt, edit_dump2.txt, editStructure.txt, JBIDE-675.tar.gz, loading_dump.txt, profiling.tar.gz, stacktraces-rhd2b1.log.gz, tree.txt
>
>
> Post to JIRA, following recommandatiopn here: http://jboss.com/index.html?module=bb&op=viewtopic&t=115447
> When editing JSF files That contains quite a lot of include, it take commonly up to 20 seconds for one character i type to get it's way to the screen. I can even see, after 10 seconds, the cursor goes on step right, and after a new 10 second the character appear in front of the cursor. This make it impossible to use JSF editor from exadel to edit such file, i have to ressort to plain xml editor without completion for facelets tags.
> I will be posting attachement containing description of files involved (sorry, no file content).
--
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, 2 months
[JBoss JIRA] Created: (JBIDE-1146) Problems with creating Seam ear web project using jre1.6.0_02.
by Anton Klimkovich (JIRA)
Problems with creating Seam ear web project using jre1.6.0_02.
--------------------------------------------------------------
Key: JBIDE-1146
URL: http://jira.jboss.com/jira/browse/JBIDE-1146
Project: JBoss Tools
Issue Type: Bug
Components: Seam, seam-gen
Affects Versions: 2.0.0.Beta4
Environment: WinXp
jre1.6.0_02
200710210005-nightly
Reporter: Anton Klimkovich
Priority: Minor
Attachments: seam.PNG
Create Seam ear project (File->New->Project->Seam->Seam Web Project)
After validation complete some errors will occure.
java.lang.NullPointerException
at org.jboss.tools.seam.internal.core.validation.SeamCoreValidator.validateXmlComponentDeclarations(SeamCoreValidator.java:448)
at org.jboss.tools.seam.internal.core.validation.SeamCoreValidator.validateComponent(SeamCoreValidator.java:402)
at org.jboss.tools.seam.internal.core.validation.SeamCoreValidator.validateComponent(SeamCoreValidator.java:323)
at org.jboss.tools.seam.internal.core.validation.SeamCoreValidator.validate(SeamCoreValidator.java:161)
at org.jboss.tools.seam.internal.core.validation.SeamValidatorManager.validate(SeamValidatorManager.java:75)
at org.jboss.tools.seam.internal.core.validation.SeamValidatorManager.validateInJob(SeamValidatorManager.java:60)
at org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:75)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
--
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, 2 months
[JBoss JIRA] Created: (JBIDE-1958) JBoss JSP Editor fails to load
by Alex Titov (JIRA)
JBoss JSP Editor fails to load
-------------------------------
Key: JBIDE-1958
URL: http://jira.jboss.com/jira/browse/JBIDE-1958
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsp/jsf/xml source editing
Affects Versions: 2.0.1
Environment: Ubuntu 7.10
Reporter: Alex Titov
Priority: Minor
In unpredictable cases JSP editor cannot start. To start it I have to reload Eclipse.
!ENTRY org.eclipse.jface 4 2 2008-03-26 21:02:16.376
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.jface".
!STACK 0
java.lang.NoClassDefFoundError: Could not initialize class sun.awt.X11GraphicsEnvironment
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:169)
at java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment(GraphicsEnvironment.java:68)
at org.jboss.tools.vpe.editor.toolbar.format.TextFormattingToolBar.createItems(TextFormattingToolBar.java:92)
at org.jboss.tools.vpe.editor.toolbar.SplitToolBar.createToolBarControl(SplitToolBar.java:36)
at org.jboss.tools.vpe.editor.toolbar.VpeToolBarManager.addToolBar(VpeToolBarManager.java:84)
at org.jboss.tools.vpe.editor.mozilla.MozillaEditor.createPartControl(MozillaEditor.java:154)
at org.jboss.tools.vpe.editor.VpeEditorPart.createPartControl(VpeEditorPart.java:518)
at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditorPart.addPage(JSPMultiPageEditorPart.java:82)
at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditor.createPagesForWindows(JSPMultiPageEditor.java:399)
at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditor.createPages(JSPMultiPageEditor.java:375)
at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditorPart.createPartControl(JSPMultiPageEditorPart.java:124)
at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:661)
at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:426)
at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:592)
at org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:263)
at org.eclipse.ui.internal.EditorManager.findEditor(EditorManager.java:398)
at org.eclipse.ui.internal.EditorManager.findEditor(EditorManager.java:376)
at org.eclipse.ui.internal.WorkbenchPage.findEditor(WorkbenchPage.java:1985)
at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.isOpenInEditor(EditorUtility.java:112)
at org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart.linkToEditor(PackageExplorerPart.java:1024)
at org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart.handlePostSelectionChanged(PackageExplorerPart.java:928)
at org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart.access$1(PackageExplorerPart.java:923)
at org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart$3.selectionChanged(PackageExplorerPart.java:441)
at org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:842)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at org.eclipse.core.runtime.Platform.run(Platform.java:857)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:46)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:199)
at org.eclipse.jface.viewers.StructuredViewer.firePostSelectionChanged(StructuredViewer.java:840)
at org.eclipse.jface.viewers.StructuredViewer.handlePostSelect(StructuredViewer.java:1153)
at org.eclipse.jface.viewers.StructuredViewer$5.widgetSelected(StructuredViewer.java:1178)
at org.eclipse.jface.util.OpenStrategy.firePostSelectionEvent(OpenStrategy.java:250)
at org.eclipse.jface.util.OpenStrategy.access$4(OpenStrategy.java:244)
at org.eclipse.jface.util.OpenStrategy$3.run(OpenStrategy.java:418)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:129)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3296)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2974)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219)
at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:169)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
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:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:508)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447)
at org.eclipse.equinox.launcher.Main.run(Main.java:1173)
Version: 3.3.2
Build id: M20080221-1800
awt.toolkit=sun.awt.motif.MToolkit
java: sun jvm 1.6.0.03
--
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, 2 months
[JBoss JIRA] Created: (JBIDE-1978) VPE doesn't work at all in the latest build.
by Anton Klimkovich (JIRA)
VPE doesn't work at all in the latest build.
--------------------------------------------
Key: JBIDE-1978
URL: http://jira.jboss.com/jira/browse/JBIDE-1978
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor
Affects Versions: 2.1
Environment: Build 200803312120-nightly
WinXP
Reporter: Anton Klimkovich
Assigned To: Maxim Areshkau
Priority: Critical
Attachments: exception.txt, exception1.txt, exception2.txt
EXECUTE: Create JSFKickStart project or JSFwithFaceletsKickStart project or Seam project
EXECUTE: Open inputUserName.jsp or any othe page (jsp, xhtml)
ASSERT: JBoss Editor is opened on Visual/Source tab without any exceptions
FAILURE: java.lang.IllegalArgumentException: Message parameter cannot be null
Full log attached.
java.lang.NullPointerException
EXECUTE: Set cursor to Source part
FAILURE: java.lang.NullPointerException
at org.jboss.tools.vpe.editor.toolbar.format.FormatControllerManager.getFormatTemplateForTag(FormatControllerManager.java:227)
EXECUTE: Swith to different tabs.
FAILURE: Also a lot of different exceptions fall.
--
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, 2 months
[JBoss JIRA] Created: (JBIDE-1776) Tools palette: divide widgets on "simple" and "advanced"
by Alex Ivanov (JIRA)
Tools palette: divide widgets on "simple" and "advanced"
--------------------------------------------------------
Key: JBIDE-1776
URL: http://jira.jboss.com/jira/browse/JBIDE-1776
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: jsp/jsf/xml source editing
Reporter: Alex Ivanov
Priority: Trivial
In Jboss tools palette, both "JBoss Ajax4JSF" and particularly "JBoss RichFaces" list are overwhelming.
Everything is listed which is good but novice user is lost in dozens of widgets.
I suggest to split palette on "RichFaces simple" and "RichFaces full". You can even keep "RichFaces full" palette closed unless user clicks "Show Full Palette" button, displayed on "RichFaces simple"
Alternative name: "RichFaces essential" but that's a longer name.
--
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, 2 months
[JBoss JIRA] Commented: (JBIDE-675) Large JSF file are too slow to handle, making editor useless for them
by Maxim Areshkau (JIRA)
[ http://jira.jboss.com/jira/browse/JBIDE-675?page=comments#action_12406490 ]
Maxim Areshkau commented on JBIDE-675:
--------------------------------------
I have forget about it's thread :). But here sayed about SWT modification (including embeding mozilla browser). May be for SWT it's have a reason, but we need modify only mozilla DOM elements(this is not SWT objects). so I will commit my changes in next iteration.
> Large JSF file are too slow to handle, making editor useless for them
> ---------------------------------------------------------------------
>
> Key: JBIDE-675
> URL: http://jira.jboss.com/jira/browse/JBIDE-675
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JSF, Visual Page Editor
> Affects Versions: ExadelStudioPro4
> Environment: Eclipse 3.2.2
> Exadel Studio 4.0.4
> Kubuntu Feisty Fawn
> 1G RAM
> CPU Intel(R) Pentium(R) 4 CPU 2.80GHz, HyperThreading activated
> Reporter: David Delbecq
> Assigned To: Maxim Areshkau
> Priority: Critical
> Fix For: 2.2.x
>
> Attachments: .classpath, copy_dump.txt, edit_dump1.txt, edit_dump2.txt, editStructure.txt, JBIDE-675.tar.gz, loading_dump.txt, profiling.tar.gz, stacktraces-rhd2b1.log.gz, tree.txt
>
>
> Post to JIRA, following recommandatiopn here: http://jboss.com/index.html?module=bb&op=viewtopic&t=115447
> When editing JSF files That contains quite a lot of include, it take commonly up to 20 seconds for one character i type to get it's way to the screen. I can even see, after 10 seconds, the cursor goes on step right, and after a new 10 second the character appear in front of the cursor. This make it impossible to use JSF editor from exadel to edit such file, i have to ressort to plain xml editor without completion for facelets tags.
> I will be posting attachement containing description of files involved (sorry, no file content).
--
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, 2 months