[ http://jira.jboss.com/jira/browse/JBIDE-1655?page=comments#action_12395717 ] Max Andersen commented on JBIDE-1655: ------------------------------------- anything in the logs? -- 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-1655?page=comments#action_12395799 ] Chris Simons commented on JBIDE-1655: ------------------------------------- Sorry, I should mention that this was *not* an issue when I was using the Seam 1.21GA runtimes (set through Project -> Seam Settings). We are currently using Seam 2.0 GA and this problem is on all three of our JBoss Tools installations (three developers) running on similar settings. -- 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-1655?page=all ] Max Andersen updated JBIDE-1655: -------------------------------- Fix Version/s: 2.0.1 Assignee: Viacheslav Kabanovich Chris - could you provide some more info ? e.g. sample project that has the issue or ? Slava - got any idea why this could be happening ? -- 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-1655?page=comments#action_12396849 ] Chris Simons commented on JBIDE-1655: ------------------------------------- Viacheslav, Sorry for taking a bit of time to get back to you all. The problem only affects XHTML files (which is odd). The problem does not affect projects created straight from JBoss Tools (Seam or otherwise). Perhaps this can be chalked up to migrating/opening projects that were generated with seam-gen prior to JBoss Tools? -- 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-1655?page=all ] Denis Golovin updated JBIDE-1655: --------------------------------- Due Date: 03/Feb/08 -- 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-1655?page=all ] Chris Simons updated JBIDE-1655: -------------------------------- Attachment: screenshot-1.jpg Wanting to show you that this also seems to apply to TLDs. No matter what folder I put in the "Folder:" text box, Eclipse will not accept the file. This is the exact same behavior as appears when attemping to add a new XHTML file. I can add/create new TLDs into other projects created from scratch, but not "feature-pm" as this was brought over from a previous Exadel Studio Pro workspace. Also keep in mind that I am unable to "Add JSF Capabilities" to the "feature-pm" project shown above (which is another issue I've reported). Thank 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-1655?page=comments#action_12397238 ] Chris Simons commented on JBIDE-1655: ------------------------------------- I also performed a Help -> Report a Problem and referenced this issue number. Thank you for looking into this issue. -- 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-1655?page=all ] Chris Simons updated JBIDE-1655: -------------------------------- Attachment: jbosstools-diagnostics-20080128135249.zip Sorry, I knew that. :) -- 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-1655?page=comments#action_12397355 ] Chris Simons commented on JBIDE-1655: ------------------------------------- Viacheslav and Max, When you pointed to the .settings directory, it reminded me that I had always wondered if this was the problem. Let me run down the steps I did to fix this issue (it also, coincidentally, fixed another bug that I had entered into JIRA, I will put these same comments there, too)... I found that my /project/.settings/org.jboss.tools.jst.web.xml was *missing*. I copied this file from a test project called "jsfpallete" and let Eclipse injest it. I then closed Eclipse and the program added a bunch of additional libraries to the file akin to my project (JBoss Seam, IceFaces, etc.). I made a few adjustments to the file, specifically: From: <FILESYSTEMS APPLICATION_NAME="feature-pm" ENTITY="FileSystems" VERSION="2.0.0.cr1" WORKSPACE_HOME="./WebContent/WEB-INF"> To: <FILESYSTEMS APPLICATION_NAME="feature-pm" ENTITY="FileSystems" VERSION="2.0.0.cr1" WORKSPACE_HOME="./view/WEB-INF"> Because we had started our Seam project prior to JBoss Tools, we did not have the pre-designated "WebContent" directory and instead had our WEB-INF under a folder called /view. Believe it or not, this totally fixed the issue. I can now add the IceFaces TLD and get content assist *and* add XHTML and other files to the project. However, I am worried that as we check out additional projects from SVN, we are going to have to go through this same routine each time. Do you all have any thoughts on why this may have happened in the first place? Thanks for your amazing support. If you feel this is something that can be addressed via an update, please by all means do - it would certainly alleviate some confusion. -- 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-1655?page=comments#action_12397361 ] Max Andersen commented on JBIDE-1655: ------------------------------------- btw. not sure if this is something to fix in 2.0.1, i feel this might need bigger changes to handle properly. -- 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-1655?page=comments#action_12397376 ] Chris Simons commented on JBIDE-1655: ------------------------------------- Agreed, I would have rather have repaired by removing the nature but was not aware there was a way to do so. If I run into this again, which I'm pretty sure I will (again, our projects did not start with JBoss Tools), I will attempt to remove .jsf.jsfnature before modifying jst.web.xml. On another note, do you all feel this could be a culprit in other JBoss Tools project issues pertaining to projects *not* created through the IDE? I hope this experience has helped rather than caused more issues. -- 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-1655?page=comments#action_12397393 ] Viacheslav Kabanovich commented on JBIDE-1655: ---------------------------------------------- I have contributed a fix, that tests jsfnature when it is accessed. If jsfnature is corrupted because config file is missing, warning "Project P/Test has corrupted nature: org.jboss.tools.jsf.jsfnature" will be logged and jsfnature will be removed from project natures list. Seam project only may need jsfnature in order to be shown in Web Project View as JSF project, all other JBoss Tools does not need this nature. Having it removed automatically, user can add it correctly, if needed, by 'Add JSF Capabilities'. No manual accessing configuration files is needed. Max, may it be a tolerant solution for the issue in 2.0.1? -- 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-1655?page=all ] Viacheslav Kabanovich resolved JBIDE-1655. ------------------------------------------ Resolution: Done I created task JBIDE-1714. I am not sure yet that it can be safely implemented for 2.1 -- 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