On 8/2/10 15:21, Carl Hall wrote:
The manifest from our oracle ojdbc bundle is attached. To my knowledge, we don't use any mandatory attributes. There are no other errors in the log. Just this CNFE over and over (every ~5 secs).

You might have to copy it into the message since the attachment appears to have been stripped.

-> richard



On Mon, Aug 2, 2010 at 2:38 PM, Richard S. Hall <[email protected] <mailto:[email protected]>> wrote:

     On 8/2/10 14:30, Carl Hall wrote:

        I'm baffled by the message below.  This was working a little
        while back but
        have no explanation as to what changed to bring this about.

        We're exporting the Oracle JDBC driver from a bundle as noted
        below.  We
        have 'DynamicImport-Package: *' set on the bundle giving the
        message.
        What attributes are mismatched?  How can I get around this?

        Caused by: java.lang.ClassNotFoundException: *** Class
        'oracle.jdbc.driver.OracleDriver' was not found, but this is
        likely normal
        since package 'oracle.jdbc.driver' is dynamically imported by
        bundle
        org.apache.sling.jcr.jackrabbit.server [26]. However, bundle
        org.sakaiproject.nakamura.ojdbc [117] does export this package
        with
        attributes that do not match. ***


    It is possible it is exported with mandatory attributes? Perhaps
    you can show the manifest from the providing bundle. Are there any
    other messages being logged by the framework?

    -> richard

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: [email protected]
    <mailto:[email protected]>
    For additional commands, e-mail: [email protected]
    <mailto:[email protected]>




---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to