Re: [osgi-dev] Integration with Karaf

2016-11-10 Thread David Leangen 

> For anybody else confused by this thread, there are now two Tim Wards 
> apparently!



Ahh! Now I understand!! :-)

Hehehe. Thanks for pointing this out.

The disadvantage of “David” is that there are too many of us. But I have an 
unusual last name, so at least there are not two of me (that I know of).

=David

___
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev

Re: [osgi-dev] Integration with Karaf

2016-11-10 Thread Tim Ward 

On 10/11/2016 11:05, Tim Ward wrote:

On 10/11/2016 10:26, Tim Verbelen wrote:

Hi Tim,

If you want to use some of the eclipse equinox bundles (such as 
org.eclipse.equinox.coordinator), you are kind of bound to the 
equinox framework since they depend on the org.eclipse.osgi.util 
package that is provided by the equinox framework.


Sorry, I have no idea whether I "want to use some of the eclipse 
equinox bundles". All I did (I think!) so far as any "configurer" 
(which seems to be the problem?) was concerned was put


@RequireConfigurerExtender

in one of my source files, which I think I copied from one of the 
tutorials. I haven't found any documentation of what this actually 
does - is it specific to equinox, is it something that I can't use 
with felix? In which case what should I have written to use felix, and 
where do I find the documentation?


So I tried commenting out the @RequireConfigurerExtender to see what 
would happen (in addition, of course, to my code not working), and got 
the following:


karaf@root()> list
START LEVEL 100 , List Threshold: 50
 ID | State | Lvl | Version| Name
---
 56 | Active|  80 | 3.2.0.201605172008 | biz.aQute.remote.agent
158 | Active|  80 | 1.0.1  | Apache Felix Log Service
159 | Active|  80 | 1.0.0.201611091637 | 
com.telensa.apps.planet.pc.provider
160 | Active|  80 | 1.0.0.201611101220 | 
com.telensa.apps.planet.ws.application

162 | Active|  80 | 3.2.0  | Apache Felix Http Jetty
163 | Active|  80 | 1.1.2  | Apache Felix Servlet API
164 | Active|  80 | 2.0.2  | Apache Felix 
Declarative Services

165 | Active|  80 | 9.3.8.v20160314| Jetty :: Utilities
166 | Active|  80 | 9.3.8.v20160314| Jetty :: Utilities :: 
Ajax(JSON)
167 | Active|  80 | 1.3.1.201505202024 | 
org.osgi:org.osgi.service.event
168 | Active|  80 | 1.3.0.201505202024 | 
org.osgi:org.osgi.service.metatype
169 | Active|  80 | 2.0.0.201610141744 | 
osgi.enroute.executor.simple.provider
170 | Active|  80 | 2.0.0.201610141744 | 
osgi.enroute.logger.simple.provider
171 | Active|  80 | 2.0.0.201610141745 | 
osgi.enroute.web.simple.provider

172 | Installed |  80 | 1.3.100.v20140115-1647 | Event Admin
173 | Installed |  80 | 1.4.100.v20150408-1437 | Meta Type
karaf@root()>

So my bundles are now fully resolved and active, but what on earth are 
the unresolved "Event Admin" and "Meta Type" doing there? - I didn't 
explicitly ask for them, and if their failure to resolve doesn't stop my 
application resolving why are they there at all?


--
Tim Ward

___
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev

Re: [osgi-dev] Integration with Karaf

2016-11-10 Thread Tim Ward 

On 10/11/2016 10:31, Neil Bartlett wrote:
For anybody else confused by this thread, there are now two Tim Wards 
apparently!


Oh yes, I had spotted that there was one already here, and had intended 
to say "this is a different one" in my first post to the list, but 
forgot to do so - sorry for any confusion.


--
Tim Ward

___
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev

Re: [osgi-dev] Integration with Karaf

2016-11-10 Thread Tim Ward 

On 10/11/2016 10:26, Tim Verbelen wrote:

Hi Tim,

If you want to use some of the eclipse equinox bundles (such as 
org.eclipse.equinox.coordinator), you are kind of bound to the equinox 
framework since they depend on the org.eclipse.osgi.util package that 
is provided by the equinox framework.


Sorry, I have no idea whether I "want to use some of the eclipse equinox 
bundles". All I did (I think!) so far as any "configurer" (which seems 
to be the problem?) was concerned was put


@RequireConfigurerExtender

in one of my source files, which I think I copied from one of the 
tutorials. I haven't found any documentation of what this actually does 
- is it specific to equinox, is it something that I can't use with 
felix? In which case what should I have written to use felix, and where 
do I find the documentation?


If you do want to run these on a different OSGi framework, try 
including the org.eclipse.equinox.supplement bundle, which is a small 
utility bundle that also exports this util package. The source code 
can be found at 
http://git.eclipse.org/c/equinox/rt.equinox.framework.git/tree/bundles/org.eclipse.osgi/supplement


We are fore example hosting a version of this bundle in the Ecipse 
Concierge repository 
(https://www.eclipse.org/concierge/repository/index.xml), which you 
can add to your BNDTools workspace. Make sure to add the supplement 
bundle to your run requirements before hitting resolve.


Best regards,

Tim



--
Tim Ward

___
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev

Re: [osgi-dev] Integration with Karaf

2016-11-10 Thread Tim Verbelen 

Hi Tim,

If you want to use some of the eclipse equinox bundles (such as 
org.eclipse.equinox.coordinator), you are kind of bound to the equinox 
framework since they depend on the org.eclipse.osgi.util package that is 
provided by the equinox framework.


If you do want to run these on a different OSGi framework, try including 
the org.eclipse.equinox.supplement bundle, which is a small utility 
bundle that also exports this util package. The source code can be found 
at 
http://git.eclipse.org/c/equinox/rt.equinox.framework.git/tree/bundles/org.eclipse.osgi/supplement


We are fore example hosting a version of this bundle in the Ecipse 
Concierge repository 
(https://www.eclipse.org/concierge/repository/index.xml), which you can 
add to your BNDTools workspace. Make sure to add the supplement bundle 
to your run requirements before hitting resolve.


Best regards,

Tim

On 11/10/2016 10:32 AM, Tim Ward wrote:
So, I've gone through the enRoute tutorials, which worked fine, then 
tried writing some code of my own, which worked fine, then tried 
deploying it to Karaf, attempting to following the instructions in


http://enroute.osgi.org/appnotes/bndtools-and-karaf.html

and it doesn't work, and after several days nobody here can make any 
progress with understanding what's wrong or how to fix it.


As I'm new to this stuff I don't really know what information might 
enable people to help spot my problem, but I'll start with the karaf 
output below. I did the "resolve" on the debug.bndrun so why are there 
things that appear not to be resolved?


karaf@root()> list
START LEVEL 100 , List Threshold: 50
 ID | State | Lvl | Version| Name
 


 56 | Active|  80 | 3.2.0.201605172008 | biz.aQute.remote.agent
137 | Active|  80 | 1.0.1  | Apache Felix Log Service
138 | Active|  80 | 1.0.0.201611091637 | 
com.telensa.apps.planet.pc.provider
139 | Installed |  80 | 1.0.0.201611091638 | 
com.telensa.apps.planet.ws.application

141 | Active|  80 | 3.2.0  | Apache Felix Http Jetty
142 | Active|  80 | 1.1.2  | Apache Felix Servlet API
143 | Active|  80 | 2.0.2  | Apache Felix 
Declarative Services

144 | Installed |  80 | 1.3.100.v20150410-1453 | Coordinator
145 | Installed |  80 | 1.3.100.v20140115-1647 | Event Admin
146 | Installed |  80 | 1.4.100.v20150408-1437 | Meta Type
147 | Active|  80 | 9.3.8.v20160314| Jetty :: Utilities
148 | Active|  80 | 9.3.8.v20160314| Jetty :: Utilities :: 
Ajax(JSON)
149 | Active|  80 | 1.3.1.201505202024 | 
org.osgi:org.osgi.service.event
150 | Active|  80 | 1.3.0.201505202024 | 
org.osgi:org.osgi.service.metatype
151 | Installed |  80 | 2.0.0.201610141744 | 
osgi.enroute.configurer.simple.provider
152 | Active|  80 | 2.0.0.201610141744 | 
osgi.enroute.executor.simple.provider
153 | Active|  80 | 2.0.0.201610141744 | 
osgi.enroute.logger.simple.provider
154 | Active|  80 | 2.0.0.201610141745 | 
osgi.enroute.web.simple.provider

karaf@root()> diag
com.telensa.apps.planet.ws.application (139)

Status: Installed
Unsatisfied Requirements:
[com.telensa.apps.planet.ws.application [139](R 139.0)] osgi.extender; 
(&(osgi.extender=osgi.enroute.configurer)(&(version>=1.0.0)(!(version>=2.0.0



Coordinator (144)
-
Status: Installed
Unsatisfied Requirements:
[org.eclipse.equinox.coordinator [144](R 144.0)] osgi.wiring.package; 
(&(osgi.wiring.package=org.eclipse.osgi.util)(version>=1.1.0)(!(version>=2.0.0)))
[org.eclipse.equinox.coordinator [144](R 144.0)] osgi.wiring.package; 
(&(osgi.wiring.package=org.osgi.service.coordinator)(version>=1.0.0)(!(version>=1.1.0)))



Event Admin (145)
-
Status: Installed
Unsatisfied Requirements:
[org.eclipse.equinox.event [145](R 145.0)] osgi.wiring.package; 
(&(osgi.wiring.package=org.eclipse.osgi.framework.eventmgr)(version>=1.1.0))
[org.eclipse.equinox.event [145](R 145.0)] osgi.wiring.package; 
(&(osgi.wiring.package=org.eclipse.osgi.util)(version>=1.1.0))



Meta Type (146)
---
Status: Installed
Unsatisfied Requirements:
[org.eclipse.equinox.metatype [146](R 146.0)] osgi.wiring.package; 
(&(osgi.wiring.package=org.eclipse.osgi.util)(version>=1.1.0)(!(version>=2.0.0))) 




osgi.enroute.configurer.simple.provider (151)
-
Status: Installed
Unsatisfied Requirements:
[osgi.enroute.configurer.simple.provider [151](R 151.0)] 
osgi.wiring.package; 
(&(osgi.wiring.package=org.osgi.service.coordinator)(version>=1.0.0)(!(version>=2.0.0)))
[osgi.enroute.configurer.simple.provider [151](R 151.0)] 
osgi.wiring.package; 
(&(osgi.wiring.package=osgi.enroute.configurer.api)(version>=1.0.0)(!(version>=1.1.0)))
[osgi.enroute.configurer.simple.provider [151](R 151.0)]

Re: [osgi-dev] Integration with Karaf

2016-11-10 Thread Christian Schneider 

On 10.11.2016 10:55, Tim Ward wrote:


Insofar as I understand any of what is going on, which is not very 
much, this sounds plausible - there does look like a bizarre mixture 
of equinox and felix components (although one of my colleagues says 
"that's not a problem as they all just implement OSGi specs").
You typically can mix components from equinox and felix but you should 
never install two implementations of the same spec.



Like:
equinox event admin -> felix event admin
equinox meta type -> felix meta type
equinox coordinator -> felix coordinator

For configurer I am not sure. In karaf there is the combination of 
felix comfig admin and file install for this but configurer might 
still fit in.


I suggest that you change these bundles in the index you use to the 
ones that are present in karaf.


All I did was hit the "resolve" button on the debug.bndrun file. Are 
you suggesting I somehow persuade that button to do something 
different? How?
Yes. You need to provide an index that has the right bundles for the 
platform to deploy to. Then resolve will come up with a solution that is 
better for running in karaf.
The pom I pointed to provides such an index. Alternatively you can add 
the bundles individually to your own index / repository.


You need to make sure that the implementation bundles the resolver works 
on are compatible to the bundles that are already present in karaf.


Christian

--
Christian Schneider
http://www.liquid-reality.de

Open Source Architect
http://www.talend.com

___
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev

Re: [osgi-dev] Integration with Karaf

2016-11-10 Thread Guillaume Nodet 
You asked how to solve the problem, I'm just answering.
If you don't want to depend on Equinox framework, do not deploy bundles
that do depend on it ;-)
In this case,  osgi.enroute.configurer.simple.provider depends on the
equinox coordinator which depends on org.eclipse.equinox.util package
provided by the equinox framework.
Christian indicated replacement bundles.  Felix services (such as
eventadmin, coordinator) don't have any dependencies on a specific
framework.

As for why those bundles have been selected for deployment, I can't help
you on that part...

2016-11-10 10:50 GMT+01:00 Tim Ward :

> On 10/11/2016 09:43, Guillaume Nodet wrote:
>
> It seems you have a strong dependency on the Equinox OSGi framework.
> In Karaf, run the "framework equinox ; shutdown --reboot --force " commands
> and see if this is better.
>
>
> Thanks, but we are specifically and deliberately wanting to use Felix, and
> I think those commands would switch from Felix to Equinox?
>
> --
> Tim Ward
>
>
> ___
> OSGi Developer Mail List
> osgi-dev@mail.osgi.org
> https://mail.osgi.org/mailman/listinfo/osgi-dev
>



-- 
---
Guillaume Nodet

Red Hat, Open Source Integration

Email: gno...@redhat.com
Web: http://fusesource.com
Blog: http://gnodet.blogspot.com/
___
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev

Re: [osgi-dev] Integration with Karaf

2016-11-10 Thread Tim Ward 

On 10/11/2016 09:44, Christian Schneider wrote:
It looks like you are installing a lot of bundles that are already 
present in apache karaf. These can conflict with the ones already 
present.
The actual resolve problems you get are because you are missing some 
equinox bundles the bundle you try to install need. Installing these 
will not
fully solve your problems though as there will still be conflicts with 
the bundles karaf already has.


Insofar as I understand any of what is going on, which is not very much, 
this sounds plausible - there does look like a bizarre mixture of 
equinox and felix components (although one of my colleagues says "that's 
not a problem as they all just implement OSGi specs").



Like:
equinox event admin -> felix event admin
equinox meta type -> felix meta type
equinox coordinator -> felix coordinator

For configurer I am not sure. In karaf there is the combination of 
felix comfig admin and file install for this but configurer might 
still fit in.


I suggest that you change these bundles in the index you use to the 
ones that are present in karaf.


All I did was hit the "resolve" button on the debug.bndrun file. Are you 
suggesting I somehow persuade that button to do something different? How?



As a starting point you can use the ones I use in this index project:
https://github.com/apache/cxf-dosgi/tree/master/samples/repository


Sorry, I don't understand what you're suggesting I do here. I don't have 
any "pom" files, I'm using bndtools.



Christian


--
Tim Ward

___
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev

Re: [osgi-dev] Integration with Karaf

2016-11-10 Thread Tim Ward 

On 10/11/2016 09:43, Guillaume Nodet wrote:

It seems you have a strong dependency on the Equinox OSGi framework.
In Karaf, run the "framework equinox ;shutdown --reboot --force " 
commands and see if this is better.


Thanks, but we are specifically and deliberately wanting to use Felix, 
and I think those commands would switch from Felix to Equinox?


--
Tim Ward

___
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev

Re: [osgi-dev] Integration with Karaf

2016-11-10 Thread Christian Schneider 
It looks like you are installing a lot of bundles that are already 
present in apache karaf. These can conflict with the ones already present.
The actual resolve problems you get are because you are missing some 
equinox bundles the bundle you try to install need. Installing these 
will not
fully solve your problems though as there will still be conflicts with 
the bundles karaf already has.


Like:
equinox event admin -> felix event admin
equinox meta type -> felix meta type
equinox coordinator -> felix coordinator

For configurer I am not sure. In karaf there is the combination of felix 
comfig admin and file install for this but configurer might still fit in.


I suggest that you change these bundles in the index you use to the ones 
that are present in karaf.

As a starting point you can use the ones I use in this index project:
https://github.com/apache/cxf-dosgi/tree/master/samples/repository

Christian

On 10.11.2016 10:32, Tim Ward wrote:
So, I've gone through the enRoute tutorials, which worked fine, then 
tried writing some code of my own, which worked fine, then tried 
deploying it to Karaf, attempting to following the instructions in


http://enroute.osgi.org/appnotes/bndtools-and-karaf.html

and it doesn't work, and after several days nobody here can make any 
progress with understanding what's wrong or how to fix it.


As I'm new to this stuff I don't really know what information might 
enable people to help spot my problem, but I'll start with the karaf 
output below. I did the "resolve" on the debug.bndrun so why are there 
things that appear not to be resolved?


karaf@root()> list
START LEVEL 100 , List Threshold: 50
 ID | State | Lvl | Version| Name
 


 56 | Active|  80 | 3.2.0.201605172008 | biz.aQute.remote.agent
137 | Active|  80 | 1.0.1  | Apache Felix Log Service
138 | Active|  80 | 1.0.0.201611091637 | 
com.telensa.apps.planet.pc.provider
139 | Installed |  80 | 1.0.0.201611091638 | 
com.telensa.apps.planet.ws.application

141 | Active|  80 | 3.2.0  | Apache Felix Http Jetty
142 | Active|  80 | 1.1.2  | Apache Felix Servlet API
143 | Active|  80 | 2.0.2  | Apache Felix 
Declarative Services

144 | Installed |  80 | 1.3.100.v20150410-1453 | Coordinator
145 | Installed |  80 | 1.3.100.v20140115-1647 | Event Admin
146 | Installed |  80 | 1.4.100.v20150408-1437 | Meta Type
147 | Active|  80 | 9.3.8.v20160314| Jetty :: Utilities
148 | Active|  80 | 9.3.8.v20160314| Jetty :: Utilities :: 
Ajax(JSON)
149 | Active|  80 | 1.3.1.201505202024 | 
org.osgi:org.osgi.service.event
150 | Active|  80 | 1.3.0.201505202024 | 
org.osgi:org.osgi.service.metatype
151 | Installed |  80 | 2.0.0.201610141744 | 
osgi.enroute.configurer.simple.provider
152 | Active|  80 | 2.0.0.201610141744 | 
osgi.enroute.executor.simple.provider
153 | Active|  80 | 2.0.0.201610141744 | 
osgi.enroute.logger.simple.provider
154 | Active|  80 | 2.0.0.201610141745 | 
osgi.enroute.web.simple.provider

karaf@root()> diag
com.telensa.apps.planet.ws.application (139)

Status: Installed
Unsatisfied Requirements:
[com.telensa.apps.planet.ws.application [139](R 139.0)] osgi.extender; 
(&(osgi.extender=osgi.enroute.configurer)(&(version>=1.0.0)(!(version>=2.0.0



Coordinator (144)
-
Status: Installed
Unsatisfied Requirements:
[org.eclipse.equinox.coordinator [144](R 144.0)] osgi.wiring.package; 
(&(osgi.wiring.package=org.eclipse.osgi.util)(version>=1.1.0)(!(version>=2.0.0)))
[org.eclipse.equinox.coordinator [144](R 144.0)] osgi.wiring.package; 
(&(osgi.wiring.package=org.osgi.service.coordinator)(version>=1.0.0)(!(version>=1.1.0)))



Event Admin (145)
-
Status: Installed
Unsatisfied Requirements:
[org.eclipse.equinox.event [145](R 145.0)] osgi.wiring.package; 
(&(osgi.wiring.package=org.eclipse.osgi.framework.eventmgr)(version>=1.1.0))
[org.eclipse.equinox.event [145](R 145.0)] osgi.wiring.package; 
(&(osgi.wiring.package=org.eclipse.osgi.util)(version>=1.1.0))



Meta Type (146)
---
Status: Installed
Unsatisfied Requirements:
[org.eclipse.equinox.metatype [146](R 146.0)] osgi.wiring.package; 
(&(osgi.wiring.package=org.eclipse.osgi.util)(version>=1.1.0)(!(version>=2.0.0))) 




osgi.enroute.configurer.simple.provider (151)
-
Status: Installed
Unsatisfied Requirements:
[osgi.enroute.configurer.simple.provider [151](R 151.0)] 
osgi.wiring.package; 
(&(osgi.wiring.package=org.osgi.service.coordinator)(version>=1.0.0)(!(version>=2.0.0)))
[osgi.enroute.configurer.simple.provider [151](R 151.0)] 
osgi.wiring.package; 
(&(osgi.wiring.package=osgi.enroute.configurer.api)(version>=1.0.0)(!(version>=1.1.0)))

Re: [osgi-dev] Integration with Karaf

2016-11-10 Thread Guillaume Nodet 
It seems you have a strong dependency on the Equinox OSGi framework.
In Karaf, run the "framework equinox ; shutdown --reboot --force " commands
and see if this is better.

2016-11-10 10:32 GMT+01:00 Tim Ward :

> So, I've gone through the enRoute tutorials, which worked fine, then tried
> writing some code of my own, which worked fine, then tried deploying it to
> Karaf, attempting to following the instructions in
>
> http://enroute.osgi.org/appnotes/bndtools-and-karaf.html
>
> and it doesn't work, and after several days nobody here can make any
> progress with understanding what's wrong or how to fix it.
>
> As I'm new to this stuff I don't really know what information might enable
> people to help spot my problem, but I'll start with the karaf output below.
> I did the "resolve" on the debug.bndrun so why are there things that appear
> not to be resolved?
>
> karaf@root()> list
> START LEVEL 100 , List Threshold: 50
>  ID | State | Lvl | Version| Name
> 
> 
>  56 | Active|  80 | 3.2.0.201605172008 | biz.aQute.remote.agent
> 137 | Active|  80 | 1.0.1  | Apache Felix Log Service
> 138 | Active|  80 | 1.0.0.201611091637 |
> com.telensa.apps.planet.pc.provider
> 139 | Installed |  80 | 1.0.0.201611091638 |
> com.telensa.apps.planet.ws.application
> 141 | Active|  80 | 3.2.0  | Apache Felix Http Jetty
> 142 | Active|  80 | 1.1.2  | Apache Felix Servlet API
> 143 | Active|  80 | 2.0.2  | Apache Felix Declarative
> Services
> 144 | Installed |  80 | 1.3.100.v20150410-1453 | Coordinator
> 145 | Installed |  80 | 1.3.100.v20140115-1647 | Event Admin
> 146 | Installed |  80 | 1.4.100.v20150408-1437 | Meta Type
> 147 | Active|  80 | 9.3.8.v20160314| Jetty :: Utilities
> 148 | Active|  80 | 9.3.8.v20160314| Jetty :: Utilities ::
> Ajax(JSON)
> 149 | Active|  80 | 1.3.1.201505202024 |
> org.osgi:org.osgi.service.event
> 150 | Active|  80 | 1.3.0.201505202024 |
> org.osgi:org.osgi.service.metatype
> 151 | Installed |  80 | 2.0.0.201610141744 |
> osgi.enroute.configurer.simple.provider
> 152 | Active|  80 | 2.0.0.201610141744 |
> osgi.enroute.executor.simple.provider
> 153 | Active|  80 | 2.0.0.201610141744 |
> osgi.enroute.logger.simple.provider
> 154 | Active|  80 | 2.0.0.201610141745 |
> osgi.enroute.web.simple.provider
> karaf@root()> diag
> com.telensa.apps.planet.ws.application (139)
> 
> Status: Installed
> Unsatisfied Requirements:
> [com.telensa.apps.planet.ws.application [139](R 139.0)] osgi.extender;
> (&(osgi.extender=osgi.enroute.configurer)(&(version>=1.0.0)(
> !(version>=2.0.0
>
>
> Coordinator (144)
> -
> Status: Installed
> Unsatisfied Requirements:
> [org.eclipse.equinox.coordinator [144](R 144.0)] osgi.wiring.package;
> (&(osgi.wiring.package=org.eclipse.osgi.util)(version>=1.1.
> 0)(!(version>=2.0.0)))
> [org.eclipse.equinox.coordinator [144](R 144.0)] osgi.wiring.package;
> (&(osgi.wiring.package=org.osgi.service.coordinator)(version
> >=1.0.0)(!(version>=1.1.0)))
>
>
> Event Admin (145)
> -
> Status: Installed
> Unsatisfied Requirements:
> [org.eclipse.equinox.event [145](R 145.0)] osgi.wiring.package;
> (&(osgi.wiring.package=org.eclipse.osgi.framework.eventmgr)(
> version>=1.1.0))
> [org.eclipse.equinox.event [145](R 145.0)] osgi.wiring.package;
> (&(osgi.wiring.package=org.eclipse.osgi.util)(version>=1.1.0))
>
>
> Meta Type (146)
> ---
> Status: Installed
> Unsatisfied Requirements:
> [org.eclipse.equinox.metatype [146](R 146.0)] osgi.wiring.package;
> (&(osgi.wiring.package=org.eclipse.osgi.util)(version>=1.1.
> 0)(!(version>=2.0.0)))
>
>
> osgi.enroute.configurer.simple.provider (151)
> -
> Status: Installed
> Unsatisfied Requirements:
> [osgi.enroute.configurer.simple.provider [151](R 151.0)]
> osgi.wiring.package; (&(osgi.wiring.package=org.osg
> i.service.coordinator)(version>=1.0.0)(!(version>=2.0.0)))
> [osgi.enroute.configurer.simple.provider [151](R 151.0)]
> osgi.wiring.package; (&(osgi.wiring.package=osgi.en
> route.configurer.api)(version>=1.0.0)(!(version>=1.1.0)))
> [osgi.enroute.configurer.simple.provider [151](R 151.0)] osgi.service;
> (objectClass=java.lang.Object)
> [osgi.enroute.configurer.simple.provider [151](R 151.0)] osgi.service;
> (objectClass=org.osgi.service.cm.ConfigurationAdmin)
> [osgi.enroute.configurer.simple.provider [151](R 151.0)] osgi.service;
> (objectClass=org.osgi.service.coordinator.Coordinator)
> [osgi.enroute.configurer.simple.provider [151](R 151.0)] osgi.service;
> (objectClass=org.osgi.service.log.LogService)
>
>
> karaf@root()>
>
>
> --
> Tim Ward
>
> ___
> OSGi Developer Mail List