If I use the CatalogResolver from this article in place of the current MetaDataEntityResolver:
package org.jboss.xml.binding;
import org.apache.xml.resolver.tools.CatalogResolver;
public class Unmarshaller
{
...
entityResolver = new CatalogResolver(); //MetaDataEntityResolver(null);
the server starts up fine. We need to update our entity resolution to
either use the CatalogResolver or do the same things it does. CatalogResolver
is in the xerces resolver.jar.
xxxxxxxxxxxxxxxxxxxxxxxx
Scott Stark
Chief Technology Officer
JBoss Group, LLC
xxxxxxxxxxxxxxxxxxxxxxxx
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Scott M Stark
> Sent: Tuesday, March 30, 2004 5:58 PM
> To: [EMAIL PROTECTED]
> Subject: RE: [JBoss-dev] Seeing sporadic failures in the
> headjboss-local-jdbc.rar deployment
>
> Also,
> http://www.xml.com/lpt/a/2004/03/03/catalogs.html
>
> xxxxxxxxxxxxxxxxxxxxxxxx
> Scott Stark
> Chief Technology Officer
> JBoss Group, LLC
> xxxxxxxxxxxxxxxxxxxxxxxx
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED] On Behalf Of
> > Adrian Brock
> > Sent: Tuesday, March 30, 2004 2:25 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: [JBoss-dev] Seeing sporadic failures in the
> > headjboss-local-jdbc.rar deployment
> >
> > Try again from cvs. At least the j2ee1.4 and connector schemas were
> > old.
> > I also put a hack in the entity resolver to cater for schema
> > includes. Does anybody know how you are supposed to do this
> properly?
> > It seems to want to find the xsds in the same place it got the
> > original xml document rather than relative to the xsd that does the
> > include?
> >
> > Regards,
> > Adrian
>
smime.p7s
Description: S/MIME cryptographic signature
