DO NOT REPLY [Bug 9482] New: - Problem with Pointer asPath method using dynamic beans

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9482>.
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

           Summary: Problem with Pointer asPath method using dynamic beans
           Product: Commons
           Version: 1.0 Beta 1
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Blocker
          Priority: Other
         Component: JXPath
        AssignedTo: commons-dev@jakarta.apache.org
        ReportedBy: mm@teraspect.de


Hi,

I noticed a strange behaviour of asPath, when I use dynamic beans (with
DynamicPropertyHandler).

Considering a dynamic property "properties", which contains a Vector with 5
Objects (Strings in my case), using iteratePointers (works now :-)) returns a
strange path using the asPath method on the returned pointers:

[@name='properties'][1]
[@name='properties'][2]
[@name='properties'][3]
[@name='properties'][4]
[@name='properties'][5]

This path leads (of course) to an error, when I invoke the context.getValue
method with it. I attached a testcase.

Also I noticed, that in some cases im my application the "index" begins with 2
instead of 1. But I could not reproduce this in a simple testcase. It looks like
this:

[@name='properties'][2]
[@name='properties'][3]
[@name='properties'][4]
[@name='properties'][5]

Perhaps you'll face this behaviour too.

Thanx
Markus

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>