[ 
https://issues.apache.org/jira/browse/ARIES-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419026#comment-15419026
 ] 

Niten Aggarwal commented on ARIES-1593:
---------------------------------------

Hi,

I know there is another similar issue 
https://issues.apache.org/jira/browse/ARIES-1540 like this one which is fixed 
in 1.6.2. 

Could you please let me know how to apply this fix in Karaf 4.0.5 as we are 
facing same issue and cannot change aries blueprint version just by changing 
features.xml. We are on karaf 4.0.5 and feature will be installed through nexus 
repository directly so we cannot update this feature just for blueprint.core 
version.

<feature name="aries-blueprint" description="Aries Blueprint" version="4.0.5">
 <feature prerequisite="false" dependency="false">aries-proxy</feature>
 <bundle 
start-level="20">mvn:org.apache.aries.blueprint/org.apache.aries.blueprint.api/1.0.1</bundle>
 <bundle 
start-level="20">mvn:org.apache.aries.blueprint/org.apache.aries.blueprint.cm/1.0.8</bundle>
 <bundle 
start-level="20">mvn:org.apache.aries.blueprint/org.apache.aries.blueprint.core.compatibility/1.0.0</bundle>
 <bundle 
start-level="20">mvn:org.apache.aries.blueprint/org.apache.aries.blueprint.core/1.6.1</bundle>
 <conditional>
 <condition>bundle</condition>
 <bundle 
start-level="30">mvn:org.apache.karaf.bundle/org.apache.karaf.bundle.blueprintstate/4.0.5</bundle>
 </conditional>
 <capability>
 
osgi.service;effective:=active;objectClass=org.apache.aries.blueprint.services.ParserService,
 osgi.extender; 
osgi.extender="osgi.blueprint";uses:="org.osgi.service.blueprint.container,org.osgi.service.blueprint.reflect";version:Version="1.0"
 </capability>
 </feature>


> Blueprint NamespaceHandler can't resolve XSD in offline mode
> ------------------------------------------------------------
>
>                 Key: ARIES-1593
>                 URL: https://issues.apache.org/jira/browse/ARIES-1593
>             Project: Aries
>          Issue Type: Bug
>          Components: Blueprint
>    Affects Versions: blueprint-core-1.6.1
>            Reporter: Niten Aggarwal
>
> When the NamespaceHandler is offline, it fails to resolve the XSD:
> 1.6.1 | Unable to start blueprint container for bundle 
> org.talend.esb.job.controller/6.2.0.SNAPSHOT
> org.xml.sax.SAXParseException: src-resolve: Cannot resolve the name 
> 'ptp:ParameterizedInt' to a(n) 'simpleType definition' component.
>     at 
> org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown 
> Source)[:]
>     at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)[:]
>     at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)[:]
>     at 
> org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(Unknown 
> Source)[:]
>     at 
> org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(Unknown 
> Source)[:]
>     at 
> org.apache.xerces.impl.xs.traversers.XSDAbstractTraverser.reportSchemaError(Unknown
>  Source)[:]
>     at 
> org.apache.xerces.impl.xs.traversers.XSDAttributeTraverser.traverseNamedAttr(Unknown
>  Source)[:]
>     at 
> org.apache.xerces.impl.xs.traversers.XSDAttributeTraverser.traverseLocal(Unknown
>  Source)[:]
>     at 
> org.apache.xerces.impl.xs.traversers.XSDAbstractTraverser.traverseAttrsAndAttrGrps(Unknown
>  Source)[:]
>     at 
> org.apache.xerces.impl.xs.traversers.XSDComplexTypeTraverser.processComplexContent(Unknown
>  Source)[:]
>     at 
> org.apache.xerces.impl.xs.traversers.XSDComplexTypeTraverser.traverseComplexTypeDecl(Unknown
>  Source)[:]
>     at 
> org.apache.xerces.impl.xs.traversers.XSDComplexTypeTraverser.traverseLocal(Unknown
>  Source)[:]
>     at 
> org.apache.xerces.impl.xs.traversers.XSDElementTraverser.traverseNamedElement(Unknown
>  Source)[:]
>     at 
> org.apache.xerces.impl.xs.traversers.XSDElementTraverser.traverseGlobal(Unknown
>  Source)[:]
>     at 
> org.apache.xerces.impl.xs.traversers.XSDHandler.traverseSchemas(Unknown 
> Source)[:]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to