9:09 a.m.
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)
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
9:13 a.m.
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:
Actually, I'm misreading hudson. "Age=6" is not 6 days but
6 builds. The breakage was a little under 3 days ago. :-)
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
9:38 a.m.
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)
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
11:28 a.m.
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=138414
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)
1:25 p.m.
New subject: Recent large regression in the testsuite - SECURITY-260 and jboss-metadata-1.0.0.Beta28
This was a mistake on my part. I was obviously not supposed to commit
the metadata changes before a new release of jbosssx (think my brain was
in auto-commit mode). Anyway, your workaround does the trick for now and
as soon as we have a jbosssx release I'll perform the proper cleanup on AS.
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)
>
>
6001
days inactive
6001
days old
jboss-development@lists.jboss.org
4 comments
3 participants
participants (3)
-
Adrian Brock -
Anil Saldhana -
Stefan N. Guilhen