[
http://jira.jboss.com/jira/browse/JBIDE-1318?page=comments#action_12405792 ]
Alexey Kazakov commented on JBIDE-1318:
---------------------------------------
Yes.
What we have:
1. WTP JSF EL validator. It uses JSF EL variable resolver.
2. Our Seam EL validator. It uses our seam variable resolver.
What we can do:
1. Disable WTP JSF EL validation. And use only our validator.
2. Try to have a mixture of our and JSF validators. I think it's very hard to
implement it in proper way.
How we can disable WTP JSF EL validation.
1. Disable the proper rule in the preferences of WTP JSF Tools. (for example we can do it
using our firstrun plug-in). Disadvantage: It's kind of hack ;)
2. Disable JSF EL variable resolver (using extension point) for all seam projects.
Disadvantage: we can lost some functions of WTP JSF Tools that use this resolver. But I
don't think that users can find a lot of benefits of such features in real seam
projects. Maybe I'm wrong.
I'm out of ideas :(
How we can solve this problem better?
Hook into WTP JSF el model to avoid duplicate warnings
------------------------------------------------------
Key: JBIDE-1318
URL:
http://jira.jboss.com/jira/browse/JBIDE-1318
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor
Affects Versions: 2.0.0.CR1
Environment: Windows XP Pro version 2002
Reporter: Matt Fischer
Assigned To: Alexey Kazakov
Priority: Minor
Fix For: 2.1
Attachments: RHDS-295.zip
Max - Here's the details.
Open RHDS, no warnings on .jsp pages.
Open a .jsp file, not warnings.
Add code that references a ManagedBean. Click Save. Warnings for referenced Beans
(& bundles BTW) appear.
Go To Project Clean - warnings appear for all beans.
I'll included an .avi file and log file again.
Matt
--
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