<div dir="ltr">Hello again,<br><br>Nevermind that. I got the source from the distribution instead of directly from perforce and now it works.<br><br>But now, I confirmed that there were some changes in this release that affects the Olap4j test suite. The Mondrian Olap4j driver throws MondrianException where an OlapException is expected by the API. This happens in Olap4j's ConnectionTest.testValidateError, line 1787. It waits for an OlapException but gets a MondrianException instead. Since MondrianException is a subclass of RuntimeException, it gets through all Olap4jMondrianDriver error handling facilities right back to the end-user. This is a no-no and an infringement of the current Olap4j API.<br>
<br>The violation exact point is in MondrianOlap4jonnection.validateSelect(), line 614. The method signature says it throws only OlapExceptions, but as I said before, the call to parseQuery() at line 614 triggers a subclass of RuntimeException to be thrown, thus violating the API.<br>
<br>This is reproductible with Mondrian 3.0.4 and Olap4j head or whatever recision you want as a matter of fact. <br><br>Luc<br><br><br><br><br><div class="gmail_quote">On Mon, Oct 6, 2008 at 11:59 AM, Luc Boudreau <span dir="ltr"><<a href="mailto:lucboudreau@gmail.com">lucboudreau@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div dir="ltr"><br>Hello,<br><br>I'm trying to build Mondrian changeset 3.0.4.11371 from source but i get "ParserSym.BANG cannot be resolved" in mondrian-3.0/src/main/mondrian/olap/Scanner.java, line 721.<br>
<br>Since this file is generated at build time, i'm asking the developer's list. What did I do wrong?! Howcome it didn't get generated properly? What are the workarrounds?<br><br clear="all"><br>-- <br>_____________________________<br>
Luc Boudreau<br>
</div>
</blockquote></div><br><br clear="all"><br>-- <br>_____________________________<br>Luc Boudreau<br>
</div>