[ https://jira.jboss.org/jira/browse/JBIDE-6212?page=com.atlassian.jira.plu... ] Victor Rubezhny updated JBIDE-6212: ----------------------------------- Attachment: assertionFailedException.txt -- 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-6212?page=com.atlassian.jira.plu... ] Victor Rubezhny updated JBIDE-6212: ----------------------------------- Fix Version/s: 3.6-Helios (was: 3.2.next) Affects Version/s: 3.2.next -- 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-6212?page=com.atlassian.jira.plu... ] Victor Rubezhny commented on JBIDE-6212: ---------------------------------------- Because of the latest changes in WST StructuredContentAssistProcessor class we cannot use the HTML/JSP/XML processors as children of our special compound CA processor (SortingCompoundContentAssistProcessor). The Completion event was added to the processors and its handler methods deny any handling in case of the Completion event came not from the root Compound CA Processor (there is another case but it is not useful for us). So, this event processing denial prevents the CA Processor to be initialized properly on CA proposals calculation. As result we have faced two main problems: 1. We cannot filter the proposal duplications (Some tag/attribute proposals come from two different sources - from WST HTML CA Processor and from our CA XHTML CA processor simultaneously - and then they are to be filtered with our Sorting Compound CA Processor before they will be shown in CA selector window). 2. We cannot be sure in how the proposals will be ordered in CA selector window. In Eclipse 3.5 we had control on the overall ranking and sorting process, but in Eclipse 3,6 we'll have no such possibility (at least it will be very cut). As the only solution I can suggest to move some functionality of SortingCompoundContentAssistProcessor (which was used to collect/unify/sort proposals from all the available sources including the WST CA processors) to the SourceViewerConfiguration (which is used to create a set of CA processors for the editor). If it will be possible to set up the CA processor acquiring procedure that we could call our (JBoss) CA processors at first and WST CA processors at last, so probably we can solve these problems. The next modification is not a problem but probably a feature request for us: In Eclipse 3.6 the WST CA Processors (derived from StructuredContentAssistProcessor) are widely using the CA Categories (as result a user may choose different kinds of proposals to be shown in the CA selector window by sequential pressing Ctrl-Space key combination). No categories are realized in JBoss CA Processors. But probably it will be useful to add categories for JSF/Seam/CDI EL proposals. -- 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/browse/JBIDE-6212?page=com.atlassian.jira.plugin.s... ] Victor Rubezhny resolved JBIDE-6212. ------------------------------------ Resolution: Done -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira