[Mondrian] MondrianServer - getting all connections

[Paul Stoellberger]

Hi,

I'm using a similar approach to the XmlServlet to load up mondrian/olap4j.
Now my question is, once i created the MondrianServer, how can i retrieve all connections?

i thought i could use the catalognames etc. as a wildcard but it seems like thats failing.

(A loop until con is null)
con = server.getConnection(null, null, null);
.... (add it to the list of connections)

-Paul
_______________________________________________
Mondrian mailing list
Mondrian (AT) pentaho (DOT) org
http://lists.pentaho.org/mailman/listinfo/mondrian

[Paul Stoellberger]

Just a quick update

The problem was that Util.readVirtualFile() was called 3 times for a catalog
2 times the CatalogLocator replaced the "solution:" VFS prefix with the solution repository path (yeah thats in the biserver) .... so i get file:/user/tmp/file.xml
but the last time it didn't, and thats when i got the error ... the path still looks like : solution:biserver/steelwheels/asdf.xml

I've just simply hacked the contentfinder to replace "solution:" with the solution root path

this is however a hack and i would like to fix this properly if possible

Any input on this?
Would really appreciate it

-Paul

On May 17, 2011, at 6:09 , Paul Stoellberger wrote:

> Hi,
>
> I'm using a similar approach to the XmlServlet to load up mondrian/olap4j.
> Now my question is, once i created the MondrianServer, how can i retrieve all connections?
>
> i thought i could use the catalognames etc. as a wildcard but it seems like thats failing.
>
> (A loop until con is null)
> con = server.getConnection(null, null, null);
> ... (add it to the list of connections)
>
> -Paul


_______________________________________________
Mondrian mailing list
Mondrian (AT) pentaho (DOT) org
http://lists.pentaho.org/mailman/listinfo/mondrian

[Luc Boudreau]

This is the same strategy used in Pentaho's BI server. 'solution:' is not a
proper protocol so we too remove the prefix and replace it with the actual
absolute path.

Luc

On Tue, May 17, 2011 at 11:19 AM, Paul Stoellberger <
p.stoellberger (AT) gmail (DOT) com> wrote:

> Just a quick update
>
> The problem was that Util.readVirtualFile() was called 3 times for a
> catalog
> 2 times the CatalogLocator replaced the "solution:" VFS prefix with the
> solution repository path (yeah thats in the biserver) .... so i get
> file:/user/tmp/file.xml
> but the last time it didn't, and thats when i got the error ... the path
> still looks like : solution:biserver/steelwheels/asdf.xml
>
> I've just simply hacked the contentfinder to replace "solution:" with the
> solution root path
>
> this is however a hack and i would like to fix this properly if possible
>
> Any input on this?
> Would really appreciate it
>
> -Paul
>
> On May 17, 2011, at 6:09 , Paul Stoellberger wrote:
>
> Hi,
>
> I'm using a similar approach to the XmlServlet to load up mondrian/olap4j.
> Now my question is, once i created the MondrianServer, how can i retrieve
> all connections?
>
> i thought i could use the catalognames etc. as a wildcard but it seems like
> thats failing.
>
> (A loop until con is null)
> con = server.getConnection(null, null, null);
> ... (add it to the list of connections)
>
> -Paul
>
>
>
> _______________________________________________
> Mondrian mailing list
> Mondrian (AT) pentaho (DOT) org
> http://lists.pentaho.org/mailman/listinfo/mondrian
>
>

_______________________________________________
Mondrian mailing list
Mondrian (AT) pentaho (DOT) org
http://lists.pentaho.org/mailman/listinfo/mondrian

[Paul Stoellberger]

yeah but i thought thats what the cataloglocator is for!?
it is being called and replaces the path correctly. but somehow mondrian still wants to read it from the wrong url in 1 out of 3 cases. in 2 my correct cataloglocator url is being used

my implementation is based on the biservers implementation in pentahoxmlaserlvlet but somehow there is a small piece missing i guess

-paul




Am 17.05.2011 um 16:37 schrieb Luc Boudreau <lucboudreau (AT) gmail (DOT) com>:

> This is the same strategy used in Pentaho's BI server. 'solution:' is not a proper protocol so we too remove the prefix and replace it with the actual absolute path.
>
> Luc
>
> On Tue, May 17, 2011 at 11:19 AM, Paul Stoellberger <p.stoellberger (AT) gmail (DOT) com> wrote:
> Just a quick update
>
> The problem was that Util.readVirtualFile() was called 3 times for a catalog
> 2 times the CatalogLocator replaced the "solution:" VFS prefix with the solution repository path (yeah thats in the biserver) .... so i get file:/user/tmp/file.xml
> but the last time it didn't, and thats when i got the error ... the path still looks like : solution:biserver/steelwheels/asdf.xml
>
> I've just simply hacked the contentfinder to replace "solution:" with the solution root path
>
> this is however a hack and i would like to fix this properly if possible
>
> Any input on this?
> Would really appreciate it
>
> -Paul
>
> On May 17, 2011, at 6:09 , Paul Stoellberger wrote:
>
>> Hi,
>>
>> I'm using a similar approach to the XmlServlet to load up mondrian/olap4j..
>> Now my question is, once i created the MondrianServer, how can i retrieve all connections?
>>
>> i thought i could use the catalognames etc. as a wildcard but it seems like thats failing.
>>
>> (A loop until con is null)
>> con = server.getConnection(null, null, null);
>> ... (add it to the list of connections)
>>
>> -Paul
>
>
> _______________________________________________
> Mondrian mailing list
> Mondrian (AT) pentaho (DOT) org
> http://lists.pentaho.org/mailman/listinfo/mondrian
>
>
> _______________________________________________
> Mondrian mailing list
> Mondrian (AT) pentaho (DOT) org
> http://lists.pentaho.org/mailman/listinfo/mondrian

_______________________________________________
Mondrian mailing list
Mondrian (AT) pentaho (DOT) org
http://lists.pentaho.org/mailman/listinfo/mondrian