Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 19675 invoked from network); 30 May 2002 02:01:48 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 30 May 2002 02:01:48 -0000 Received: (qmail 10751 invoked by uid 97); 30 May 2002 02:01:56 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 10666 invoked by uid 97); 30 May 2002 02:01:55 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 10652 invoked by uid 50); 30 May 2002 02:01:55 -0000 Date: 30 May 2002 02:01:55 -0000 Message-ID: <20020530020155.10651.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: commons-dev@jakarta.apache.org Cc: Subject: DO NOT REPLY [Bug 9482] - Problem with Pointer asPath method using dynamic beans X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9482 Problem with Pointer asPath method using dynamic beans dmitri@apache.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Additional Comments From dmitri@apache.org 2002-05-30 02:01 ------- There were two problems: one with DynamicPropertyPointer - it generated an incorrect path. Once that was fixed, I discovered another: paths generated (now correctly) by those pointers were not interpreted correctly. That problem was with the PredicateContext, which failed to treat paths like "foo[@name='bar'] [2]" correctly: instead of taking the first collection for name 'bar' and extracting the second element, it was in fact looking for a second collection named 'bar'. I could not reproduce the other issue: with iterations starting at #2. -- To unsubscribe, e-mail: For additional commands, e-mail: