<div dir="ltr">Just dropping it in there won&#39;t work because OSGI doesn&#39;t have a way to know that mondrian&#39;s bundle depends on your driver&#39;s bundle. <div><br></div><div>What you do is create a new fragment bundle (a jar with only the META-INF stuff) which depends on the driver&#39;s bundle but injects itself into the mondrian bundle. This should bridge the two.</div>

</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Jun 27, 2014 at 11:40 AM, Tom Barber(Alabs) <span dir="ltr">&lt;<a href="mailto:tom@analytical-labs.com" target="_blank">tom@analytical-labs.com</a>&gt;</span> wrote:<br>

<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
  
    
  
  <div bgcolor="#FFFFFF" text="#000000">
    <div>Ah yeah Kurtis is correct the Mysql
      JDBC Driver has the osgi headers.<br>
      <br>
      We&#39;ll I&#39;ve put it in the fragment_bundles directory and I still
      get the Hive error, any other suggestions?<br>
      <br>
      Thanks<span class="HOEnZb"><font color="#888888"><br>
      <br>
      Tom</font></span><div><div class="h5"><br>
      <br>
      On 27/06/14 16:31, Kurtis Walker wrote:<br>
    </div></div></div><div><div class="h5">
    <blockquote type="cite">
      
      
      Yes, but I think most of them already are.  If the manifest has a
      Bundle-Name, Bundle-Version, etc, then it is ready for osgi.<br>
      <br>
      On Fri, 2014-06-27 at 10:24 -0500, Tom Barber(Alabs) wrote:
      <blockquote type="CITE"> Hmm thanks for the tip Kurtis, no joy so
        far. Should I assume the driver needs osgi&#39;ifying?<br>
        <br>
        Thanks<br>
        <br>
        Tom<br>
        <br>
        On 27/06/14 15:46, Kurtis Walker wrote:<br>
        <br>
      </blockquote>
      <blockquote type="CITE">
        <blockquote type="CITE"> The hive error is misleading.  It
          really means that no JDBC driver could be found to satisfy
          your connect string.  I think you&#39;ll need to put your driver
          in the OSGI directory also.<br>
          <br>
          On Fri, 2014-06-27 at 09:33 -0500, Tom Barber(Alabs) wrote: <br>
          <blockquote type="CITE"> Looks about right, thanks Luc,
            Mondrian + Commons IO needed placing in the osgi
            directory.....<br>
            <br>
            Now if only I knew why on earth its trying to use Hive to
            connect....<br>
            <br>
            On 27/06/14 14:11, Luc Boudreau wrote:<br>
            <br>
            <blockquote type="CITE"> Oh right. That&#39;d be in the EE
              builds only I&#39;m afraid. <br>
              <br>
              The modules should be in solutions/system/osgi<br>
              <br>
              On Jun 27, 2014 8:59 AM, &quot;Tom Barber(Alabs)&quot; &lt;<a href="mailto:tom@analytical-labs.com" target="_blank">tom@analytical-labs.com</a>&gt;
              wrote: <br>
              <blockquote> Interesting Luc, you mean should work out of
                the box, as in, there is already a jar there?<br>
                <br>
                I downloaded 5.1 and had a look, the Mondrian Jar I
                found(grep) was labeled 3.7 and I asked Pedro and he
                said there were some Mondrian 4 stuff for Mongo but not
                in general population.<br>
                <br>
                Tom<br>
                <br>
                On 27/06/14 13:50, Luc Boudreau wrote:<br>
                <br>
                <blockquote type="CITE"> Hello Tom, <br>
                  <br>
                  With a 5.1 server, all you need to do is use
                  &quot;jdbc:mondrian4&quot; instead of &quot;jdbc:mondrian&quot; as the URL
                  prefix and it should work out of the box. <br>
                  <br>
                  Let us know if you run into any issues. <br>
                  <br>
                  Luc<br>
                  <br>
                  On Jun 27, 2014 6:38 AM, &quot;Tom Barber(Alabs)&quot; &lt;<a href="mailto:tom@analytical-labs.com" target="_blank">tom@analytical-labs.com</a>&gt;
                  wrote:<br>
                  <blockquote> Alright chaps,<br>
                    <br>
                    I&#39;m trying to crowbar Mondrian 4 into the BI Server
                    Saiku plugin and I<br>
                    would like some clarification of a few bits and
                    pieces.<br>
                    <br>
                    We&#39;ve shipped our own Mondrian Jar and also done
                    some funky cache<br>
                    sharing etc, anyway, I would like to ship Mondrian 4
                    and unsurprisingly<br>
                    its not as simple as just replacing the Jar.<br>
                    <br>
                    I would like to know<br>
                    <br>
                    a) is it even possible? I saw Julian&#39;s slide
                    suggesting that the<br>
                    Mondrian 4 lib should run happily alongside Mondrian
                    3 as an OSGI module.<br>
                    b) To bootstrap Mondrian we currently run
                     Class.forName(<br>
                    &quot;mondrian.olap4j.MondrianOlap4jDriver&quot; ); but if
                    have 2 Jars, how does<br>
                    is it supposed to know which to bootstrap, or should
                    it load Mondrian 3,<br>
                    but Mondrian 4 be automatic or do I have to register
                    the Mondrian 4 jar<br>
                    in a different manner?<br>
                    Either way I get<br>
                    java.lang.IllegalAccessError: class
                    mondrian.olap4j.MondrianOlap4jExtra<br>
                    cannot access its superclass
                    mondrian.xmla.XmlaHandler$XmlaExtraImpl<br>
                    <br>
                    The first time I try and run Saiku followed by<br>
                    java.lang.NoClassDefFoundError: Could not initialize
                    class<br>
                    mondrian.olap4j.MondrianOlap4jDriver<br>
                    <br>
                    The next time, so I need work out how to unclash
                    them if possible.<br>
                    <br>
                    I tried just straight replacing Mondrian 3 with
                    Mondrian 4 in the<br>
                    platform out of curiosity but with that I get a
                    linkage error so that<br>
                    test was also a no go.<br>
                    <br>
                    Anyway, hints or tips please.<br>
                    <br>
                    Thanks<br>
                    <br>
                    Tom<br>
                    _______________________________________________<br>
                    Mondrian mailing list<br>
                    <a href="mailto:Mondrian@pentaho.org" target="_blank">Mondrian@pentaho.org</a><br>
                    <a href="http://lists.pentaho.org/mailman/listinfo/mondrian" target="_blank">http://lists.pentaho.org/mailman/listinfo/mondrian</a>
                    <br>
                  </blockquote>
                  <br>
                  <br>
                  <pre>_______________________________________________
Mondrian mailing list
<a href="mailto:Mondrian@pentaho.org" target="_blank">Mondrian@pentaho.org</a>
<a href="http://lists.pentaho.org/mailman/listinfo/mondrian" target="_blank">http://lists.pentaho.org/mailman/listinfo/mondrian</a>
</pre>
                </blockquote>
                <br>
                <br>
                <br>
                _______________________________________________<br>
                Mondrian mailing list<br>
                <a href="mailto:Mondrian@pentaho.org" target="_blank">Mondrian@pentaho.org</a><br>
                <a href="http://lists.pentaho.org/mailman/listinfo/mondrian" target="_blank">http://lists.pentaho.org/mailman/listinfo/mondrian</a><br>
                <br>
              </blockquote>
              <br>
              <br>
              <pre>_______________________________________________
Mondrian mailing list
<a href="mailto:Mondrian@pentaho.org" target="_blank">Mondrian@pentaho.org</a>
<a href="http://lists.pentaho.org/mailman/listinfo/mondrian" target="_blank">http://lists.pentaho.org/mailman/listinfo/mondrian</a>
</pre>
            </blockquote>
            <br>
          </blockquote>
          <br>
          <br>
          <br>
          <pre>_______________________________________________
Mondrian mailing list
<a href="mailto:Mondrian@pentaho.org" target="_blank">Mondrian@pentaho.org</a>
<a href="http://lists.pentaho.org/mailman/listinfo/mondrian" target="_blank">http://lists.pentaho.org/mailman/listinfo/mondrian</a>
</pre>
        </blockquote>
        <br>
      </blockquote>
      <br>
      <br>
      <fieldset></fieldset>
      <br>
      <pre>_______________________________________________
Mondrian mailing list
<a href="mailto:Mondrian@pentaho.org" target="_blank">Mondrian@pentaho.org</a>
<a href="http://lists.pentaho.org/mailman/listinfo/mondrian" target="_blank">http://lists.pentaho.org/mailman/listinfo/mondrian</a>
</pre>
    </blockquote>
    <br>
  </div></div></div>

<br>_______________________________________________<br>
Mondrian mailing list<br>
<a href="mailto:Mondrian@pentaho.org">Mondrian@pentaho.org</a><br>
<a href="http://lists.pentaho.org/mailman/listinfo/mondrian" target="_blank">http://lists.pentaho.org/mailman/listinfo/mondrian</a><br>
<br></blockquote></div><br></div>