[jira] Commented: (JCR-616) Completeness/Freshness of Namespace Registry

[ http://issues.apache.org/jira/browse/JCR-616?page=comments#action_12451306 ] angela commented on JCR-616: i committed the patch with some modifications as a short term solution. form my point of view, the patch addresses the problem only partially

[jira] Commented: (JCR-616) Completeness/Freshness of Namespace Registry

[ http://issues.apache.org/jira/browse/JCR-616?page=comments#action_12449676 ] Julian Reschke commented on JCR-616: OK. I have a prototype running which at least fixes the problem for me. Changes: 1) NamespaceStorage: add method "getRegis

[jira] Commented: (JCR-616) Completeness/Freshness of Namespace Registry

[ http://issues.apache.org/jira/browse/JCR-616?page=comments#action_12446946 ] angela commented on JCR-616: > 1) Clarify that the Map returned from getRegisteredNamespaces() isn't > required to > be complete, i'm not totally happy with this. getR

[jira] Commented: (JCR-616) Completeness/Freshness of Namespace Registry

[ http://issues.apache.org/jira/browse/JCR-616?page=comments#action_12446945 ] Marcel Reutegger commented on JCR-616: -- I would require that only those mappings must be available, that went through the RepositoryService. Not all, just the on

[jira] Commented: (JCR-616) Completeness/Freshness of Namespace Registry

[ http://issues.apache.org/jira/browse/JCR-616?page=comments#action_12446931 ] Julian Reschke commented on JCR-616: One problem with approach 4) is that in some backend systems, users can set arbitrary custom properties. That is, there is no

[jira] Commented: (JCR-616) Completeness/Freshness of Namespace Registry

[ http://issues.apache.org/jira/browse/JCR-616?page=comments#action_12446926 ] Marcel Reutegger commented on JCR-616: -- 1) Allow the SPI to return the prefix as an optional part of a QName when using a namespace that the client has not yet s

[jira] Commented: (JCR-616) Completeness/Freshness of Namespace Registry

[ http://issues.apache.org/jira/browse/JCR-616?page=comments#action_12446916 ] Julian Reschke commented on JCR-616: I like 1) alot (in fact I was going to suggest something like this myself...), but 2 and 3 would work well for me as well. I

[jira] Commented: (JCR-616) Completeness/Freshness of Namespace Registry

[ http://issues.apache.org/jira/browse/JCR-616?page=comments#action_12446913 ] Jukka Zitting commented on JCR-616: --- I think that instead of (or before) auto-generating a prefix for an unknown namespace the jcr2spi should ask the backend for a

[jira] Commented: (JCR-616) Completeness/Freshness of Namespace Registry

[ http://issues.apache.org/jira/browse/JCR-616?page=comments#action_12446896 ] Marcel Reutegger commented on JCR-616: -- Namespace prefixes cannot be just generated, because there is a notion of a repository wide namespace registry with a som

[jira] Commented: (JCR-616) Completeness/Freshness of Namespace Registry

[ http://issues.apache.org/jira/browse/JCR-616?page=comments#action_12446882 ] angela commented on JCR-616: RepositoryConfig.getRegisteredNamespaces()? there is not RepositoryConfig in the SPI and the one contained in jcr2spi doesn't have the menti