[ https://jira.jboss.org/jira/browse/JBIDE-4469?page=com.atlassian.jira.plu... ] Jeff Wexler updated JBIDE-4469: ------------------------------- Description: On Windows Server 2003, using a project name with a period often causes issues. For example, to easily illustrate: Jboss AS stopped. ant explode booking example (using ds configured to Postgresql in my case). Rename ear to com.mysite.ear Rename jar to com.mysite.jar Rename war to com.mysite.war Update application.xml with the changes. Change com.mysite.war\WEB-INF\components.xml such that jndi-pattern changed to "com.mysite/#{ejbName}/local" Change com.mysite.jar\META-INF\persistence.xml such that jta-data-source changed to java:/com.mysiteDatasource Rename jboss-seam-booking-ds.xml to com.mysite-ds.xml Change com.mysite-ds.xml such that jndi-name changed to com.mysiteDatasource Then start Jboss default server, get deploy errors. Stop JBoss AS. Then make all the above changes but without the period in the file names and values such that commysite is used instead. Then start JBoss AS, it works. If stop JBoss AS, and change them all back to with the period again such that com.mysite again. Then will not work. If change back to commysite again without the period works again. I've verified this several times in somewhat amazement. Note: I just attempted again with the period and this time it worked. Strange. I say somewhat because period in folder names within c:\Inetpub\wwwroot also causes issues with IIS and thus is clearly a Microsoft problem. If initially create a seam web project using JBoss tools with a period, it WILL work. However, after starting to use the project and make changes (i.e., simple stuff which should not cause issues), re-build, etc. eventually, get the strange errors as in the case above. I recomend some kind of warning or other message or means to warn users using Windows to avoid including periods in the project names. It would save some people a lot of wasted time. I would also suggest adding a comment in an appropriate location in the related reference documents (Seam Tools and perhaps Seam Reference doc). was: On Windows Server 2003, using a project name with a period often causes issues. For example, to easily illustrate: Jboss AS stopped. ant explode booking example (using ds configured to Postgresql in my case). Rename ear to com.mysite.ear Rename jar to com.mysite.jar Rename war to com.mysite.war Update application.xml with the changes. Change com.mysite.war\WEB-INF\components.xml such that jndi-pattern changed to "com.mysite/#{ejbName}/local" Change com.mysite.jar\META-INF\persistence.xml such that jta-data-source changed to java:/com.mysiteDatasource Rename jboss-seam-booking-ds.xml to com.mysite-ds.xml Change com.mysite-ds.xml such that jndi-name changed to com.mysiteDatasource Then start Jboss default server, get deploy errors. Stop JBoss AS. Then make all the above changes but without the period in the file names and values such that commysite is used instead. Then start JBoss AS, it works. I just attempted again with the period and this time it worked. Strange. If stop JBoss AS, and change them all back to with the period again such that com.mysite again. Then will not work. If change back to commysite again without the period works again. I've verified this several times in somewhat amazement. I say somewhat because period in folder names within c:\Inetpub\wwwroot also causes issues with IIS and thus is clearly a Microsoft problem. If initially create a seam web project using JBoss tools with a period, it WILL work. However, after starting to use the project and make changes (i.e., simple stuff which should not cause issues), re-build, etc. eventually, get the strange errors as in the case above. I recomend some kind of warning or other message or means to warn users using Windows to avoid including periods in the project names. It would save some people a lot of wasted time. I would also suggest adding a comment in an appropriate location in the related reference documents (Seam Tools and perhaps Seam Reference doc). -- 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