Hide Forgot
project_key: SOA It is difficult to properly configure fedartion connector as it does not properly handle errors in configurations. Whenever there is an error in projection rules, missing sourc node etc. it just throws an exception null org.modeshape.graph.search.SearchEngineIndexer.indexSubgraph(SearchEngineIndexer.java:278) at org.modeshape.graph.search.SearchEngineIndexer.index(SearchEngineIndexer.java:229) at org.modeshape.graph.search.SearchEngineIndexer.index(SearchEngineIndexer.java:137) at org.modeshape.jcr.RepositoryQueryManager$SelfContained.reindexContent(RepositoryQueryManager.java:397) at org.modeshape.jcr.RepositoryQueryManager$SelfContained.<init>(RepositoryQueryManager.java:341) at org.modeshape.jcr.JcrRepository.<init>(JcrRepository.java:648) at org.modeshape.jcr.JcrEngine.doCreateJcrRepository(JcrEngine.java:305) at org.modeshape.jcr.JcrEngine.getRepository(JcrEngine.java:210) at org.jboss.soa.modeshape.jcr.client.RepositoryReferenceFactory.getStandaloneRepository(RepositoryReferenceFactory.java:54) at org.jboss.soa.modeshape.jcr.client.RepositoryReferenceFactory.getRepository(RepositoryReferenceFactory.java:32) at org.jboss.soa.modeshape.qa.tests.FederatedConnectorTest.createRecord(FederatedConnectorTest.java:48) 23 lines not shown The connector should validate the settings and report the error details.
This is the fix that went in on Sept 27 and didn't make it into ER2, but should be there in ER3.
Link: Added: This issue depends MODE-897
Link: Added: This issue depends SOA-2295
This fix was committed on Sept 27(see links) and didn't make it into ER2, but should be in ER3
Will verify in ER4 due to bug when errors are reported only if both warning and errors are present
Verified in ER6