History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: RDW-2
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Severe Severe
Assignee: Michael D'Amour
Reporter: Jake Cornelius
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Pentaho Report Design WIzard - Pre-Citrus

problem using xquery in the report design wizard

Created: 09/May/07 07:48 AM   Updated: 25/Sep/07 12:30 AM
Component/s: Data Sources
Affects Version/s: Pentaho 1.2.1, Pentaho 1.2.0
Fix Version/s: Pentaho 1.6 GA

Time Tracking:
Not Specified


 Description  « Hide
This problem was reported by Alain Debecker from BPM Conseil (Alain Debecker [Alain.Debecker@bpm-conseil.com]), could we have someone look into this and provide him with a response?

Trying to test Xquery in the RDWizard, we could not do much more that standard Xpath.

The forum learned us that this issue was resolved in RStudio, up to a doc("{XML_DOCUMENT}") tag. This solution works fine on the platform, but did not work for the Designors. Not even when we copy/pasted the samples.


 All   Comments   Work Log   Change History   Transitions      Sort Order: Ascending order - Click to sort in descending order
Anthony de Shazor - 23/May/07 08:43 AM
Can you look into this issue today?

Michael D'Amour - 23/May/07 11:04 AM
doc("{XML_DOCUMENT}") not working in RDW...

Anthony de Shazor - 01/Jun/07 09:48 AM
Comment from Alain:

Thanks for your commit. Things are going better since then.

We are stumbling now on a stange error. Trying to make a report with
summary lines, we are using the recomended technique of making two
sequences in a row. The following example was tested succesfully in
saxon -- modulo the doc("{XML_DOCUMENT}")-- and the two individual
queries works fine in pentaho.

However, combining querry produces a *NumberFormatException*.

At some pointy time during the debugging, the wizard parser told us to
write "}}" instead of "}" just after the $arv1. We compiled happily to
this suggestion, but the parser answered that he found the first char of
"}}" while expecting "}}".

I joint the saxon Xquery we need, and a screenshot of the above sentence.

Michael D'Amour - 30/Aug/07 12:23 PM
Wrote to Alain asking to see if there is an update from their end. The original problem is resolved, the current problem is very specific.

Michael D'Amour - 12/Sep/07 04:25 PM
Have not heard back from customer in a few weeks, assuming the issue is closed.