Mailing-List: contact dev-help@myfaces.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "MyFaces Development" <dev@myfaces.apache.org>
Date: Tue, 8 Aug 2017 15:17:00 +0000 (UTC)
From: "Eduardo Breijo (JIRA)" <dev@myfaces.apache.org>
To: dev@myfaces.apache.org
Message-ID: <JIRA.13093203.1502205401000.118057.1502205420485@Atlassian.JIRA>
In-Reply-To: <JIRA.13093203.1502205401000@Atlassian.JIRA>
References: <JIRA.13093203.1502205401000@Atlassian.JIRA> <JIRA.13093203.1502205401057@jira-lw-us.apache.org>
Subject: [jira] [Created] (MYFACES-4132) Search expression doesn't work as
 expected when expression is id:keyword
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 08 Aug 2017 15:17:09 -0000

Eduardo Breijo created MYFACES-4132:
---------------------------------------

             Summary: Search expression doesn't work as expected when expression is id:keyword
                 Key: MYFACES-4132
                 URL: https://issues.apache.org/jira/browse/MYFACES-4132
             Project: MyFaces Core
          Issue Type: Bug
    Affects Versions: 2.3.0-beta
            Reporter: Eduardo Breijo


When a component search is done using an expression of this type "id:keyword", the resolved id is unexpected. 

I have provided a test app:
1) Deploy the app on tomcat
2) Drive a request: http://localhost:8080/ComponentSearchExpression/index.xhtml
3) When you check this response message: "TEST resolveComponent with search expression 'form1:@parent' -> form1" we should expect that the expression "form1:@parent" resolves to "body" and not "form1".
4) Another example in that same test: Check the page source and look for "Body Child(1)", the search expression used is "body:@child(1)" and this should resolve to "form1" but instead it is resolving to "body"


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)