That is the source of the problem.
The metadata xsd removal and jbosssx release had to be synchronized,
which has not happened. I am told that it was an accidental removal in
the metadata project.
Adrian Brock wrote:
I've done a temporary workaround for this issue,
but it needs fixing properly:
http://jira.jboss.com/jira/browse/JBAS-5767
On Mon, 2008-07-14 at 16:09 +0200, Adrian Brock wrote:
> There's a large number of tests that started failing A WEEK AGO
> due to the following two changes:
>
> Removal of security xsds from the jboss-metadata project
>
http://viewvc.jboss.org/cgi-bin/viewvc.cgi/jbossas?view=rev&revision=...
> to jbosssx
http://jira.jboss.com/jira/browse/SECURITY-260
>
> Upgrade of jboss-metadata in trunk
>
http://viewvc.jboss.org/cgi-bin/viewvc.cgi/jbossas?view=rev&revision=...
>
> So a lot of tests are failing because the xsds are no longer
> in any of the jars:
>
> Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Failed to
> resolve schema nsURI=urn:jboss:security-config:5.0
> location=resource:security-config_5_0.xsd
> at
>
org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:309)
> at org.jboss.xb.binding.parser.sax.SaxJBossXBParser
> $DelegatingContentHandler.startElement(SaxJBossXBParser.java:401)