Uploaded image for project: 'ModeShape'
  1. ModeShape
  2. MODE-1473

Second property is ignored in org.modeshape.jcr.query.qom.JcrQueryObjectModelFactory.equiJoinCondition(String, String, String, String)

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 2.8.2.Final, 3.0.0.Alpha4
    • 2.8.1.Final
    • Query
    • None

      There is a bug in the method org.modeshape.jcr.query.qom.JcrQueryObjectModelFactory.equiJoinCondition(String, String, String, String):

      public EquiJoinCondition equiJoinCondition( String selector1Name,
                                            String property1Name,
                                            String selector2Name,
                                            String property2Name ) {
    CheckArg.isNotNull(selector1Name, "selector1Name");
    CheckArg.isNotNull(property1Name, "property1Name");
    CheckArg.isNotNull(selector2Name, "selector2Name");
    CheckArg.isNotNull(selector2Name, "selector2Name");
    return new JcrEquiJoinCondition(selectorName(selector1Name), property1Name, selectorName(selector2Name), selector2Name);
}

      where selector2Name is used as the 4th parameter to the JcrEquiJoinCondition constructor, but should be property2Name.

            hchiorean Horia Chiorean (Inactive)
            dimonv_jira Dmitri Voronov (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: