>(am interested to know where the Crimson parser is being picked up from)?
That was it! Thank you very much for your help. -----Original Message----- From: Simon Laws [mailto:[email protected]] Sent: Tuesday, January 10, 2012 1:52 AM To: [email protected] Subject: Re: Schema loading problem On Tue, Jan 10, 2012 at 9:08 AM, Kallen McInerney <[email protected]> wrote: > Hi new to Tuscany here. During startup of Tuscany I sometimes get the > exception below which I tracked down to the following unreachable URL > > > > www.w3.org/2001/xml.xsd > > > > I am able to work around it using the solution in TUSCANY-2979 but I take it > this disables validation of my composite files. Is there a way to keep > validation working? Can I somehow override with a local version of the file > xml.xsd? > > > > https://issues.apache.org/jira/browse/TUSCANY-2979 > > > > > > Thanks in advance. > > > > Jan 9, 2012 11:59:55 PM org.apache.tuscany.sca.impl.NodeImpl <init> > > INFO: domain: shop-services > > Jan 10, 2012 12:01:30 AM org.apache.tuscany.sca.impl.NodeImpl > installContribution > > INFO: installContribution: services > > org.apache.tuscany.sca.runtime.ActivationException: > org.apache.tuscany.sca.assembly.builder.CompositeBuilderException: Exception > while building model {http://docs.oasis-open.org/ns/opencsa/sca/200912} > > at > org.apache.tuscany.sca.impl.DeployedComposite.<init>(DeployedComposite.java:85) > > at > org.apache.tuscany.sca.impl.NodeImpl.startComposite(NodeImpl.java:331) > > at > org.apache.tuscany.sca.impl.NodeImpl.startDeployables(NodeImpl.java:487) > > > > Caused by: > org.apache.tuscany.sca.assembly.builder.CompositeBuilderException: Exception > while building model {http://docs.oasis-open.org/ns/opencsa/sca/200912} > > at > org.apache.tuscany.sca.builder.impl.ModelBuilderImpl.build(ModelBuilderImpl.java:144) > > at > org.apache.tuscany.sca.assembly.builder.DefaultBuilderExtensionPoint$LazyCompositeBuilder.build(DefaultBuilderExtensionPoint.java:256) > > at > org.apache.tuscany.sca.deployment.impl.DeployerImpl.build(DeployerImpl.java:593) > > at > org.apache.tuscany.sca.deployment.impl.DeployerImpl.build(DeployerImpl.java:500) > > at > org.apache.tuscany.sca.impl.DeployedComposite.build(DeployedComposite.java:102) > > at > org.apache.tuscany.sca.impl.DeployedComposite.<init>(DeployedComposite.java:81) > > ... 20 more > > Caused by: > org.apache.tuscany.sca.assembly.builder.CompositeBuilderException: > java.lang.UnsupportedOperationException: This DocumentBuilder, > "org.apache.crimson.jaxp.DocumentBuilderImpl", does not support the reset > functionality. Specification "null" version "null" > > at > org.apache.tuscany.sca.builder.impl.PolicyAppliesToBuilderImpl.build(PolicyAppliesToBuilderImpl.java:93) > > at > org.apache.tuscany.sca.builder.impl.CompositePolicyBuilderImpl.checkPolicies(CompositePolicyBuilderImpl.java:396) > > at > org.apache.tuscany.sca.builder.impl.CompositePolicyBuilderImpl.build(CompositePolicyBuilderImpl.java:73) > > at > org.apache.tuscany.sca.builder.impl.ModelBuilderImpl.build(ModelBuilderImpl.java:135) > > ... 25 more > > Caused by: java.lang.UnsupportedOperationException: This DocumentBuilder, > "org.apache.crimson.jaxp.DocumentBuilderImpl", does not support the reset > functionality. Specification "null" version "null" > > at > javax.xml.parsers.DocumentBuilder.reset(DocumentBuilder.java:92) > > at > org.apache.tuscany.sca.common.xml.dom.DOMHelper$1.resetInstance(DOMHelper.java:278) > > at > org.apache.tuscany.sca.common.xml.dom.DOMHelper$1.resetInstance(DOMHelper.java:269) > > at > org.apache.tuscany.sca.common.xml.dom.ParserPool.returnToPool(ParserPool.java:64) > > at > org.apache.tuscany.sca.common.xml.dom.DOMHelper.returnDocumentBuilder(DOMHelper.java:106) > > at > org.apache.tuscany.sca.common.xml.dom.DOMHelper.load(DOMHelper.java:123) > > at > org.apache.tuscany.sca.builder.impl.PolicyAttachmentBuilderImpl.saveAsDOM(PolicyAttachmentBuilderImpl.java:244) > > at > org.apache.tuscany.sca.builder.impl.PolicyAppliesToBuilderImpl.build(PolicyAppliesToBuilderImpl.java:82) > > ... 28 more > > > > Kallen McInerney > Principal Engineer > > Email: [email protected] > > Phone: (831) 531-4811 > > Skype: kallen.mcinerney > > > > SHOP.COMTM > A Market America Company > > > > Shop Smart, Save BigT > www.shop.com > > Join us on Facebook. > Follow us on Twitter. > > Read The Shopping Vine. > > > > Hi Kallen What version of Tuscany were you running (from the stack it looks like 2. something)? What's the environment you're running it in (am interested to know where the Crimson parser is being picked up from)? In 2.x we do ship a local version of xml.xsd here [1] which our schema locator should be picking up but maybe there is a bug or some environment/configuration that means it's not being picked in your case. Looking at the stack the code is trying to reading in a string version of the domain composite in order to create a DOM and apply policy XPath statements. Given the stack you have what lead you to the conclusion about xml.xsd? [1] http://svn.apache.org/repos/asf/tuscany/sca-java-2.x/trunk/modules/assembly-xsd/src/main/resources/org/apache/tuscany/sca/assembly/xsd/ Regards Simon -- Apache Tuscany committer: tuscany.apache.org Co-author of a book about Tuscany and SCA: tuscanyinaction.com
