[
https://issues.apache.org/jira/browse/OAK-7533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Deparvu resolved OAK-7533.
-------------------------------
Resolution: Fixed
Fix Version/s: 1.9.4
1.10
fixed with http://svn.apache.org/viewvc?rev=1833309&view=rev
I opted for a lazy check only in the case of an error of the existing nodestate
properties (as opposed to only looking at the optimized set), made no attempt
to cache, this is a fallback and not a usual scenario. if it turns out perf is
important in this area, this decision can be revisited later.
There was also some opportunity for refactoring so I ended up removing a few
methods from the Namespaces class that seemed to not be in use.
> NameValidator is not using namespaces defined in the current transaction
> ------------------------------------------------------------------------
>
> Key: OAK-7533
> URL: https://issues.apache.org/jira/browse/OAK-7533
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Components: core
> Reporter: Alex Deparvu
> Assignee: Alex Deparvu
> Priority: Major
> Fix For: 1.10, 1.9.4
>
>
> I would like to add a fallback for the NameValidator to check the current
> transaction content in case there's namespaces it doesn't find as defined,
> before throwing an exception.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
