[daisy] [JIRA] Closed: (DSY-440) navigation query node with nested body resolves context-values wrong

[Marc Portier (JIRA)]

     [ http://issues.cocoondev.org//browse/DSY-440?page=all ]
     
Marc Portier closed DSY-440:
----------------------------

    Fix Version: public - 2.0.1
     Resolution: Fixed

fix committed in revision 3921
http://svn.cocoondev.org/viewsvn?rev=3921&view=rev

> navigation query node with nested body resolves context-values wrong
> --------------------------------------------------------------------
>
>          Key: DSY-440
>          URL: http://issues.cocoondev.org//browse/DSY-440
>      Project: Daisy
>         Type: Bug
>   Components: Navigation
>     Versions: public - 2.0
>     Reporter: Marc Portier
>      Fix For: public - 2.0.1
>  Attachments: DSY-440-patch.txt
>
> As reported by Alan Mortensen on the list:
> http://lists.cocoondev.org/pipermail/daisy/2007-April/006269.html
> a nested query referencing ${1}, ${documentId}, ... inserts some strange toString version of 'org.outerj.daisy.navigation.impl.ContextValue' into the statement, it should however insert the actual values contained in those objects.
> A fast first checkup of the ContextResolver code shows that for dates and links the value.getValue() is formatted, while in the default case the toString is directly called on the value object.
> Just changing that seems to enable most of the suggested nested query statements.
> A patch will be provided. Some extra testing might be due though.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.cocoondev.org//secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira