[JBoss JIRA] Created: (DNA-282) Federation connector improperly handles root-level node with one projection of a non-root node from a single source
by Randall Hauch (JIRA)
Federation connector improperly handles root-level node with one projection of a non-root node from a single source
-------------------------------------------------------------------------------------------------------------------
Key: DNA-282
URL: https://jira.jboss.org/jira/browse/DNA-282
Project: DNA
Issue Type: Bug
Components: Connectors
Reporter: Randall Hauch
Assignee: Randall Hauch
Priority: Blocker
The federation connector currently has a problem when configured to project a non-root node from a single source into the root node of the federated repository. The cache always has a root node with a specific UUID, and the single source's non-root node has a different UUID, so when the federation connector attempts to project that non-root node from the source into the root node of the federated repository, the cache is unable to store the node with the UUID from the source.
This problem arose when working on DNA-281 - the test cases were changed to use the InMemory connector rather than the SimpleRepositorySource connector (used for testing only). The simple implementation didn't maintain UUIDs, whereas the in-memory implementation does. (This is one of the problems with using a "mock" or non-production implementation in tests.)
So, although the code compiles, several of the federation connector's tests fail, and the problem also affects several of the JCR unit tests and the Getting Started repository example. Therefore, after these are fixed, the corresponding projects need to be added back into the POM file.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 1 month
[JBoss JIRA] Created: (DNA-374) Multiplicity of some properties may change when saved and reloaded from the graph
by Randall Hauch (JIRA)
Multiplicity of some properties may change when saved and reloaded from the graph
---------------------------------------------------------------------------------
Key: DNA-374
URL: https://jira.jboss.org/jira/browse/DNA-374
Project: DNA
Issue Type: Bug
Components: JCR
Reporter: Randall Hauch
Assignee: Randall Hauch
Fix For: 0.4
This problem arises when a client uses the multi-valued setter methods in the JCR API to create on a node a new property with a single value, to save the node, and then to continue working with the property (again, using the multi-valued setter or getter methods). When the property is created, an appropriate multi-valued property definition will be chosen from those available on the node's primary type (and mixin types, if there are any). However, after the save, the property may node have a single-valued property definition. And since JCR does not allow a single-valued property to be changed via the multi-valued setters, the result is an exception when the client attempts to set the property using the multi-valued setters.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 1 month
[JBoss JIRA] Updated: (DNA-37) Federate schema information from relational sources
by Randall Hauch (JIRA)
[ https://jira.jboss.org/jira/browse/DNA-37?page=com.atlassian.jira.plugin.... ]
Randall Hauch updated DNA-37:
-----------------------------
Fix Version/s: 0.5
(was: 0.4)
Pushing to 0.5, since they are not critical for 0.4 and because we're approaching the end of 0.4. If the assignee thinks it can be finished before the 0.4 release, please note here and notify the team.
> Federate schema information from relational sources
> ---------------------------------------------------
>
> Key: DNA-37
> URL: https://jira.jboss.org/jira/browse/DNA-37
> Project: DNA
> Issue Type: Feature Request
> Components: Connectors
> Reporter: Randall Hauch
> Assignee: Sergiy Litsenko
> Priority: Minor
> Fix For: 0.5
>
>
> Create a connector for the federation engine that contributes and exposes the database schema information for a relational database (via JDBC) into the federated repository. This would make it possible to have a repository provide information about the databases in an organization. One choice would be whether to import (and copy) the schema structure, or to provide access to it in real time.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 1 month