[ http://jira.jboss.com/jira/browse/JBIDE-999?page=all ] Max Andersen moved RHDS-207 to JBIDE-999: ----------------------------------------- Project: JBoss Tools (was: Red Hat Developer Studio) Key: JBIDE-999 (was: RHDS-207) Affects Version/s: 2.0.0.Beta3 (was: 1.0.0.beta1) -- 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-999?page=all ] Denis Golovin reassigned JBIDE-999: ----------------------------------- Assignee: Alexey Kazakov -- 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-999?page=all ] Max Andersen updated JBIDE-999: ------------------------------- Issue Type: Feature Request (was: Bug) Fix Version/s: 2.1 (was: 2.0.0.CR1) yes - new feature. Definitly makes sense to support it. -- 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-999?page=comments#action_12396900 ] Max Andersen commented on JBIDE-999: ------------------------------------ first version should just look for variables upwards in the dom3 and see if there is a var attribute on a known tag like h:dataTable. -- 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-999?page=comments#action_12397656 ] Max Andersen commented on JBIDE-999: ------------------------------------ Sounds good. comments for the limitations: 1) So our current JSF specific validation (EL's) is not done as part of JSF + extensionspoint contributed by seam plugin ? We need to fix that at some point. 2) Why is knowledge base a big performance hit ? Wouldn't it just be a matter of having a list of components to look for ? e.g. datatable, foreach, etc. ? -- 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-999?page=comments#action_12397662 ] Alexey Kazakov commented on JBIDE-999: -------------------------------------- I mean JSF EL validation in jsp/xhtml. -- 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-999?page=all ] Max Andersen updated JBIDE-999: ------------------------------- Description: Named "var" attributes in a JSF datatable are not being recognized and are therefore evaluated by the Seam Validator as an Invalid Expression. For instance if I have the following: Code: ... <h:dataTable var="entry" value="#{myList}"> <h:column> <h:outputText value="#{entry.value}" /> </h:column> ... myList is recognized but entry is not. #{entry.value} is shown as an Invalid Expression. What we will do: 1. When validator tries to resolve Seam EL in jsp/xhtml we should go up a dom tree and find all elements with "var" attribute. 2. If EL contains name from "var" then we look for "value" attribute. 3. Then we parse "value" attribute and translate it to a Seam context variable. 4. Use the found context variable for validating Seam EL. 5. We will add a new rule in seam validation preferences to let user switch off/on this feature. Here are a few limitations: 1. It will work only for seam projects. But we don't have any JSF validation in jsp/xhtml. 2. We wount recognize any special jsf components with "var". Just looking for every var/value attributes of all parent dom elements. Original Jacob's description: Named "var" attributes in a JSF datatable are not being recognized and are therefore evaluated by the Seam Validator as an Invalid Expression. For instance if I have the following: Code: ... <h:dataTable var="entry" value="#{myList}"> <h:column> <h:outputText value="#{entry.value}" /> </h:column> ... myList is recognized but entry is not. #{entry.value} is shown as an Invalid Expression. was: What we will do: 1. When validator tries to resolve Seam EL in jsp/xhtml we should go up a dom tree and find all elements with "var" attribute. 2. If EL contains name from "var" then we look for "value" attribute. 3. Then we parse "value" attribute and translate it to a Seam context variable. 4. Use the found context variable for validating Seam EL. 5. We will add a new rule in seam validation preferences to let user switch off/on this feature. Here are a few limitations: 1. It will work only for seam projects. But we don't have any JSF validation in jsp/xhtml. 2. We wount recognize any special jsf components with "var". Just looking for every var/value attributes of all parent dom elements. Original Jacob's description: Named "var" attributes in a JSF datatable are not being recognized and are therefore evaluated by the Seam Validator as an Invalid Expression. For instance if I have the following: Code: ... <h:dataTable var="entry" value="#{myList}"> <h:column> <h:outputText value="#{entry.value}" /> </h:column> ... myList is recognized but entry is not. #{entry.value} is shown as an Invalid Expression. updating so the actual problem is also in description. -- 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-999?page=all ] Alexey Kazakov resolved JBIDE-999. ---------------------------------- Resolution: Done -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-999?page=com.atlassian.jira.plug... ] Aliaksey Nis closed JBIDE-999. ------------------------------ Closed. -- 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