[
https://jira.jboss.org/jira/browse/JBIDE-4545?page=com.atlassian.jira.plu...
]
Julien Kronegg commented on JBIDE-4545:
---------------------------------------
On a "big" project generated with seam-gen (64 entities, 180 xhtml, 180
.page.xml), I saw no improvement.
I have a MyEntityHome with @Name annotation and two @In properties, referred 415 times in
the project in 58 xhtml or page.xml files.
JBossTools-ALL-win32-3.1.0.M2-N200906241801-H293
- full validation after clean: 80-90 seconds
- validation of MyEntityHome: 4-5 seconds
JBossTools-ALL-win32-3.1.0.M3-N200907020001-H7
- full validation after clean: 90-140 seconds
- validation of MyEntityHome: 4-5 seconds (the .xhtml or .page.xml resource name is not
displayed anymore in the progress bar)
Revalidate El only if referenced context variable was changed.
--------------------------------------------------------------
Key: JBIDE-4545
URL:
https://jira.jboss.org/jira/browse/JBIDE-4545
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Seam
Reporter: Alexey Kazakov
Assignee: Alexey Kazakov
Fix For: 3.1.0.M3
Now we have a mapping in EL validator between context variable names and resources that
reference to them.
So if user changed a *.java with @Name("name1") we revalidate all resources
which have #{name1...}
But actually we don't need to parse whole resource again to find #{name1...}.
It's too slow.
Let's improove this one and keep references between each EL and variable name. Then
we will be able to revalidate particular EL if context variable was changed.
It's won't require so slow parsing of each resource with referenced ELs.
--
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