[ http://jira.jboss.com/jira/browse/JBSEAM-1533?page=comments#action_12366568 ] Gavin King commented on JBSEAM-1533: ------------------------------------ Um, thats not very helpful. Exactly what is wrong in 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/JBSEAM-1533?page=comments#action_12366572 ] Dan Allen commented on JBSEAM-1533: ----------------------------------- Gavin, I may be able to provide some insight here. First of all, the web.xml file does validate. The following command proves it. xmllint --noout --schema http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd web.xml web.xml validates What I have seen though, is that Eclipse WTP (if the seam-gen project is setup that way by a user) that NONE is not a valid role as a security constraint. This role is not needed because the lack of a role indicates no permissions. So the following stanza would do just fine. <security-constraint> <display-name>Restrict raw XHTML Documents</display-name> <web-resource-collection> <web-resource-name>XHTML</web-resource-name> <url-pattern>*.xhtml</url-pattern> </web-resource-collection> </security-constraint> The only other possibility is that the project name that Mikhail chose was not valid within the context of an xml file. However, other patch of mine already suggests that we do some filtering on the name of the project before using it everywhere. My vote is to close this issue, unless you feel that taking out the role-name NONE. -- 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/JBSEAM-1533?page=comments#action_12366585 ] Mikhail Grushinskiy commented on JBSEAM-1533: --------------------------------------------- It is too easy to mess up web.xml. Maybe ant task which validates all web.xml files against xsd across all seam CVS code would help. I've seen error in Exadel Studio which marked some of the as invalid per XSD. Unfortunately I got rid of it and I do not remember exactly which ones was it. I guess ant task validating all web.xml in Seam srource snapshot would be very useful since it will do the check repeatedly. -- 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/JBSEAM-1533?page=comments#action_12366593 ] Mikhail Grushinskiy commented on JBSEAM-1533: --------------------------------------------- Dan, thanks for compliment about xmlstarlet ( I wrote xmlstarlet :) ), but I think you need some Java validator integrated within ant script. It should be used for all xml files in Seam project which have dtd or xsd defined. This will help to avoid such bug reports in future as these errors will be discovered at build time. -- 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/JBSEAM-1533?page=all ] Pete Muir closed JBSEAM-1533. ----------------------------- Resolution: Duplicate Issue Closing, other issue is more descriptive -- 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