Details

    • Sub-task
    • Status: Closed
    • Major
    • Resolution: Not A Problem
    • 1.4.0
    • 1.6.0, 2.0-M1
    • camel-core, osgi
    • None

    Description

      See parent issue.

      Thanks Claus. I hope this can help getting it resolved. Let me know if it is, even a snapshot will do very well for us.

      Another question, is below "DynamicImport-Package workaround" supposed to be bug? Or it's just the way Camel needs to be configured on OSGi? If so it should be mentioned somewhere in the docs... not everybody knows that DynamicImport-Package even exists.. (even some OSGi programmers)

      First of all, to even get this to "work" requires my own bundle to have this manifest:
      DynamicImport-Package: org.apache.camel.*

      Failing to do so will result in more classloading errors.

      Attachments

        Activity

          People

            Unassigned Unassigned
            davsclaus Claus Ibsen
            Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: