[ https://issues.apache.org/jira/browse/ARIES-1600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schneider resolved ARIES-1600.
----------------------------------------
Resolution: Fixed
I already fixed this but unfortunately put it into the wrong commit. So the message is misleading.
https://github.com/apache/aries/commit/11515bd4178ecbab68285ad4959199785315e838
Basically the NamespaceHandler should not throw an exception when it is given a wrong namespace
but rather return null.
So this should work in jpa-2.5.0. Can you check if it works there?
> '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)