[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-4514) Improve performance of Seam Validator when a Java file is modified

[Alexey Kazakov (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBIDE-4514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12472945#action_12472945 ] 

Alexey Kazakov commented on JBIDE-4514:
---------------------------------------

What Seam EL validator does if you change *.java:
- find all context variables which is defined in this java. (@Name, @Out, ...)
- Re-validate all files which use this variables.
- Re-validate all files which use unresolved variables (just in case if changed java defines new variable now)

My suggestion is to add new option to preferences to disable re-validation unresolved ELs. In most cases it may increase performance for big complex projects.

> Improve performance of Seam Validator when a Java file is modified
> ------------------------------------------------------------------
>
>                 Key: JBIDE-4514
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-4514
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: Seam
>    Affects Versions: 3.0.0.GA
>         Environment: JBossTools-ALL-win32-3.0.1.GA-R200905070146-H18, Seam 2.1.2.GA
>            Reporter: Julien Kronegg
>            Assignee: Alexey Kazakov
>             Fix For: 3.1.0.M2
>
>
> Seam Validator checks EL expressions in WebContent/*.xhtml pages when a Java file is modified.
> On a Intel Core2 1.83 GHz T5600 machine with 2 GB RAM, it takes about 0.5 second per XHTML page generated by seam-gen (and modified using the workaround described in JBIDE-4512 to have no "property cannot be resolved" warnings). This is very high and has a big impact if you got a lot of XHTML pages (I got 150 of them!).
> So it would be nice if the whole validation process could take about 2-5 seconds (instead of about 2 minutes for me).

-- 
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