[ http://jira.jboss.com/jira/browse/JBIDE-845?page=comments#action_12376857 ] Viacheslav Kabanovich commented on JBIDE-845: --------------------------------------------- It is likely to be WTP bug. I have been able to reproduce it with wtp's XML Editor (not Faces Config Editor!). I also found that to increase probability of failure, it is needed, after having saved modifications and before closing editor, to wait while all internal jobs in Eclipse are completed (flashing info in the right lower corner of Eclipse may indicate their progress). Cause looks as follows: wtp has internal model for faces config, that is used in Faces Config Editor. That model is hooked to wtp's xml model. Any client that uses wtp's xml model must take it for read and then release it from read. If wtp's xml model is not released by some client, after reopening wtp's xml editor will not work correctly, one of results being the failure of content assist. I found that if wtp's XML Editor (or Red Hat XML Editor) is used, then after saving modifications, internal wtp's model for faces config hooks to wtp's xml model, and does not release it, because it is designed to release xml model on closing its Faces Config Editor. The same problem takes place with web.xml. Again, wtp has internal model for it hooked to xml model, and in the same manner, it takes xml model for edit after saving modifications in XML Editor, and does not release 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-845?page=comments#action_12380548 ] Denis Golovin commented on JBIDE-845: ------------------------------------- Slava, could you provide reference to WTP bug in bugzilla? If no please create bug in eclipse bugzilla and put it in issue 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-845?page=all ] Rob Stryker updated JBIDE-845: ------------------------------ Component/s: UpStream Changing component to upstream -- 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-845?page=all ] Max Andersen updated JBIDE-845: ------------------------------- Fix Version/s: 2.1.x (was: LATER) Priority: Optional (was: Major) seem the bug should be fixed in WTP 2.0.2 - but we cant recommend using that yet before the ear deployment issue is fixed. -- 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-845?page=all ] Anton Klimkovich closed JBIDE-845. ---------------------------------- Verified on: (2.1.2) 200806192021-nightly and (3.0 alpha) 200806192047-nightly -- 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