[ http://jira.jboss.com/jira/browse/JBIDE-1318?page=all ] Max Andersen moved RHDS-295 to JBIDE-1318: ------------------------------------------ Project: JBoss Tools (was: Red Hat Developer Studio) Key: JBIDE-1318 (was: RHDS-295) Component/s: Visual Page Editor (was: visualeditor) Affects Version/s: 2.0.0.CR1 (was: 1.0.0.beta2) -- 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

[ http://jira.jboss.com/jira/browse/JBIDE-1318?page=all ] Max Andersen updated JBIDE-1318: -------------------------------- Fix Version/s: 2.0.0.GA Matt - let us know if that works for you. -- 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

[ http://jira.jboss.com/jira/browse/JBIDE-1318?page=comments#action_12388085 ] Max Andersen commented on JBIDE-1318: ------------------------------------- you "loose" the JSF validation that doesn't know how to handle seam components ;) -- 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

[ http://jira.jboss.com/jira/browse/JBIDE-1318?page=all ] Max Andersen updated JBIDE-1318: -------------------------------- Summary: Hook into WTP JSF el model to avoid duplicate warnings (was: ManagedBean cannot be resolved after save ) -- 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

[ http://jira.jboss.com/jira/browse/JBIDE-1318?page=all ] Alexey Kazakov updated JBIDE-1318: ---------------------------------- Workaround Description: Disable WTP JSF validator for a project: Project/Properties/Validation/JSP Semantic Validator (JSF) or for all projects: Window/Preferences/Validation/JSP Semantic Validator (JSF) was:Disable WTP JSF validator: Project/Properties/Validation/JSP Semantic Validator (JSF) -- 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

[ http://jira.jboss.com/jira/browse/JBIDE-1318?page=comments#action_12404895 ] Alexey Kazakov commented on JBIDE-1318: --------------------------------------- We can set property "Window/Preferences/Web and XML/JavaServer Faces Tools/Validation/Identifier Resolution/Variable not found" as "Ignore" in our org.jboss.tools.jst.firstrun plugin. -- 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

[ http://jira.jboss.com/jira/browse/JBIDE-1318?page=all ] Alexey Kazakov resolved JBIDE-1318. ----------------------------------- Resolution: Done Fixed for seam projects. If users want to disable this feature for plain JSF projects then they could do it manually (see workaround). -- 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

[ http://jira.jboss.com/jira/browse/JBIDE-1318?page=comments#action_12405773 ] Alexey Kazakov commented on JBIDE-1318: --------------------------------------- We have our own validator for EL in seam projects. Should we get rid of it and try to hook in JSF Tools' one to provide variables? I'm sure we will have a lot of problems with it. And even if we use WTP JSF Tools we still have to use our own validator to provide validation in XHTML, java, xml, ... Also seam extends "usal" EL and we should use our validator even for EL in jsp. So all it means that we can not avoid using our seam validator. I think just disabling WTP JSF validation for resolving EL variables is the best solution. -- 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

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

[ http://jira.jboss.com/jira/browse/JBIDE-1318?page=comments#action_12406394 ] Max Andersen commented on JBIDE-1318: ------------------------------------- Note: this solution just goes in and for seam projects register a variableresolver for WTP's JSF model that will always say a variable is resolvable making its validator stop putting bogus and duplicate warnings. -- 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