Hey Christian,

1) fragments will never start; they only get resolved
2) What exactly is the startup exception? (using log:display-exception in the 
karaf
console or getting the relevant log from ${karaf.home}/data/log/karaf.log (or
servicemix.log I think it is for smx)
3) I'm not sure if it's the service or the API you have to extend. You can try
both

kind regards,
andreas

On Mon, Dec 13, 2010 at 11:18:22AM +0100, Christian Müller wrote:
>    Hello Niclas, hello Achim!
>    Thank your for your answers.
>    We trieyed Achim's proposed solution. We created a fragment bundle (see
>    attachment for the OSGI bundle) which has this OSGI meta data in
>    MANIFEST.MF:
>    Fragment-Host:
>    org.ops4j.pax.logging.pax-logging-service;bundle-version="[1.5.0,1.6.0)
>    "
>    We also changed the ServiceMix configuration file
>    SERVICEMIX/etc/org.ops4j.pax.logging.cfg and instruct ServiceMix to use
>    our custom Layout class:
>    log4j.appender.out.layout=com.awl.wlsi.extensions.pcilogging.PCIPattern
>    Layout
>    We added this bundle to the SERVICEMIX/etc/startup.properties file
>    direct after the pax logging bundles:
>    org/ops4j/pax/logging/pax-logging-api/1.5.0/pax-logging-api-1.5.0.jar=8
>    org/ops4j/pax/logging/pax-logging-service/1.5.0/pax-logging-service-1.5
>    .0.jar=8
>    com/awl/wlsi/extensions/pci-logging-extension/1.1.0-SNAPSHOT/pci-loggin
>    g-extension-1.1.0-SNAPSHOT.jar=8
>    When we start ServiceMix, we can see the following message:
>    Auto-properties start: org.osgi.framework.BundleException: A fragment
>    bundle cannot be started:
>    com.awl.wlsi.extensions.pci-logging-extension_1.1.0.SNAPSHOT [3]
>    Peculiarly the OSGI bundles are not started anymore:
>    ka...@root> osgi:list
>    START LEVEL 100
>       ID   State         Blueprint      Spring    Level  Name
>    [   0] [Active     ] [            ] [       ] [    0] OSGi System
>    Bundle (3.5.1.R35x_v20090827)
>    [   1] [Active     ] [            ] [       ] [    5] OPS4J Pax Url -
>    mvn: (1.1.2)
>    [   2] [Active     ] [            ] [       ] [    5] OPS4J Pax Url -
>    wrap: (1.1.2)
>    [   3] [Resolved   ] [            ] [       ] [    8] WLSI ::
>    extensions :: pci-logging-extension (1.1.0.SNAPSHOT)
>                                           Hosts: 4
>    [   4] [Resolved   ] [            ] [       ] [    8] OPS4J Pax Logging
>    - Service (1.5.0)
>                                           Fragments: 3
>    ...
>    If we start the bundles, we get the following exceptions:
>    ka...@root> start 4
>    You are about to access system bundle 4.  Do you want to continue
>    (yes/no): Exception in
>    org.ops4j.pax.logging.service.internal.Activator.start() of bundle
>    org.ops4j.pax.logging.pax-logging-service.
>    ka...@root> start 3
>    You are about to access system bundle 3.  Do you want to continue
>    (yes/no): A fragment bundle cannot be started:
>    com.awl.wlsi.extensions.pci-logging-extension_1.1.0.SNAPSHOT [3]
>    Unfortunatly the servicemix log file is empty.
>    Any ideas what we are doing wrong?
>    Thanks in advance,
>    Christian


> _______________________________________________
> general mailing list
> [email protected]
> http://lists.ops4j.org/mailman/listinfo/general

Attachment: pgpmObzvUunEm.pgp
Description: PGP signature

_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general

Reply via email to