[dna-issues] [JBoss JIRA] Resolved: (DNA-449) Federation connector does not find it's configuration when imported using the JcrConfiguration
[
https://jira.jboss.org/jira/browse/DNA-449?page=com.atlassian.jira.plugin...
]
Randall Hauch resolved DNA-449.
-------------------------------
Resolution: Done
Corrected a number of issues with the federated connector. One particularly nasty problem
(and the last to be fixed) was the connector's join operations were fully awaiting
until all the forking operations were completed before they were each joined. The
blocking queue was turned off, but this was causing most of the concurrency issues.
Marking this issue as resolved.
Federation connector does not find it's configuration when
imported using the JcrConfiguration
----------------------------------------------------------------------------------------------
Key: DNA-449
URL: https://jira.jboss.org/jira/browse/DNA-449
Project: DNA
Issue Type: Bug
Components: API, Connectors
Affects Versions: 0.4
Reporter: Randall Hauch
Assignee: Randall Hauch
Priority: Blocker
Fix For: 0.5
When a configuration file is imported using the JcrConfiguration (or DnaConfiguration),
the Federation Connector doesn't find the connector's workspace definitions. I
believe this is because the configuration files are imported with slightly modified paths.
This problem prevents the federation connector from being used, and thus is a bigger
problem.
Fixing this should be pretty straightforward and is low risk, and simply involves
supplying the correct path to the source configuration element when the
RepositorySource's are initialized by the RepositoryLibrary, then changing the
FederatedRepositorySource to use this new path.
--
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