Bug 780018 (SOA-2379)

Summary: Offset projection in federation connector does not work for non-root source paths
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: Jiri Pechanec <jpechane>
Component: EDSAssignee: Van Halbert <vhalbert>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: urgent Docs Contact:
Priority: urgent    
Version: 5.1.0.ER2CC: rhauch
Target Milestone: ---   
Target Release: 5.2.0.ER2   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-2379
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-10-21 11:24:18 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
modeshape-config.xml
none
FederatedConnectorTest.java none

Description Jiri Pechanec 2010-10-06 10:26:53 UTC
project_key: SOA

The federation connector is configured to use the following projection rule
<mode:projectionRules>/source1 => /a</mode:projectionRules>

The source repository content is
   [testng] Retrieving standalone repository ...
   [testng] /a {jcr:primaryType=nt:unstructured, }
   [testng]     /a/b {jcr:primaryType=nt:unstructured, }
   [testng] /jcr:system {jcr:primaryType=mode:system, }

If I try to access federated repository I get
Unable to find "/{}a"; lowest existing path is "/"
org.modeshape.graph.connector.federation.JoinRequestProcessor.setPathNotFound(JoinRequestProcessor.java:400) 
at org.modeshape.graph.connector.federation.JoinRequestProcessor.process(JoinRequestProcessor.java:333) 
at org.modeshape.graph.request.processor.RequestProcessor.process(RequestProcessor.java:284) 
at org.modeshape.graph.connector.federation.JoinRequestProcessor.process(JoinRequestProcessor.java:196) 
at org.modeshape.graph.connector.federation.JoinRequestProcessor.process(JoinRequestProcessor.java:144) 
at org.modeshape.graph.connector.federation.FederatedRepositoryConnection.execute(FederatedRepositoryConnection.java:225) 
at org.modeshape.graph.connector.RepositoryConnectionPool$ConnectionWrapper.execute(RepositoryConnectionPool.java:1129) 
at org.modeshape.graph.request.CompositeRequestChannel$2.call(CompositeRequestChannel.java:193) 
at org.modeshape.graph.request.CompositeRequestChannel$2.call(CompositeRequestChannel.java:183) 
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) 
at java.util.concurrent.FutureTask.run(FutureTask.java:138) 
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) 
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) 
at java.lang.Thread.run(Thread.java:619) 
1 lines not shown 

If projection rule is changed to
<mode:projectionRules>/source1 => /</mode:projectionRules>

Then the federated repository correctly displays content as
   [testng] Retrieving standalone repository ...
   [testng] /source1 {jcr:primaryType=nt:unstructured, }
   [testng]     /source1/a {jcr:primaryType=nt:unstructured, }
   [testng]         /source1/a/b {jcr:primaryType=nt:unstructured, }
   [testng] /jcr:system {jcr:primaryType=mode:system, }

Comment 1 Jiri Pechanec 2010-10-06 11:58:41 UTC
Attachment: Added: modeshape-config.xml
Attachment: Added: FederatedConnectorTest.java


Comment 2 Van Halbert 2010-10-06 14:51:08 UTC
Link: Added: This issue depends MODE-931


Comment 3 Van Halbert 2010-10-06 18:39:00 UTC
ModeShape has committed the fix and should be in ER3.

Comment 4 Jiri Pechanec 2010-10-20 07:09:40 UTC
The issue is still present in ER3

Comment 7 Dana Mison 2011-01-05 00:08:23 UTC
Writer: Added: Darrin


Comment 8 Randall Hauch 2011-01-12 14:13:39 UTC
ModeShape does not utilize this feature in SOA-P or BRMS, so this does not cause a problem for the way our products are used out of the box. However, it is possible that a customers might choose to use JCR in a custom way and run into this. At this time, they'll have to live with this limitation.



Comment 9 Randall Hauch 2011-01-12 14:15:48 UTC
Release Notes Text: Added: It is a known issue that projection rules such as "/source1 => /a" will not work at this time. Other production rules do work, including "/source1 => /".


Comment 10 Van Halbert 2011-06-29 18:26:17 UTC
ModeShape has targeted this as critical to be fixed in 2.5 for the product.  

Comment 12 Jiri Pechanec 2011-10-21 11:24:18 UTC
Verified in ER5