[Olap4j-devel] [Mondrian] Convert Connection to OlapConnection

Julian Hyde jhyde at pentaho.com
Thu Apr 8 11:07:03 EDT 2010

Indeed! Would have been even smaller if you'd used ivy to avoid checking in
olap4j.jar and javacup.jar!


From: Luc Boudreau [mailto:lucboudreau at gmail.com] 
Sent: Thursday, April 08, 2010 7:34 AM
To: Mondrian developer mailing list; olap4j-devel at lists.sourceforge.net
Subject: Re: [Olap4j-devel] [Mondrian] Convert Connection to OlapConnection

I released mdx4j, a wrapper for olap4j's internal parser. It is under EPL so
anyone can embed it. I think I'll send a submission to the Guinness World
Records book for the smallest library ever.


Luc Boudreau

On Wed, Apr 7, 2010 at 7:54 PM, Julian Hyde <jhyde at pentaho.com> wrote:


Luc wrote: 

Julian. Discussing with Jonathan Fuerth, I came to understand your point.
Olap4j does not promote a given MDX syntax nor should it ever do. I will
start a spin-off project able to provide external code with a MdxParser that
does not require a backend server connection.

That would be great. I can think of a couple of ways to do it.
One way to do that might be to provide a dummy driver. It might be easy:
just a driver class, a connection class, and the only thing you can do with
the connection is to call getParserFactory. Can't tell without looking at
the code.
Another way would be to have a way to instantiate a default parser factory.
Say MdxParserFactory.DEFAULT.createMdxParser(null). I don't mind adding that
to the olap4j API; I just didn't want an implementation class like
DefaultMdxParserImpl to be forever part of the official API.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.pentaho.org/pipermail/mondrian/attachments/20100408/6e75ab70/attachment.html 

More information about the Mondrian mailing list