aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Schneider (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (ARIES-1079) The jpa.xsd incorrectly specifies bp:map for context, or namespace handler looking for wrong namespace
Date Fri, 13 Feb 2015 09:03:11 GMT

     [ https://issues.apache.org/jira/browse/ARIES-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Christian Schneider resolved ARIES-1079.
----------------------------------------
       Resolution: Fixed
    Fix Version/s: jpa-blueprint-aries-1.0.5
         Assignee: Christian Schneider

Applied fix from [~ggerla]. Can you please test if it works for you?

> The jpa.xsd incorrectly specifies bp:map for context, or namespace handler looking for
wrong namespace
> ------------------------------------------------------------------------------------------------------
>
>                 Key: ARIES-1079
>                 URL: https://issues.apache.org/jira/browse/ARIES-1079
>             Project: Aries
>          Issue Type: Bug
>          Components: JPA
>    Affects Versions: 1.0, jpa-blueprint-aries-1.0.4
>            Reporter: Kurt Westerfeld
>            Assignee: Christian Schneider
>             Fix For: jpa-blueprint-aries-1.0.5
>
>
> The namespace handler for jpa:* constructs (ie. http://aries.apache.org/xmlns/jpa/v1.0.0
namespace), specifies that a context can be supplied with <map> of properties.  This
is defined in jpa.xsd as a blueprint map; however, when turning on schema validation, the
blueprint xml will only validate if using the jpa: prefix/namespace.
> I found NSHandler.java is looking for the blueprint namespace, which conflicts with xml
schema validation.  To fix this, either the xsd must change, or the NSHandler must change.
 My recommendation would be to change the xsd, but I'm not sure what to change it to.
> Unit tests for jpa don't include the full xsi schema validation instructions, so they
pass fine using <map> vs. <jpa:map>.  I can turn off schema validation for my
blueprint file, and use the blueprint Bundle-SymbolicName trick, but I found that interpolated
values were not being passed, so I abandoned the need.  I felt this issue should be documented,
however.
> If this is fixed, it would only be a little bit more work to make this perfect to allow
for interpolated property values in <map>.  Not sure if that is a lot of work, however.



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

Mime
View raw message