[ https://jira.jboss.org/jira/browse/JBIDE-5617?page=com.atlassian.jira.plu... ] Tom Fennelly commented on JBIDE-5617: ------------------------------------- This should be fixed IMO. -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-5617?page=com.atlassian.jira.plu... ] Tom Fennelly commented on JBIDE-5617: ------------------------------------- Attaching the docs (written last year) re hiding/showing model nodes: http://community.jboss.org/wiki/SmooksEditorTemplateGeneration#Hiding_and... If there's anything there that does not make sense, please let me know and I'll attempt to clarify. -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-5617?page=com.atlassian.jira.plu... ] Xue Peng commented on JBIDE-5617: --------------------------------- Tom , In FreemarkerTemplateXMLModel , I use this way to judge is it a hidden node: 1. Get the value of the "hidden" attribute. 2. If this node is under a "choice" element node , to get all other nodes in this "choice" element node , if one of them has been linked , other nodes are hidden. I will change my codes with the TemplateBuilder API. -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-5617?page=com.atlassian.jira.plu... ] Tom Fennelly commented on JBIDE-5617: ------------------------------------- I'm not really sure what your issue is from your description. I had a look at how you're using the templating API and you're not using it as it was intended. Perhaps I wasn't clear enough about this in the docs. You seem to be creating a new Template Builder instance with every add/remove of a mapping. The intention always was that the editor would maintain a single instance of the TemplateBuilder (per template), adding and removing mappings from it as the user adds and removes mappings. On this single instance, you can call TemplateBuilder.buildTemplate() as many times as you like i.e. for every mapping added/removed. This might be OK, but I'm not sure since it is not how the templating API was designed to be used. Is there any way we can change to use it as intended? I find it hard to see how you are doing it currently without duplicating some of the behavior of the templating API, recording the current set of mappings etc so you can do your "replay all mappings" for every add/remove mappings (as you are currently doing, as it seems to me). In order to do the replay, you must have a record of all the mappings, right? You shouldn't need to be doing this replay and since it was not as it was intended to be used, I'm not sure of side effects etc. If you can't redo the editor parts, then I will look more closely and try to get the tests in the templating API to better match how you are using it. That way we'll have a better idea of what the possible side effects are. -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-5617?page=com.atlassian.jira.plu... ] Tom Fennelly closed JBIDE-5617. ------------------------------- Resolution: Done This looks to be working guys... going to close for now. Hope that's OK :) -- 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