]
David Delbecq commented on JBIDE-675:
-------------------------------------
Hello, i come back with additional informations
I downloaded Redhat Developper Studio 2 beta1, as it seems to replace exadel studio. I
tried to open file and have to inform you it still take 42 seconds on a 2.8Ghz dual core
computer to open my form. I attach a file (stacktraces-rhd2b1.log.gz) that provides a few
stacktraces generated from the "double click on employee.xhtml" to the highlight
some are of source.
Note that behaviour vary.
Sometimes i wait around 20 seconds to get code then wait another 20 second to get a
reactive pointer (code displayed but interface frozen)
Sometimes if have to wait a plain 40 seconds and then i immediatly have a reactive area.
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: JBoss Tools
Issue Type: Bug
Components: JSF
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
Attachments: .classpath, copy_dump.txt, edit_dump1.txt, edit_dump2.txt,
editStructure.txt, loading_dump.txt, 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: