[
https://issues.apache.org/jira/browse/ARIES-1600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15683960#comment-15683960
]
Panos Kavalagios commented on ARIES-1600:
-----------------------------------------
Tested successfully on Apache Karaf version 4.0.6 with the following:
{code:none}
bundle:uninstall org.apache.aries.jpa.blueprint
bundle:install -s mvn:org.apache.aries.jpa/org.apache.aries.jpa.blueprint/2.5.0
{code}
the list command displays:
{code:none}
START LEVEL 100 , List Threshold: 50
ID | State | Lvl | Version | Name
134 | Active | 80 | 2.5.0 | Apache Aries JPA blueprint
{code}
the exception is not reported.
> 'Unknown namespace for jpa' in JpaNsHandler
> -------------------------------------------
>
> Key: ARIES-1600
> URL: https://issues.apache.org/jira/browse/ARIES-1600
> Project: Aries
> Issue Type: Bug
> Components: JPA
> Affects Versions: jpa-2.4.0
> Reporter: Rafael Bedia
> Assignee: Christian Schneider
> Fix For: jpa-2.5.0
>
> Attachments: unknown-namespace-error.txt
>
>
> The IllegalArgumentException "Unknown namespace for jpa: " is being triggered
> in org.apache.aries.jpa.blueprint.impl.JpaNsHandler.getSchemaLocation.
> The bundle I am deploying has several extension namespaces defined in the
> Blueprint XML. I don't have a minimal example that exhibits this problem but
> I might be able to create one if necessary.
> I'm not sure why the JpaNsHandler is being passed a namespace that it can't
> handle. However all other implementations of NamespaceHandler that I have
> seen return null if they are passed a namespace they do not recognize. When I
> replaced the IllegalArgumentException with returning null the bundle
> successfully started.
> This is related to ARIES-1403.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
