You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@karaf.apache.org by "Leschke, Scott" <SL...@medline.com> on 2016/05/13 15:51:19 UTC
Can't resolve org.osgi.service.component 1.2 ?
Hi all,
I've been messing around with OSGi and Karaf for a bit over 2 years now. Technically I'm no longer a developer, although if you want to get stuff done, sometimes you just have to do it yourself. I've built a BAM (Business Activity Monitoring) platform using OSGi (I wasn't aware of Decanter when I originally did this but it sounds very similar in many ways. Looking more closely at that is a future).
To date, I've done everything using Blueprint which has worked quite well but I thought it might be time to take a look at DS to see where that might fit in. To get a feel, I had BndTools create a component bundle and tweaked things a bit so that it should run in Karaf 4.0.5 as BndTools appears to be anticipating OSGi R6 support. I changed the build to reference osgi.cmpn; version=5.0 for example.
When I deploy the bundle, the resolver complains about not being able to satisfy the package requirement: org.osgi.service.component - version [1.2-2.0). I've looked at the manifest and verified that the package is actually imported so I'm at a loss. The component code and actual bundle manifest are shown below, for completeness. Any thoughts on what might be going on would be appreciated.
Regards, Scott
Manifest-Version: 1.0
Bnd-LastModified: 1463152495066
Bundle-ManifestVersion: 2
Bundle-Name: zCompTest
Bundle-SymbolicName: zCompTest
Bundle-Version: 1.0.0.201605131514
Created-By: 1.8.0_71 (Oracle Corporation)
Export-Package: com.medline.zcomptest;version="1.0.0";uses:="org.osgi.
service.component"
Import-Package: org.osgi.service.component;version="[1.2,2)"
Require-Capability: osgi.ee;filter:="(&(osgi.ee=JavaSE)(version=1.8))"
Service-Component: OSGI-INF/com.medline.zcomptest.Example.xml
Tool: Bnd-3.2.0.201605070046-SNAPSHOT
import org.osgi.service.component.ComponentContext;
import org.osgi.service.component.annotations.Activate;
import org.osgi.service.component.annotations.Component;
import org.osgi.service.component.annotations.Deactivate;
@Component(
immediate = true
)
public class Example {
@Activate
protected void activate(ComponentContext c)
{
System.out.println("++ ACTIVATE");
}
@Deactivate
protected void deactivate(ComponentContext c)
{
System.out.println("-- DEACTIVATE");
}
}
Re: Can't resolve org.osgi.service.component 1.2 ?
Posted by Christian Schneider <ch...@die-schneider.net>.
On 13.05.2016 17:51, Leschke, Scott wrote:
>
> Hi all,
>
> Ive been messing around with OSGi and Karaf for a bit over 2 years
> now. Technically Im no longer a developer, although if you want to
> get stuff done, sometimes you just have to do it yourself. Ive built
> a BAM (Business Activity Monitoring) platform using OSGi (I wasnt
> aware of Decanter when I originally did this but it sounds very
> similar in many ways. Looking more closely at that is a future).
>
> To date, Ive done everything using Blueprint which has worked quite
> well but I thought it might be time to take a look at DS to see where
> that might fit in. To get a feel, I had BndTools create a component
> bundle and tweaked things a bit so that it should run in Karaf 4.0.5
> as BndTools appears to be anticipating OSGi R6 support. I changed the
> build to reference osgi.cmpn; version=5.0 for example.
>
That should be no issue. Karaf includes scr 2 which supports the newest
DS spec.
>
> When I deploy the bundle, the resolver complains about not being able
> to satisfy the package requirement: org.osgi.service.component -
> version [1.2-2.0). Ive looked at the manifest and verified that the
> package is actually imported so Im at a loss. The component code and
> actual bundle manifest are shown below, for completeness. Any
> thoughts on what might be going on would be appreciated.
>
I guess you simply forgot to install the scr feature.
Christian
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
Re: Can't resolve org.osgi.service.component 1.2 ?
Posted by Christian Schneider <ch...@die-schneider.net>.
This also happened to me a lot.
If you use the current 6.0.0 OSGi specs and the maven-bundle-plugin 3.0.0
it will automatically create a Requirement for the DS extender.
If you then install your application using a feature then karaf will
complain if the DS extender is missing.
This does not work though if you install individual bundles.
For a complete example see:
https://github.com/cschneider/Karaf-Tutorial/tree/master/tasklist-ds
Christian
2016-05-13 18:15 GMT+02:00 Leschke, Scott <SL...@medline.com>:
> OK, it’s official, I’m an idiot. You’d think I could have figured that out
> on my own. I have a script that configures Karaf when I upgrade. Since
> I’ve been using Blueprint prior to this I’ve never had to install it before
> so I missed that. Thanks so much.
>
>
>
> BTW, just want to tell everyone involved in both Karaf and BndTools what a
> great job both teams have done. Truly excellent work all the way around.
>
>
>
> *From:* Achim Nierbeck [mailto:bcanhome@googlemail.com]
> *Sent:* Friday, May 13, 2016 10:57 AM
> *To:* user@karaf.apache.org
> *Subject:* Re: Can't resolve org.osgi.service.component 1.2 ?
>
>
>
> Hi,
>
>
>
> did you also install the scr feature, and did you make sure it's actually
> the required version ;)
>
>
>
> regards, Achim
>
>
>
>
>
> 2016-05-13 17:51 GMT+02:00 Leschke, Scott <SL...@medline.com>:
>
> Hi all,
>
>
>
> I’ve been messing around with OSGi and Karaf for a bit over 2 years now.
> Technically I’m no longer a developer, although if you want to get stuff
> done, sometimes you just have to do it yourself. I’ve built a BAM (Business
> Activity Monitoring) platform using OSGi (I wasn’t aware of Decanter when I
> originally did this but it sounds very similar in many ways. Looking more
> closely at that is a future).
>
>
>
> To date, I’ve done everything using Blueprint which has worked quite well
> but I thought it might be time to take a look at DS to see where that might
> fit in. To get a feel, I had BndTools create a component bundle and tweaked
> things a bit so that it should run in Karaf 4.0.5 as BndTools appears to be
> anticipating OSGi R6 support. I changed the build to reference osgi.cmpn;
> version=5.0 for example.
>
>
>
> When I deploy the bundle, the resolver complains about not being able to
> satisfy the package requirement: org.osgi.service.component - version
> [1.2-2.0). I’ve looked at the manifest and verified that the package is
> actually imported so I’m at a loss. The component code and actual bundle
> manifest are shown below, for completeness. Any thoughts on what might be
> going on would be appreciated.
>
>
>
> Regards, Scott
>
>
>
>
>
> *Manifest-Version: 1.0*
>
> *Bnd-LastModified: 1463152495066*
>
> *Bundle-ManifestVersion: 2*
>
> *Bundle-Name: zCompTest*
>
> *Bundle-SymbolicName: zCompTest*
>
> *Bundle-Version: 1.0.0.201605131514*
>
> *Created-By: 1.8.0_71 (Oracle Corporation)*
>
> *Export-Package: com.medline.zcomptest;version="1.0.0";uses:="org.osgi.*
>
> *service.component"*
>
> *Import-Package: org.osgi.service.component;version="[1.2,2)"*
>
> *Require-Capability: osgi.ee <http://osgi.ee>;filter:="(&(osgi.ee
> <http://osgi.ee>=JavaSE)(version=1.8))"*
>
> *Service-Component: OSGI-INF/com.medline.zcomptest.Example.xml*
>
> *Tool: Bnd-3.2.0.201605070046-SNAPSHOT*
>
>
>
>
>
> *import* org.osgi.service.component.ComponentContext;
>
> *import* org.osgi.service.component.annotations.Activate;
>
> *import* org.osgi.service.component.annotations.Component;
>
> *import* org.osgi.service.component.annotations.Deactivate;
>
>
>
> @Component(
>
> immediate = *true*
>
> )
>
> *public* *class* Example {
>
>
>
> @Activate
>
> *protected* *void* activate(ComponentContext c)
>
> {
>
> System.*out*.println("++ ACTIVATE");
>
> }
>
>
>
> @Deactivate
>
> *protected* *void* deactivate(ComponentContext c)
>
> {
>
> System.*out*.println("-- DEACTIVATE");
>
> }
>
> }
>
>
>
>
>
> --
>
>
> Apache Member
>
> Apache Karaf <http://karaf.apache.org/> Committer & PMC
> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
> Project Lead
> blog <http://notizblog.nierbeck.de/>
>
> Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>
>
>
>
> Software Architect / Project Manager / Scrum Master
>
>
>
--
--
Christian Schneider
http://www.liquid-reality.de
<https://owa.talend.com/owa/redir.aspx?C=3aa4083e0c744ae1ba52bd062c5a7e46&URL=http%3a%2f%2fwww.liquid-reality.de>
Open Source Architect
http://www.talend.com
<https://owa.talend.com/owa/redir.aspx?C=3aa4083e0c744ae1ba52bd062c5a7e46&URL=http%3a%2f%2fwww.talend.com>
Re: Can't resolve org.osgi.service.component 1.2 ?
Posted by Achim Nierbeck <bc...@googlemail.com>.
No reason to call yourself an idiot it's a common thing to forget about the
obvious ;)
aka "can't see the wood for the trees"
enjoy your weekend and best regards, Achim
2016-05-13 18:15 GMT+02:00 Leschke, Scott <SL...@medline.com>:
> OK, it’s official, I’m an idiot. You’d think I could have figured that out
> on my own. I have a script that configures Karaf when I upgrade. Since
> I’ve been using Blueprint prior to this I’ve never had to install it before
> so I missed that. Thanks so much.
>
>
>
> BTW, just want to tell everyone involved in both Karaf and BndTools what a
> great job both teams have done. Truly excellent work all the way around.
>
>
>
> *From:* Achim Nierbeck [mailto:bcanhome@googlemail.com]
> *Sent:* Friday, May 13, 2016 10:57 AM
> *To:* user@karaf.apache.org
> *Subject:* Re: Can't resolve org.osgi.service.component 1.2 ?
>
>
>
> Hi,
>
>
>
> did you also install the scr feature, and did you make sure it's actually
> the required version ;)
>
>
>
> regards, Achim
>
>
>
>
>
> 2016-05-13 17:51 GMT+02:00 Leschke, Scott <SL...@medline.com>:
>
> Hi all,
>
>
>
> I’ve been messing around with OSGi and Karaf for a bit over 2 years now.
> Technically I’m no longer a developer, although if you want to get stuff
> done, sometimes you just have to do it yourself. I’ve built a BAM (Business
> Activity Monitoring) platform using OSGi (I wasn’t aware of Decanter when I
> originally did this but it sounds very similar in many ways. Looking more
> closely at that is a future).
>
>
>
> To date, I’ve done everything using Blueprint which has worked quite well
> but I thought it might be time to take a look at DS to see where that might
> fit in. To get a feel, I had BndTools create a component bundle and tweaked
> things a bit so that it should run in Karaf 4.0.5 as BndTools appears to be
> anticipating OSGi R6 support. I changed the build to reference osgi.cmpn;
> version=5.0 for example.
>
>
>
> When I deploy the bundle, the resolver complains about not being able to
> satisfy the package requirement: org.osgi.service.component - version
> [1.2-2.0). I’ve looked at the manifest and verified that the package is
> actually imported so I’m at a loss. The component code and actual bundle
> manifest are shown below, for completeness. Any thoughts on what might be
> going on would be appreciated.
>
>
>
> Regards, Scott
>
>
>
>
>
> *Manifest-Version: 1.0*
>
> *Bnd-LastModified: 1463152495066*
>
> *Bundle-ManifestVersion: 2*
>
> *Bundle-Name: zCompTest*
>
> *Bundle-SymbolicName: zCompTest*
>
> *Bundle-Version: 1.0.0.201605131514*
>
> *Created-By: 1.8.0_71 (Oracle Corporation)*
>
> *Export-Package: com.medline.zcomptest;version="1.0.0";uses:="org.osgi.*
>
> *service.component"*
>
> *Import-Package: org.osgi.service.component;version="[1.2,2)"*
>
> *Require-Capability: osgi.ee <http://osgi.ee>;filter:="(&(osgi.ee
> <http://osgi.ee>=JavaSE)(version=1.8))"*
>
> *Service-Component: OSGI-INF/com.medline.zcomptest.Example.xml*
>
> *Tool: Bnd-3.2.0.201605070046-SNAPSHOT*
>
>
>
>
>
> *import* org.osgi.service.component.ComponentContext;
>
> *import* org.osgi.service.component.annotations.Activate;
>
> *import* org.osgi.service.component.annotations.Component;
>
> *import* org.osgi.service.component.annotations.Deactivate;
>
>
>
> @Component(
>
> immediate = *true*
>
> )
>
> *public* *class* Example {
>
>
>
> @Activate
>
> *protected* *void* activate(ComponentContext c)
>
> {
>
> System.*out*.println("++ ACTIVATE");
>
> }
>
>
>
> @Deactivate
>
> *protected* *void* deactivate(ComponentContext c)
>
> {
>
> System.*out*.println("-- DEACTIVATE");
>
> }
>
> }
>
>
>
>
>
> --
>
>
> Apache Member
>
> Apache Karaf <http://karaf.apache.org/> Committer & PMC
> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
> Project Lead
> blog <http://notizblog.nierbeck.de/>
>
> Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>
>
>
>
> Software Architect / Project Manager / Scrum Master
>
>
>
--
Apache Member
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
Project Lead
blog <http://notizblog.nierbeck.de/>
Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>
Software Architect / Project Manager / Scrum Master
Re: Can't resolve org.osgi.service.component 1.2 ?
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
I think it won't be so easy ;)
If the user deploys using a feature, then, we can check the requirements
and the feature resolver can raise a warning.
However, if the user deploys a bundle, we would need to add a
BundleListener to check the "non resolved" reqs.
Let me think about it a bit.
Regards
JB
On 05/18/2016 01:34 PM, Morgan Hautman wrote:
> Hi,
>
> I think what Christian mentioned "There could at least be a warning that
> a requirement is not fulfilled" is really good idea. Since that's the
> reason why I proposed to add the feature in the first place.
> I would be favorable on Christian's approach.
>
> Regards,
> Morgan
>
> On 2016-05-18 09:44, Christian Schneider wrote:
>> I do not consider myself stupid but I forgot the scr feature quite
>> often and wondered why my bundles do nothing :-)
>> So I think the requirement for the extender is an important part.
>>
>> I also wonder if we could check the requirements when doing simple
>> bundle installs. There could at least be a warning that a requirement
>> is not fulfilled. Currently the bundle installs and starts but does
>> not work and you see nothing in the logs.
>>
>> Christian
>>
>> On 18.05.2016 09:22, Jean-Baptiste Onofr� wrote:
>>> I agree with Christian: honestly, I don't think installing SCR
>>> feature by default is a good idea, and I would also remove blueprint
>>> feature by default (it's already planned for Karaf 4.1.x).
>>>
>>> Users are not stupid: when they use @Component, they know they use
>>> DS/SCR, so they need they relay on the scr feature. The same when
>>> they use a blueprint XML.
>>>
>>> Regards
>>> JB
>>
>
--
Jean-Baptiste Onofr�
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: Can't resolve org.osgi.service.component 1.2 ?
Posted by Morgan Hautman <mo...@gmail.com>.
Hi,
I think what Christian mentioned "There could at least be a warning that
a requirement is not fulfilled" is really good idea. Since that's the
reason why I proposed to add the feature in the first place.
I would be favorable on Christian's approach.
Regards,
Morgan
On 2016-05-18 09:44, Christian Schneider wrote:
> I do not consider myself stupid but I forgot the scr feature quite
> often and wondered why my bundles do nothing :-)
> So I think the requirement for the extender is an important part.
>
> I also wonder if we could check the requirements when doing simple
> bundle installs. There could at least be a warning that a requirement
> is not fulfilled. Currently the bundle installs and starts but does
> not work and you see nothing in the logs.
>
> Christian
>
> On 18.05.2016 09:22, Jean-Baptiste Onofr� wrote:
>> I agree with Christian: honestly, I don't think installing SCR
>> feature by default is a good idea, and I would also remove blueprint
>> feature by default (it's already planned for Karaf 4.1.x).
>>
>> Users are not stupid: when they use @Component, they know they use
>> DS/SCR, so they need they relay on the scr feature. The same when
>> they use a blueprint XML.
>>
>> Regards
>> JB
>
Re: Can't resolve org.osgi.service.component 1.2 ?
Posted by Christian Schneider <ch...@die-schneider.net>.
I do not consider myself stupid but I forgot the scr feature quite often
and wondered why my bundles do nothing :-)
So I think the requirement for the extender is an important part.
I also wonder if we could check the requirements when doing simple
bundle installs. There could at least be a warning that a requirement is
not fulfilled. Currently the bundle installs and starts but does not
work and you see nothing in the logs.
Christian
On 18.05.2016 09:22, Jean-Baptiste Onofr� wrote:
> I agree with Christian: honestly, I don't think installing SCR feature
> by default is a good idea, and I would also remove blueprint feature
> by default (it's already planned for Karaf 4.1.x).
>
> Users are not stupid: when they use @Component, they know they use
> DS/SCR, so they need they relay on the scr feature. The same when they
> use a blueprint XML.
>
> Regards
> JB
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
Re: Can't resolve org.osgi.service.component 1.2 ?
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
I agree with Christian: honestly, I don't think installing SCR feature
by default is a good idea, and I would also remove blueprint feature by
default (it's already planned for Karaf 4.1.x).
Users are not stupid: when they use @Component, they know they use
DS/SCR, so they need they relay on the scr feature. The same when they
use a blueprint XML.
Regards
JB
On 05/18/2016 09:02 AM, Christian Schneider wrote:
> As we have decided to not build karaf on top of DS I also think that
> installing DS by default is not a good idea.
> If we make sure the user bundles will have the requirement for the DS
> extender then karaf will give an early warning that DS is missing. So
> that should be good enough in my opinion.
>
> Christian
>
> On 14.05.2016 12:12, Achim Nierbeck wrote:
>> I'm not a big fan of that, cause actually blueprint isn't a default
>> feature anymore either.
>>
>> regards, Achim
>>
>>
>> 2016-05-14 8:49 GMT+02:00 Morgan Hautman <morgan.hautman@gmail.com
>> <ma...@gmail.com>>:
>>
>> Hi,
>>
>> That's one of the reasons why I proposed to put the "scr" feature
>> in the default build of Karaf..
>> Because usually people forget or don't know they need to install
>> the "scr" feature.
>> I don't know if this has already been done or if there is a Jira
>> to track it?
>>
>> Regards,
>> Morgan
>>
>>
>>
>> On 2016-05-13 18:15, Leschke, Scott wrote:
>>>
>>> OK, it\u2019s official, I\u2019m an idiot. You\u2019d think I could have figured
>>> that out on my own. I have a script that configures Karaf when I
>>> upgrade. Since I\u2019ve been using Blueprint prior to this I\u2019ve never
>>> had to install it before so I missed that. Thanks so much.
>>>
>>> BTW, just want to tell everyone involved in both Karaf and
>>> BndTools what a great job both teams have done. Truly excellent
>>> work all the way around.
>>>
>>> *From:*Achim Nierbeck [mailto:bcanhome@googlemail.com]
>>> *Sent:* Friday, May 13, 2016 10:57 AM
>>> *To:* user@karaf.apache.org <ma...@karaf.apache.org>
>>> *Subject:* Re: Can't resolve org.osgi.service.component 1.2 ?
>>>
>>> Hi,
>>>
>>> did you also install the scr feature, and did you make sure it's
>>> actually the required version ;)
>>>
>>> regards, Achim
>>>
>>> 2016-05-13 17:51 GMT+02:00 Leschke, Scott
>>> <<m...@medline.com>:
>>>
>>> Hi all,
>>>
>>> I\u2019ve been messing around with OSGi and Karaf for a bit over 2
>>> years now. Technically I\u2019m no longer a developer, although if
>>> you want to get stuff done, sometimes you just have to do it
>>> yourself. I\u2019ve built a BAM (Business Activity Monitoring)
>>> platform using OSGi (I wasn\u2019t aware of Decanter when I
>>> originally did this but it sounds very similar in many ways.
>>> Looking more closely at that is a future).
>>>
>>> To date, I\u2019ve done everything using Blueprint which has
>>> worked quite well but I thought it might be time to take a
>>> look at DS to see where that might fit in. To get a feel, I
>>> had BndTools create a component bundle and tweaked things a
>>> bit so that it should run in Karaf 4.0.5 as BndTools appears
>>> to be anticipating OSGi R6 support. I changed the build to
>>> reference osgi.cmpn; version=5.0 for example.
>>>
>>> When I deploy the bundle, the resolver complains about not
>>> being able to satisfy the package requirement:
>>> org.osgi.service.component - version [1.2-2.0). I\u2019ve looked
>>> at the manifest and verified that the package is actually
>>> imported so I\u2019m at a loss. The component code and actual
>>> bundle manifest are shown below, for completeness. Any
>>> thoughts on what might be going on would be appreciated.
>>>
>>> Regards, Scott
>>>
>>> **
>>>
>>> **
>>>
>>> *Manifest-Version: 1.0*
>>>
>>> *Bnd-LastModified: 1463152495066*
>>>
>>> *Bundle-ManifestVersion: 2*
>>>
>>> *Bundle-Name: zCompTest*
>>>
>>> *Bundle-SymbolicName: zCompTest*
>>>
>>> *Bundle-Version: 1.0.0.201605131514*
>>>
>>> *Created-By: 1.8.0_71 (Oracle Corporation)*
>>>
>>> *Export-Package:
>>> com.medline.zcomptest;version="1.0.0";uses:="org.osgi.*
>>>
>>> *service.component"*
>>>
>>> *Import-Package: org.osgi.service.component;version="[1.2,2)"*
>>>
>>> *Require-Capability: osgi.ee
>>> <http://osgi.ee>;filter:="(&(osgi.ee
>>> <http://osgi.ee>=JavaSE)(version=1.8))"*
>>>
>>> *Service-Component: OSGI-INF/com.medline.zcomptest.Example.xml*
>>>
>>> *Tool: Bnd-3.2.0.201605070046-SNAPSHOT*
>>>
>>> **
>>>
>>> **
>>>
>>> *import*org.osgi.service.component.ComponentContext;
>>>
>>> *import*org.osgi.service.component.annotations.Activate;
>>>
>>> *import*org.osgi.service.component.annotations.Component;
>>>
>>> *import*org.osgi.service.component.annotations.Deactivate;
>>>
>>> @Component(
>>>
>>> immediate = *true*
>>>
>>> )
>>>
>>> *public**class*Example {
>>>
>>> @Activate
>>>
>>> *protected**void*activate(ComponentContext c)
>>>
>>> {
>>>
>>> System.*/out/*.println("++ ACTIVATE");
>>>
>>> }
>>>
>>> @Deactivate
>>>
>>> *protected**void*deactivate(ComponentContext c)
>>>
>>> {
>>>
>>> System.*/out/*.println("-- DEACTIVATE");
>>>
>>> }
>>>
>>> }
>>>
>>>
>>>
>>> --
>>>
>>>
>>> Apache Member
>>>
>>> Apache Karaf <<http://karaf.apache.org/>http://karaf.apache.org/>
>>> Committer & PMC
>>> OPS4J Pax Web
>>> <<http://wiki.ops4j.org/display/paxweb/Pax+Web/>http://wiki.ops4j.org/display/paxweb/Pax+Web/>
>>> Committer & Project Lead
>>> blog <http://notizblog.nierbeck.de/>
>>>
>>> Co-Author of Apache Karaf Cookbook
>>> <<http://bit.ly/1ps9rkS>http://bit.ly/1ps9rkS>
>>>
>>> Software Architect / Project Manager / Scrum Master
>>>
>>
>>
>>
>>
>> --
>>
>> Apache Member
>> Apache Karaf <http://karaf.apache.org/> Committer & PMC
>> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/>
>> Committer & Project Lead
>> blog <http://notizblog.nierbeck.de/>
>> Co-Author of Apache Karaf Cookbook
>> <<http://bit.ly/1ps9rkS>http://bit.ly/1ps9rkS>
>>
>> Software Architect / Project Manager / Scrum Master
>>
>
>
> --
> Christian Schneider
> http://www.liquid-reality.de
>
> Open Source Architect
> http://www.talend.com
>
--
Jean-Baptiste Onofr�
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: Can't resolve org.osgi.service.component 1.2 ?
Posted by Christian Schneider <ch...@die-schneider.net>.
As we have decided to not build karaf on top of DS I also think that
installing DS by default is not a good idea.
If we make sure the user bundles will have the requirement for the DS
extender then karaf will give an early warning that DS is missing. So
that should be good enough in my opinion.
Christian
On 14.05.2016 12:12, Achim Nierbeck wrote:
> I'm not a big fan of that, cause actually blueprint isn't a default
> feature anymore either.
>
> regards, Achim
>
>
> 2016-05-14 8:49 GMT+02:00 Morgan Hautman <morgan.hautman@gmail.com
> <ma...@gmail.com>>:
>
> Hi,
>
> That's one of the reasons why I proposed to put the "scr" feature
> in the default build of Karaf..
> Because usually people forget or don't know they need to install
> the "scr" feature.
> I don't know if this has already been done or if there is a Jira
> to track it?
>
> Regards,
> Morgan
>
>
>
> On 2016-05-13 18:15, Leschke, Scott wrote:
>>
>> OK, it\u2019s official, I\u2019m an idiot. You\u2019d think I could have figured
>> that out on my own. I have a script that configures Karaf when I
>> upgrade. Since I\u2019ve been using Blueprint prior to this I\u2019ve never
>> had to install it before so I missed that. Thanks so much.
>>
>> BTW, just want to tell everyone involved in both Karaf and
>> BndTools what a great job both teams have done. Truly excellent
>> work all the way around.
>>
>> *From:*Achim Nierbeck [mailto:bcanhome@googlemail.com]
>> *Sent:* Friday, May 13, 2016 10:57 AM
>> *To:* user@karaf.apache.org <ma...@karaf.apache.org>
>> *Subject:* Re: Can't resolve org.osgi.service.component 1.2 ?
>>
>> Hi,
>>
>> did you also install the scr feature, and did you make sure it's
>> actually the required version ;)
>>
>> regards, Achim
>>
>> 2016-05-13 17:51 GMT+02:00 Leschke, Scott <SLeschke@medline.com
>> <ma...@medline.com>>:
>>
>> Hi all,
>>
>> I\u2019ve been messing around with OSGi and Karaf for a bit over 2
>> years now. Technically I\u2019m no longer a developer, although if
>> you want to get stuff done, sometimes you just have to do it
>> yourself. I\u2019ve built a BAM (Business Activity Monitoring)
>> platform using OSGi (I wasn\u2019t aware of Decanter when I
>> originally did this but it sounds very similar in many ways.
>> Looking more closely at that is a future).
>>
>> To date, I\u2019ve done everything using Blueprint which has
>> worked quite well but I thought it might be time to take a
>> look at DS to see where that might fit in. To get a feel, I
>> had BndTools create a component bundle and tweaked things a
>> bit so that it should run in Karaf 4.0.5 as BndTools appears
>> to be anticipating OSGi R6 support. I changed the build to
>> reference osgi.cmpn; version=5.0 for example.
>>
>> When I deploy the bundle, the resolver complains about not
>> being able to satisfy the package requirement:
>> org.osgi.service.component - version [1.2-2.0). I\u2019ve looked
>> at the manifest and verified that the package is actually
>> imported so I\u2019m at a loss. The component code and actual
>> bundle manifest are shown below, for completeness. Any
>> thoughts on what might be going on would be appreciated.
>>
>> Regards, Scott
>>
>> **
>>
>> **
>>
>> *Manifest-Version: 1.0*
>>
>> *Bnd-LastModified: 1463152495066*
>>
>> *Bundle-ManifestVersion: 2*
>>
>> *Bundle-Name: zCompTest*
>>
>> *Bundle-SymbolicName: zCompTest*
>>
>> *Bundle-Version: 1.0.0.201605131514*
>>
>> *Created-By: 1.8.0_71 (Oracle Corporation)*
>>
>> *Export-Package:
>> com.medline.zcomptest;version="1.0.0";uses:="org.osgi.*
>>
>> *service.component"*
>>
>> *Import-Package: org.osgi.service.component;version="[1.2,2)"*
>>
>> *Require-Capability: osgi.ee
>> <http://osgi.ee>;filter:="(&(osgi.ee
>> <http://osgi.ee>=JavaSE)(version=1.8))"*
>>
>> *Service-Component: OSGI-INF/com.medline.zcomptest.Example.xml*
>>
>> *Tool: Bnd-3.2.0.201605070046-SNAPSHOT*
>>
>> **
>>
>> **
>>
>> *import*org.osgi.service.component.ComponentContext;
>>
>> *import*org.osgi.service.component.annotations.Activate;
>>
>> *import*org.osgi.service.component.annotations.Component;
>>
>> *import*org.osgi.service.component.annotations.Deactivate;
>>
>> @Component(
>>
>> immediate = *true*
>>
>> )
>>
>> *public**class*Example {
>>
>> @Activate
>>
>> *protected**void*activate(ComponentContext c)
>>
>> {
>>
>> System.*/out/*.println("++ ACTIVATE");
>>
>> }
>>
>> @Deactivate
>>
>> *protected**void*deactivate(ComponentContext c)
>>
>> {
>>
>> System.*/out/*.println("-- DEACTIVATE");
>>
>> }
>>
>> }
>>
>>
>>
>> --
>>
>>
>> Apache Member
>>
>> Apache Karaf <http://karaf.apache.org/> Committer & PMC
>> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/>
>> Committer & Project Lead
>> blog <http://notizblog.nierbeck.de/>
>>
>> Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>
>>
>> Software Architect / Project Manager / Scrum Master
>>
>
>
>
>
> --
>
> Apache Member
> Apache Karaf <http://karaf.apache.org/> Committer & PMC
> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/>
> Committer & Project Lead
> blog <http://notizblog.nierbeck.de/>
> Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>
>
> Software Architect / Project Manager / Scrum Master
>
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
Re: Can't resolve org.osgi.service.component 1.2 ?
Posted by Achim Nierbeck <bc...@googlemail.com>.
I'm not a big fan of that, cause actually blueprint isn't a default feature
anymore either.
regards, Achim
2016-05-14 8:49 GMT+02:00 Morgan Hautman <mo...@gmail.com>:
> Hi,
>
> That's one of the reasons why I proposed to put the "scr" feature in the
> default build of Karaf..
> Because usually people forget or don't know they need to install the "scr"
> feature.
> I don't know if this has already been done or if there is a Jira to track
> it?
>
> Regards,
> Morgan
>
>
>
> On 2016-05-13 18:15, Leschke, Scott wrote:
>
> OK, it’s official, I’m an idiot. You’d think I could have figured that out
> on my own. I have a script that configures Karaf when I upgrade. Since
> I’ve been using Blueprint prior to this I’ve never had to install it before
> so I missed that. Thanks so much.
>
>
>
> BTW, just want to tell everyone involved in both Karaf and BndTools what a
> great job both teams have done. Truly excellent work all the way around.
>
>
>
> *From:* Achim Nierbeck [mailto:bcanhome@googlemail.com
> <bc...@googlemail.com>]
> *Sent:* Friday, May 13, 2016 10:57 AM
> *To:* user@karaf.apache.org
> *Subject:* Re: Can't resolve org.osgi.service.component 1.2 ?
>
>
>
> Hi,
>
>
>
> did you also install the scr feature, and did you make sure it's actually
> the required version ;)
>
>
>
> regards, Achim
>
>
>
>
>
> 2016-05-13 17:51 GMT+02:00 Leschke, Scott <SL...@medline.com>:
>
> Hi all,
>
>
>
> I’ve been messing around with OSGi and Karaf for a bit over 2 years now.
> Technically I’m no longer a developer, although if you want to get stuff
> done, sometimes you just have to do it yourself. I’ve built a BAM (Business
> Activity Monitoring) platform using OSGi (I wasn’t aware of Decanter when I
> originally did this but it sounds very similar in many ways. Looking more
> closely at that is a future).
>
>
>
> To date, I’ve done everything using Blueprint which has worked quite well
> but I thought it might be time to take a look at DS to see where that might
> fit in. To get a feel, I had BndTools create a component bundle and tweaked
> things a bit so that it should run in Karaf 4.0.5 as BndTools appears to be
> anticipating OSGi R6 support. I changed the build to reference osgi.cmpn;
> version=5.0 for example.
>
>
>
> When I deploy the bundle, the resolver complains about not being able to
> satisfy the package requirement: org.osgi.service.component - version
> [1.2-2.0). I’ve looked at the manifest and verified that the package is
> actually imported so I’m at a loss. The component code and actual bundle
> manifest are shown below, for completeness. Any thoughts on what might be
> going on would be appreciated.
>
>
>
> Regards, Scott
>
>
>
>
>
> *Manifest-Version: 1.0*
>
> *Bnd-LastModified: 1463152495066*
>
> *Bundle-ManifestVersion: 2*
>
> *Bundle-Name: zCompTest*
>
> *Bundle-SymbolicName: zCompTest*
>
> *Bundle-Version: 1.0.0.201605131514*
>
> *Created-By: 1.8.0_71 (Oracle Corporation)*
>
> *Export-Package: com.medline.zcomptest;version="1.0.0";uses:="org.osgi.*
>
> *service.component"*
>
> *Import-Package: org.osgi.service.component;version="[1.2,2)"*
>
> *Require-Capability: osgi.ee <http://osgi.ee>;filter:="(&(osgi.ee
> <http://osgi.ee>=JavaSE)(version=1.8))"*
>
> *Service-Component: OSGI-INF/com.medline.zcomptest.Example.xml*
>
> *Tool: Bnd-3.2.0.201605070046-SNAPSHOT*
>
>
>
>
>
> *import* org.osgi.service.component.ComponentContext;
>
> *import* org.osgi.service.component.annotations.Activate;
>
> *import* org.osgi.service.component.annotations.Component;
>
> *import* org.osgi.service.component.annotations.Deactivate;
>
>
>
> @Component(
>
> immediate = *true*
>
> )
>
> *public* *class* Example {
>
>
>
> @Activate
>
> *protected* *void* activate(ComponentContext c)
>
> {
>
> System.*out*.println("++ ACTIVATE");
>
> }
>
>
>
> @Deactivate
>
> *protected* *void* deactivate(ComponentContext c)
>
> {
>
> System.*out*.println("-- DEACTIVATE");
>
> }
>
> }
>
>
>
>
>
> --
>
>
> Apache Member
>
> Apache Karaf < <http://karaf.apache.org/>http://karaf.apache.org/>
> Committer & PMC
> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
> Project Lead
> blog <http://notizblog.nierbeck.de/>
>
> Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>
>
>
>
> Software Architect / Project Manager / Scrum Master
>
>
>
>
>
--
Apache Member
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
Project Lead
blog <http://notizblog.nierbeck.de/>
Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>
Software Architect / Project Manager / Scrum Master
Re: Can't resolve org.osgi.service.component 1.2 ?
Posted by Morgan Hautman <mo...@gmail.com>.
Hi,
That's one of the reasons why I proposed to put the "scr" feature in the
default build of Karaf..
Because usually people forget or don't know they need to install the
"scr" feature.
I don't know if this has already been done or if there is a Jira to
track it?
Regards,
Morgan
On 2016-05-13 18:15, Leschke, Scott wrote:
>
> OK, it\u2019s official, I\u2019m an idiot. You\u2019d think I could have figured that
> out on my own. I have a script that configures Karaf when I upgrade.
> Since I\u2019ve been using Blueprint prior to this I\u2019ve never had to
> install it before so I missed that. Thanks so much.
>
> BTW, just want to tell everyone involved in both Karaf and BndTools
> what a great job both teams have done. Truly excellent work all the
> way around.
>
> *From:*Achim Nierbeck [mailto:bcanhome@googlemail.com]
> *Sent:* Friday, May 13, 2016 10:57 AM
> *To:* user@karaf.apache.org
> *Subject:* Re: Can't resolve org.osgi.service.component 1.2 ?
>
> Hi,
>
> did you also install the scr feature, and did you make sure it's
> actually the required version ;)
>
> regards, Achim
>
> 2016-05-13 17:51 GMT+02:00 Leschke, Scott <SLeschke@medline.com
> <ma...@medline.com>>:
>
> Hi all,
>
> I\u2019ve been messing around with OSGi and Karaf for a bit over 2
> years now. Technically I\u2019m no longer a developer, although if you
> want to get stuff done, sometimes you just have to do it yourself.
> I\u2019ve built a BAM (Business Activity Monitoring) platform using
> OSGi (I wasn\u2019t aware of Decanter when I originally did this but it
> sounds very similar in many ways. Looking more closely at that is
> a future).
>
> To date, I\u2019ve done everything using Blueprint which has worked
> quite well but I thought it might be time to take a look at DS to
> see where that might fit in. To get a feel, I had BndTools create
> a component bundle and tweaked things a bit so that it should run
> in Karaf 4.0.5 as BndTools appears to be anticipating OSGi R6
> support. I changed the build to reference osgi.cmpn; version=5.0
> for example.
>
> When I deploy the bundle, the resolver complains about not being
> able to satisfy the package requirement:
> org.osgi.service.component - version [1.2-2.0). I\u2019ve looked at the
> manifest and verified that the package is actually imported so I\u2019m
> at a loss. The component code and actual bundle manifest are shown
> below, for completeness. Any thoughts on what might be going on
> would be appreciated.
>
> Regards, Scott
>
> **
>
> **
>
> *Manifest-Version: 1.0*
>
> *Bnd-LastModified: 1463152495066*
>
> *Bundle-ManifestVersion: 2*
>
> *Bundle-Name: zCompTest*
>
> *Bundle-SymbolicName: zCompTest*
>
> *Bundle-Version: 1.0.0.201605131514*
>
> *Created-By: 1.8.0_71 (Oracle Corporation)*
>
> *Export-Package:
> com.medline.zcomptest;version="1.0.0";uses:="org.osgi.*
>
> *service.component"*
>
> *Import-Package: org.osgi.service.component;version="[1.2,2)"*
>
> *Require-Capability: osgi.ee <http://osgi.ee>;filter:="(&(osgi.ee
> <http://osgi.ee>=JavaSE)(version=1.8))"*
>
> *Service-Component: OSGI-INF/com.medline.zcomptest.Example.xml*
>
> *Tool: Bnd-3.2.0.201605070046-SNAPSHOT*
>
> **
>
> **
>
> *import*org.osgi.service.component.ComponentContext;
>
> *import*org.osgi.service.component.annotations.Activate;
>
> *import*org.osgi.service.component.annotations.Component;
>
> *import*org.osgi.service.component.annotations.Deactivate;
>
> @Component(
>
> immediate = *true*
>
> )
>
> *public**class*Example {
>
> @Activate
>
> *protected**void*activate(ComponentContext c)
>
> {
>
> System.*/out/*.println("++ ACTIVATE");
>
> }
>
> @Deactivate
>
> *protected**void*deactivate(ComponentContext c)
>
> {
>
> System.*/out/*.println("-- DEACTIVATE");
>
> }
>
> }
>
>
>
> --
>
>
> Apache Member
>
> Apache Karaf <http://karaf.apache.org/> Committer & PMC
> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/>
> Committer & Project Lead
> blog <http://notizblog.nierbeck.de/>
>
> Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>
>
> Software Architect / Project Manager / Scrum Master
>
RE: Can't resolve org.osgi.service.component 1.2 ?
Posted by "Leschke, Scott" <SL...@medline.com>.
OK, it’s official, I’m an idiot. You’d think I could have figured that out on my own. I have a script that configures Karaf when I upgrade. Since I’ve been using Blueprint prior to this I’ve never had to install it before so I missed that. Thanks so much.
BTW, just want to tell everyone involved in both Karaf and BndTools what a great job both teams have done. Truly excellent work all the way around.
From: Achim Nierbeck [mailto:bcanhome@googlemail.com]
Sent: Friday, May 13, 2016 10:57 AM
To: user@karaf.apache.org
Subject: Re: Can't resolve org.osgi.service.component 1.2 ?
Hi,
did you also install the scr feature, and did you make sure it's actually the required version ;)
regards, Achim
2016-05-13 17:51 GMT+02:00 Leschke, Scott <SL...@medline.com>>:
Hi all,
I’ve been messing around with OSGi and Karaf for a bit over 2 years now. Technically I’m no longer a developer, although if you want to get stuff done, sometimes you just have to do it yourself. I’ve built a BAM (Business Activity Monitoring) platform using OSGi (I wasn’t aware of Decanter when I originally did this but it sounds very similar in many ways. Looking more closely at that is a future).
To date, I’ve done everything using Blueprint which has worked quite well but I thought it might be time to take a look at DS to see where that might fit in. To get a feel, I had BndTools create a component bundle and tweaked things a bit so that it should run in Karaf 4.0.5 as BndTools appears to be anticipating OSGi R6 support. I changed the build to reference osgi.cmpn; version=5.0 for example.
When I deploy the bundle, the resolver complains about not being able to satisfy the package requirement: org.osgi.service.component - version [1.2-2.0). I’ve looked at the manifest and verified that the package is actually imported so I’m at a loss. The component code and actual bundle manifest are shown below, for completeness. Any thoughts on what might be going on would be appreciated.
Regards, Scott
Manifest-Version: 1.0
Bnd-LastModified: 1463152495066
Bundle-ManifestVersion: 2
Bundle-Name: zCompTest
Bundle-SymbolicName: zCompTest
Bundle-Version: 1.0.0.201605131514
Created-By: 1.8.0_71 (Oracle Corporation)
Export-Package: com.medline.zcomptest;version="1.0.0";uses:="org.osgi.
service.component"
Import-Package: org.osgi.service.component;version="[1.2,2)"
Require-Capability: osgi.ee<http://osgi.ee>;filter:="(&(osgi.ee<http://osgi.ee>=JavaSE)(version=1.8))"
Service-Component: OSGI-INF/com.medline.zcomptest.Example.xml
Tool: Bnd-3.2.0.201605070046-SNAPSHOT
import org.osgi.service.component.ComponentContext;
import org.osgi.service.component.annotations.Activate;
import org.osgi.service.component.annotations.Component;
import org.osgi.service.component.annotations.Deactivate;
@Component(
immediate = true
)
public class Example {
@Activate
protected void activate(ComponentContext c)
{
System.out.println("++ ACTIVATE");
}
@Deactivate
protected void deactivate(ComponentContext c)
{
System.out.println("-- DEACTIVATE");
}
}
--
Apache Member
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead
blog <http://notizblog.nierbeck.de/>
Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>
Software Architect / Project Manager / Scrum Master
Re: Can't resolve org.osgi.service.component 1.2 ?
Posted by Achim Nierbeck <bc...@googlemail.com>.
Hi,
did you also install the scr feature, and did you make sure it's actually
the required version ;)
regards, Achim
2016-05-13 17:51 GMT+02:00 Leschke, Scott <SL...@medline.com>:
> Hi all,
>
>
>
> I’ve been messing around with OSGi and Karaf for a bit over 2 years now.
> Technically I’m no longer a developer, although if you want to get stuff
> done, sometimes you just have to do it yourself. I’ve built a BAM (Business
> Activity Monitoring) platform using OSGi (I wasn’t aware of Decanter when I
> originally did this but it sounds very similar in many ways. Looking more
> closely at that is a future).
>
>
>
> To date, I’ve done everything using Blueprint which has worked quite well
> but I thought it might be time to take a look at DS to see where that might
> fit in. To get a feel, I had BndTools create a component bundle and tweaked
> things a bit so that it should run in Karaf 4.0.5 as BndTools appears to be
> anticipating OSGi R6 support. I changed the build to reference osgi.cmpn;
> version=5.0 for example.
>
>
>
> When I deploy the bundle, the resolver complains about not being able to
> satisfy the package requirement: org.osgi.service.component - version
> [1.2-2.0). I’ve looked at the manifest and verified that the package is
> actually imported so I’m at a loss. The component code and actual bundle
> manifest are shown below, for completeness. Any thoughts on what might be
> going on would be appreciated.
>
>
>
> Regards, Scott
>
>
>
>
>
> *Manifest-Version: 1.0*
>
> *Bnd-LastModified: 1463152495066*
>
> *Bundle-ManifestVersion: 2*
>
> *Bundle-Name: zCompTest*
>
> *Bundle-SymbolicName: zCompTest*
>
> *Bundle-Version: 1.0.0.201605131514*
>
> *Created-By: 1.8.0_71 (Oracle Corporation)*
>
> *Export-Package: com.medline.zcomptest;version="1.0.0";uses:="org.osgi.*
>
> *service.component"*
>
> *Import-Package: org.osgi.service.component;version="[1.2,2)"*
>
> *Require-Capability: osgi.ee <http://osgi.ee>;filter:="(&(osgi.ee
> <http://osgi.ee>=JavaSE)(version=1.8))"*
>
> *Service-Component: OSGI-INF/com.medline.zcomptest.Example.xml*
>
> *Tool: Bnd-3.2.0.201605070046-SNAPSHOT*
>
>
>
>
>
> *import* org.osgi.service.component.ComponentContext;
>
> *import* org.osgi.service.component.annotations.Activate;
>
> *import* org.osgi.service.component.annotations.Component;
>
> *import* org.osgi.service.component.annotations.Deactivate;
>
>
>
> @Component(
>
> immediate = *true*
>
> )
>
> *public* *class* Example {
>
>
>
> @Activate
>
> *protected* *void* activate(ComponentContext c)
>
> {
>
> System.*out*.println("++ ACTIVATE");
>
> }
>
>
>
> @Deactivate
>
> *protected* *void* deactivate(ComponentContext c)
>
> {
>
> System.*out*.println("-- DEACTIVATE");
>
> }
>
> }
>
--
Apache Member
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
Project Lead
blog <http://notizblog.nierbeck.de/>
Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>
Software Architect / Project Manager / Scrum Master