Mikhail Cherkasov created IGNITE-6352:
-----------------------------------------

             Summary: ignite-indexing is not compatible to OSGI
                 Key: IGNITE-6352
                 URL: https://issues.apache.org/jira/browse/IGNITE-6352
             Project: Ignite
          Issue Type: Bug
          Components: sql
    Affects Versions: 2.1
            Reporter: Mikhail Cherkasov
             Fix For: 2.3


the issue is reported by user, there's his message:

When trying to start Ignite in an OSGi context I get the following exception:
Caused by: java.lang.NoClassDefFoundError: org/h2/server/Service
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:264)
at 
org.apache.ignite.internal.IgniteComponentType.inClassPath(IgniteComponentType.java:153)
at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1832)
at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1648)
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1076)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:506)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:482)
at org.apache.ignite.Ignition.start(Ignition.java:304)

 That is because the h2 bundle (jar) is properly osgified, but does NOT export 
the package org.h2.server, so it isn't visible to my code's classloader



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to