You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@karaf.apache.org by Scott England-Sullivan <su...@gmail.com> on 2012/07/24 18:23:42 UTC
Adding Webconsole Plugin for SCR
Hello,
The SCR plugin has now been separated from the base install of webconsole.
Given its dependency on two features, scr & webconsole, I was wondering
what would be the correct way to add it to the standard feature.xml?
* Stand alone feature with a dependency on webconsole and scr
* Stand alone feature with no dependency features
* Include in the webconsole feature and add dependency on the scr feature
* ???
Thanks,
Scott ES
--
--
Scott England-Sullivan
----------------------------------
FuseSource
Web: http://www.fusesource.com
Blog: http://sully6768.blogspot.com
Twitter: sully6768
Re: Adding Webconsole Plugin for SCR
Posted by Scott England-Sullivan <su...@gmail.com>.
Wow, and I am the SCR proponent around here and missed that. (doh!)
I haven't checked to see if the plugin provided by Felix actually works as
a DS component would be expected to. I can take a look at that to verify
if it was written that way and to see how it is resolving which should help
drive how to proceed.
On Wed, Jul 25, 2012 at 10:02 AM, David Jencks <da...@yahoo.com>wrote:
> I wonder i we're asking the right question here. We have something we
> want to "turn on" when a set of n other things are present. We're talking
> bundles which don't work that way. A more friendly model is DS services
> with mandatory references. If we say that the n other things are services
> rather than bundles, and the thing we want to turn on is also a service,
> then we can use DS to automatically do the detection and wiring and service
> creation/registration for us.
>
> If we installed a small bundle or two with a feature, that couldn't
> resolve until some other bundle(s) were also installed, would that be a
> problem? (or used dynamic import :-(((( )
>
> david jencks
>
> On Jul 25, 2012, at 8:13 AM, Scott England-Sullivan wrote:
>
> > Do you see the capability feature extension being able to handle the case
> > where say the web console feature s installed and then you add the event
> > admin feature, which the pax-web-runtime has an optional dependency on.
> If
> > you currently install event admin after web console you get a big nasty
> > stack trace in the console window.
> >
> > I guess what I would hope to avoid is feature soup. It would be very
> nice
> > to be able to define all the dependencies and capabilities of SCR under
> the
> > SCR feature. Then depending on the features that are installed in
> > addition to SCR, management and/or web console, those SCR "capabilities"
> > would be installed.
> >
> > Make sense?
> >
> > On Wed, Jul 25, 2012 at 3:49 AM, Ioannis Canellos <io...@gmail.com>
> wrote:
> >
> >>>
> >>> definitely +1; nevertheless I still think we can "marry" Achims
> >>> proposal together with this capability think; don't you think?
> >>
> >>
> >> Of course, I think that these 2 ideas are complimentary.
> >>
> >> --
> >> *Ioannis Canellos*
> >> *
> >> FuseSource <http://fusesource.com>
> >>
> >> **
> >> Blog: http://iocanel.blogspot.com
> >> **
> >> Twitter: iocanel
> >> *
> >>
> >
> >
> >
> > --
> > --
> > Scott England-Sullivan
> > ----------------------------------
> > FuseSource
> > Web: http://www.fusesource.com
> > Blog: http://sully6768.blogspot.com
> > Twitter: sully6768
>
>
--
--
Scott England-Sullivan
----------------------------------
FuseSource
Web: http://www.fusesource.com
Blog: http://sully6768.blogspot.com
Twitter: sully6768
Re: Adding Webconsole Plugin for SCR
Posted by David Jencks <da...@yahoo.com>.
I wonder i we're asking the right question here. We have something we want to "turn on" when a set of n other things are present. We're talking bundles which don't work that way. A more friendly model is DS services with mandatory references. If we say that the n other things are services rather than bundles, and the thing we want to turn on is also a service, then we can use DS to automatically do the detection and wiring and service creation/registration for us.
If we installed a small bundle or two with a feature, that couldn't resolve until some other bundle(s) were also installed, would that be a problem? (or used dynamic import :-(((( )
david jencks
On Jul 25, 2012, at 8:13 AM, Scott England-Sullivan wrote:
> Do you see the capability feature extension being able to handle the case
> where say the web console feature s installed and then you add the event
> admin feature, which the pax-web-runtime has an optional dependency on. If
> you currently install event admin after web console you get a big nasty
> stack trace in the console window.
>
> I guess what I would hope to avoid is feature soup. It would be very nice
> to be able to define all the dependencies and capabilities of SCR under the
> SCR feature. Then depending on the features that are installed in
> addition to SCR, management and/or web console, those SCR "capabilities"
> would be installed.
>
> Make sense?
>
> On Wed, Jul 25, 2012 at 3:49 AM, Ioannis Canellos <io...@gmail.com> wrote:
>
>>>
>>> definitely +1; nevertheless I still think we can "marry" Achims
>>> proposal together with this capability think; don't you think?
>>
>>
>> Of course, I think that these 2 ideas are complimentary.
>>
>> --
>> *Ioannis Canellos*
>> *
>> FuseSource <http://fusesource.com>
>>
>> **
>> Blog: http://iocanel.blogspot.com
>> **
>> Twitter: iocanel
>> *
>>
>
>
>
> --
> --
> Scott England-Sullivan
> ----------------------------------
> FuseSource
> Web: http://www.fusesource.com
> Blog: http://sully6768.blogspot.com
> Twitter: sully6768
Re: Adding Webconsole Plugin for SCR
Posted by Scott England-Sullivan <su...@gmail.com>.
Do you see the capability feature extension being able to handle the case
where say the web console feature s installed and then you add the event
admin feature, which the pax-web-runtime has an optional dependency on. If
you currently install event admin after web console you get a big nasty
stack trace in the console window.
I guess what I would hope to avoid is feature soup. It would be very nice
to be able to define all the dependencies and capabilities of SCR under the
SCR feature. Then depending on the features that are installed in
addition to SCR, management and/or web console, those SCR "capabilities"
would be installed.
Make sense?
On Wed, Jul 25, 2012 at 3:49 AM, Ioannis Canellos <io...@gmail.com> wrote:
> >
> > definitely +1; nevertheless I still think we can "marry" Achims
> > proposal together with this capability think; don't you think?
>
>
> Of course, I think that these 2 ideas are complimentary.
>
> --
> *Ioannis Canellos*
> *
> FuseSource <http://fusesource.com>
>
> **
> Blog: http://iocanel.blogspot.com
> **
> Twitter: iocanel
> *
>
--
--
Scott England-Sullivan
----------------------------------
FuseSource
Web: http://www.fusesource.com
Blog: http://sully6768.blogspot.com
Twitter: sully6768
Re: Adding Webconsole Plugin for SCR
Posted by Ioannis Canellos <io...@gmail.com>.
>
> definitely +1; nevertheless I still think we can "marry" Achims
> proposal together with this capability think; don't you think?
Of course, I think that these 2 ideas are complimentary.
--
*Ioannis Canellos*
*
FuseSource <http://fusesource.com>
**
Blog: http://iocanel.blogspot.com
**
Twitter: iocanel
*
Re: Adding Webconsole Plugin for SCR
Posted by Andreas Pieber <an...@gmail.com>.
definitely +1; nevertheless I still think we can "marry" Achims
proposal together with this capability think; don't you think?
Kind regards,
Andreas
On Wed, Jul 25, 2012 at 10:16 AM, Ioannis Canellos <io...@gmail.com> wrote:
> Hmmm, going through that thread again I realized that I misunderstood
> Achims proposal :-S I still like it but I don't feel that this will solve
> the current issue. I am still +1 for it, but for the current problem I was
> thinking for something like:
>
>
> <feature resolver="(obr)" description="Declarative Service support"
> version="3.0.0-SNAPSHOT"
> name="scr">
> ...
> <capability feature="webconsole">
> <bundle>mvn:org.apache.karaf.scr/org.apache.karaf.scr.webconsole.
> plugin/3.0.0-SNAPSHOT</bundle>
> </capability>
> </feature>
>
> Where capability could specify a feature (as shown above), a package, a
> service etc.
>
> When the scr feature gets installed, the feature service could check if the
> defined capability is meet in our container and if so install the
> webconsole plugin.
> Also, after a feature gets installed it could have a look at the existing
> installed features and see if there are new capabilities that are meet.
>
> I think that this would be really usefull, especially for the management,
> diagnostic, webconsole related features.
>
> --
> *Ioannis Canellos*
> *
> FuseSource <http://fusesource.com>
>
> **
> Blog: http://iocanel.blogspot.com
> **
> Twitter: iocanel
> *
Re: Adding Webconsole Plugin for SCR
Posted by Ioannis Canellos <io...@gmail.com>.
Hmmm, going through that thread again I realized that I misunderstood
Achims proposal :-S I still like it but I don't feel that this will solve
the current issue. I am still +1 for it, but for the current problem I was
thinking for something like:
<feature resolver="(obr)" description="Declarative Service support"
version="3.0.0-SNAPSHOT"
name="scr">
...
<capability feature="webconsole">
<bundle>mvn:org.apache.karaf.scr/org.apache.karaf.scr.webconsole.
plugin/3.0.0-SNAPSHOT</bundle>
</capability>
</feature>
Where capability could specify a feature (as shown above), a package, a
service etc.
When the scr feature gets installed, the feature service could check if the
defined capability is meet in our container and if so install the
webconsole plugin.
Also, after a feature gets installed it could have a look at the existing
installed features and see if there are new capabilities that are meet.
I think that this would be really usefull, especially for the management,
diagnostic, webconsole related features.
--
*Ioannis Canellos*
*
FuseSource <http://fusesource.com>
**
Blog: http://iocanel.blogspot.com
**
Twitter: iocanel
*
Re: Adding Webconsole Plugin for SCR
Posted by Andreas Pieber <an...@gmail.com>.
Oh, seams this one had been deleted from my mind :-)
Yeah, but you're right. Now that I'm reading over it again it comes
back nevertheless...
Independently, we'll need to extend the feature-fragment idea for this
specific case: The problem here is that the fragment should only be
installed IFF the SCR feature is already installed when the webconsole
is installed. Adding this somewhere in your initial proposal and I'm
fine with it :-)
Kind regards,
Andreas
On Wed, Jul 25, 2012 at 9:44 AM, Achim Nierbeck <bc...@googlemail.com> wrote:
> We had this discussion before and I opened a jira-issue for it :)
>
> The idea was to have like a bundle-fragment for features.
> So name it "feature-fragment" which attaches to a certain feature and
> does get installed when
> the "host" feature is installed. That's the quintessence of the idea :)
>
> Ok there wasn't a specific issue for it yet :/
> shame on me but it was somehow attached to another one [1]
> the discussion about it can be found here [2]
>
> regards, Achim
>
> [1] - https://issues.apache.org/jira/browse/KARAF-1017
> [2] - http://karaf.922171.n3.nabble.com/PROPOSAL-A-features-fragment-for-extending-external-Features-td3709287.html
>
> 2012/7/25 Andreas Pieber <an...@gmail.com>:
>> I'm afraid this wont be enough. For example there are very likely
>> features which you don't want to install automatically just because
>> you're installing some other preconditions (e.g. springs preconditions
>> are pretty fast fullfilled, but who still wants it :-)). On the other
>> hand you might have some AOP like profiler which should be installed
>> in case you install management, BUT you don't want to install
>> management if you install the profiler. Do you see what I mean? :-)
>>
>> Kind regards,
>> Andreas
>>
>> On Wed, Jul 25, 2012 at 5:48 AM, Scott England-Sullivan
>> <su...@gmail.com> wrote:
>>> Something like the following? Add an attribute that would mark a bundle as
>>> a named dependency of a parent feature?
>>>
>>> <feature resolver="(obr)" description="Declarative Service support" version=
>>> "3.0.0-SNAPSHOT" name="scr">
>>> .... snip ....
>>> <bundle start-level="30" feature-dependency="webconsole">
>>> mvn:org.apache.karaf.scr/org.apache.karaf.scr.webconsole.plugin/3.0.0-SNAPSHOT
>>> </bundle>
>>> </feature>
>>>
>>> On Tue, Jul 24, 2012 at 10:22 PM, Andreas Pieber <an...@gmail.com> wrote:
>>>
>>>> not so sure if we don't mix up this with KARAF-201 [1]. Scanned the
>>>> mailing list, the jira and my brain for a discussion for such a
>>>> mechanism and couldn't find one. While it might be possible doing
>>>> something like this with post-scripts (as described in [1]) it might
>>>> still be better to have something dedicated for this --> It might be a
>>>> good idea discussing this now and trying to forge an issue from it
>>>> :-).
>>>>
>>>> One idea which jumps into my mind is something like: add a new tag to
>>>> the features.xml; something like optional-extension. If you enter scr
>>>> and webconsole there it could be installed automatically once both of
>>>> the others are installed. We can scan for such features after each
>>>> feature install. I think it wouldn't be too hard to implement that way
>>>> and could come in quite handy for the current webconsole and the
>>>> future karaf-webconsole.
>>>>
>>>> WDYT?
>>>>
>>>> Kind regards,
>>>> Andreas
>>>>
>>>> [1] https://issues.apache.org/jira/browse/KARAF-201
>>>>
>>>> On Tue, Jul 24, 2012 at 10:35 PM, Scott England-Sullivan
>>>> <su...@gmail.com> wrote:
>>>> > Having a trigger mechanism for features would be very useful. It dawned
>>>> on
>>>> > me while looking into this so its good to hear that it is already in
>>>> > discussion.
>>>> >
>>>> > I will just go with webconsole-scr for the moment and add some doco to
>>>> the
>>>> > Karaf site.
>>>> >
>>>> > Thanks for the input. :-)
>>>> >
>>>> > Best Regards,
>>>> > Scott ES
>>>> >
>>>> > On Tue, Jul 24, 2012 at 2:34 PM, Achim Nierbeck <bcanhome@googlemail.com
>>>> >wrote:
>>>> >
>>>> >> Hi
>>>> >>
>>>> >> yeah, somewhere in the dev threads there is a discussion about this :)
>>>> >> There should be even some issue for this.
>>>> >> It was decided to postpone this to 3.1 :)
>>>> >>
>>>> >> regards, Achim
>>>> >>
>>>> >>
>>>> >> 2012/7/24 Ioannis Canellos <io...@gmail.com>:
>>>> >> > In the past in a similar situation we had something like somefeature
>>>> and
>>>> >> > webconsole-somefeature.
>>>> >> >
>>>> >> > Now, I think that it was Andreas or Achim that proposed to extend the
>>>> >> > feature service to support something like triggers that would install
>>>> >> extra
>>>> >> > bundles for a feature when some conditions are meet.
>>>> >> > In that case it would install webconsone-scr if scr is installed and
>>>> >> > webconsole is also installed.
>>>> >> >
>>>> >> >
>>>> >> >
>>>> >> >
>>>> >> >
>>>> >> >
>>>> >> > --
>>>> >> > *Ioannis Canellos*
>>>> >> > *
>>>> >> > FuseSource <http://fusesource.com>
>>>> >> >
>>>> >> > **
>>>> >> > Blog: http://iocanel.blogspot.com
>>>> >> > **
>>>> >> > Twitter: iocanel
>>>> >> > *
>>>> >>
>>>> >>
>>>> >>
>>>> >> --
>>>> >>
>>>> >> Apache Karaf <http://karaf.apache.org/> Committer & PMC
>>>> >> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/>
>>>> >> Committer & Project Lead
>>>> >> OPS4J Pax for Vaadin
>>>> >> <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> Commiter & Project
>>>> >> Lead
>>>> >> blog <http://notizblog.nierbeck.de/>
>>>> >>
>>>> >
>>>> >
>>>> >
>>>> > --
>>>> > --
>>>> > Scott England-Sullivan
>>>> > ----------------------------------
>>>> > FuseSource
>>>> > Web: http://www.fusesource.com
>>>> > Blog: http://sully6768.blogspot.com
>>>> > Twitter: sully6768
>>>>
>>>
>>>
>>>
>>> --
>>> --
>>> Scott England-Sullivan
>>> ----------------------------------
>>> FuseSource
>>> Web: http://www.fusesource.com
>>> Blog: http://sully6768.blogspot.com
>>> Twitter: sully6768
>
>
>
> --
>
> Apache Karaf <http://karaf.apache.org/> Committer & PMC
> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/>
> Committer & Project Lead
> OPS4J Pax for Vaadin
> <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> Commiter & Project
> Lead
> blog <http://notizblog.nierbeck.de/>
Re: Adding Webconsole Plugin for SCR
Posted by Achim Nierbeck <bc...@googlemail.com>.
We had this discussion before and I opened a jira-issue for it :)
The idea was to have like a bundle-fragment for features.
So name it "feature-fragment" which attaches to a certain feature and
does get installed when
the "host" feature is installed. That's the quintessence of the idea :)
Ok there wasn't a specific issue for it yet :/
shame on me but it was somehow attached to another one [1]
the discussion about it can be found here [2]
regards, Achim
[1] - https://issues.apache.org/jira/browse/KARAF-1017
[2] - http://karaf.922171.n3.nabble.com/PROPOSAL-A-features-fragment-for-extending-external-Features-td3709287.html
2012/7/25 Andreas Pieber <an...@gmail.com>:
> I'm afraid this wont be enough. For example there are very likely
> features which you don't want to install automatically just because
> you're installing some other preconditions (e.g. springs preconditions
> are pretty fast fullfilled, but who still wants it :-)). On the other
> hand you might have some AOP like profiler which should be installed
> in case you install management, BUT you don't want to install
> management if you install the profiler. Do you see what I mean? :-)
>
> Kind regards,
> Andreas
>
> On Wed, Jul 25, 2012 at 5:48 AM, Scott England-Sullivan
> <su...@gmail.com> wrote:
>> Something like the following? Add an attribute that would mark a bundle as
>> a named dependency of a parent feature?
>>
>> <feature resolver="(obr)" description="Declarative Service support" version=
>> "3.0.0-SNAPSHOT" name="scr">
>> .... snip ....
>> <bundle start-level="30" feature-dependency="webconsole">
>> mvn:org.apache.karaf.scr/org.apache.karaf.scr.webconsole.plugin/3.0.0-SNAPSHOT
>> </bundle>
>> </feature>
>>
>> On Tue, Jul 24, 2012 at 10:22 PM, Andreas Pieber <an...@gmail.com> wrote:
>>
>>> not so sure if we don't mix up this with KARAF-201 [1]. Scanned the
>>> mailing list, the jira and my brain for a discussion for such a
>>> mechanism and couldn't find one. While it might be possible doing
>>> something like this with post-scripts (as described in [1]) it might
>>> still be better to have something dedicated for this --> It might be a
>>> good idea discussing this now and trying to forge an issue from it
>>> :-).
>>>
>>> One idea which jumps into my mind is something like: add a new tag to
>>> the features.xml; something like optional-extension. If you enter scr
>>> and webconsole there it could be installed automatically once both of
>>> the others are installed. We can scan for such features after each
>>> feature install. I think it wouldn't be too hard to implement that way
>>> and could come in quite handy for the current webconsole and the
>>> future karaf-webconsole.
>>>
>>> WDYT?
>>>
>>> Kind regards,
>>> Andreas
>>>
>>> [1] https://issues.apache.org/jira/browse/KARAF-201
>>>
>>> On Tue, Jul 24, 2012 at 10:35 PM, Scott England-Sullivan
>>> <su...@gmail.com> wrote:
>>> > Having a trigger mechanism for features would be very useful. It dawned
>>> on
>>> > me while looking into this so its good to hear that it is already in
>>> > discussion.
>>> >
>>> > I will just go with webconsole-scr for the moment and add some doco to
>>> the
>>> > Karaf site.
>>> >
>>> > Thanks for the input. :-)
>>> >
>>> > Best Regards,
>>> > Scott ES
>>> >
>>> > On Tue, Jul 24, 2012 at 2:34 PM, Achim Nierbeck <bcanhome@googlemail.com
>>> >wrote:
>>> >
>>> >> Hi
>>> >>
>>> >> yeah, somewhere in the dev threads there is a discussion about this :)
>>> >> There should be even some issue for this.
>>> >> It was decided to postpone this to 3.1 :)
>>> >>
>>> >> regards, Achim
>>> >>
>>> >>
>>> >> 2012/7/24 Ioannis Canellos <io...@gmail.com>:
>>> >> > In the past in a similar situation we had something like somefeature
>>> and
>>> >> > webconsole-somefeature.
>>> >> >
>>> >> > Now, I think that it was Andreas or Achim that proposed to extend the
>>> >> > feature service to support something like triggers that would install
>>> >> extra
>>> >> > bundles for a feature when some conditions are meet.
>>> >> > In that case it would install webconsone-scr if scr is installed and
>>> >> > webconsole is also installed.
>>> >> >
>>> >> >
>>> >> >
>>> >> >
>>> >> >
>>> >> >
>>> >> > --
>>> >> > *Ioannis Canellos*
>>> >> > *
>>> >> > FuseSource <http://fusesource.com>
>>> >> >
>>> >> > **
>>> >> > Blog: http://iocanel.blogspot.com
>>> >> > **
>>> >> > Twitter: iocanel
>>> >> > *
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >>
>>> >> Apache Karaf <http://karaf.apache.org/> Committer & PMC
>>> >> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/>
>>> >> Committer & Project Lead
>>> >> OPS4J Pax for Vaadin
>>> >> <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> Commiter & Project
>>> >> Lead
>>> >> blog <http://notizblog.nierbeck.de/>
>>> >>
>>> >
>>> >
>>> >
>>> > --
>>> > --
>>> > Scott England-Sullivan
>>> > ----------------------------------
>>> > FuseSource
>>> > Web: http://www.fusesource.com
>>> > Blog: http://sully6768.blogspot.com
>>> > Twitter: sully6768
>>>
>>
>>
>>
>> --
>> --
>> Scott England-Sullivan
>> ----------------------------------
>> FuseSource
>> Web: http://www.fusesource.com
>> Blog: http://sully6768.blogspot.com
>> Twitter: sully6768
--
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/>
Committer & Project Lead
OPS4J Pax for Vaadin
<http://team.ops4j.org/wiki/display/PAXVAADIN/Home> Commiter & Project
Lead
blog <http://notizblog.nierbeck.de/>
Re: Adding Webconsole Plugin for SCR
Posted by Andreas Pieber <an...@gmail.com>.
I'm afraid this wont be enough. For example there are very likely
features which you don't want to install automatically just because
you're installing some other preconditions (e.g. springs preconditions
are pretty fast fullfilled, but who still wants it :-)). On the other
hand you might have some AOP like profiler which should be installed
in case you install management, BUT you don't want to install
management if you install the profiler. Do you see what I mean? :-)
Kind regards,
Andreas
On Wed, Jul 25, 2012 at 5:48 AM, Scott England-Sullivan
<su...@gmail.com> wrote:
> Something like the following? Add an attribute that would mark a bundle as
> a named dependency of a parent feature?
>
> <feature resolver="(obr)" description="Declarative Service support" version=
> "3.0.0-SNAPSHOT" name="scr">
> .... snip ....
> <bundle start-level="30" feature-dependency="webconsole">
> mvn:org.apache.karaf.scr/org.apache.karaf.scr.webconsole.plugin/3.0.0-SNAPSHOT
> </bundle>
> </feature>
>
> On Tue, Jul 24, 2012 at 10:22 PM, Andreas Pieber <an...@gmail.com> wrote:
>
>> not so sure if we don't mix up this with KARAF-201 [1]. Scanned the
>> mailing list, the jira and my brain for a discussion for such a
>> mechanism and couldn't find one. While it might be possible doing
>> something like this with post-scripts (as described in [1]) it might
>> still be better to have something dedicated for this --> It might be a
>> good idea discussing this now and trying to forge an issue from it
>> :-).
>>
>> One idea which jumps into my mind is something like: add a new tag to
>> the features.xml; something like optional-extension. If you enter scr
>> and webconsole there it could be installed automatically once both of
>> the others are installed. We can scan for such features after each
>> feature install. I think it wouldn't be too hard to implement that way
>> and could come in quite handy for the current webconsole and the
>> future karaf-webconsole.
>>
>> WDYT?
>>
>> Kind regards,
>> Andreas
>>
>> [1] https://issues.apache.org/jira/browse/KARAF-201
>>
>> On Tue, Jul 24, 2012 at 10:35 PM, Scott England-Sullivan
>> <su...@gmail.com> wrote:
>> > Having a trigger mechanism for features would be very useful. It dawned
>> on
>> > me while looking into this so its good to hear that it is already in
>> > discussion.
>> >
>> > I will just go with webconsole-scr for the moment and add some doco to
>> the
>> > Karaf site.
>> >
>> > Thanks for the input. :-)
>> >
>> > Best Regards,
>> > Scott ES
>> >
>> > On Tue, Jul 24, 2012 at 2:34 PM, Achim Nierbeck <bcanhome@googlemail.com
>> >wrote:
>> >
>> >> Hi
>> >>
>> >> yeah, somewhere in the dev threads there is a discussion about this :)
>> >> There should be even some issue for this.
>> >> It was decided to postpone this to 3.1 :)
>> >>
>> >> regards, Achim
>> >>
>> >>
>> >> 2012/7/24 Ioannis Canellos <io...@gmail.com>:
>> >> > In the past in a similar situation we had something like somefeature
>> and
>> >> > webconsole-somefeature.
>> >> >
>> >> > Now, I think that it was Andreas or Achim that proposed to extend the
>> >> > feature service to support something like triggers that would install
>> >> extra
>> >> > bundles for a feature when some conditions are meet.
>> >> > In that case it would install webconsone-scr if scr is installed and
>> >> > webconsole is also installed.
>> >> >
>> >> >
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > *Ioannis Canellos*
>> >> > *
>> >> > FuseSource <http://fusesource.com>
>> >> >
>> >> > **
>> >> > Blog: http://iocanel.blogspot.com
>> >> > **
>> >> > Twitter: iocanel
>> >> > *
>> >>
>> >>
>> >>
>> >> --
>> >>
>> >> Apache Karaf <http://karaf.apache.org/> Committer & PMC
>> >> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/>
>> >> Committer & Project Lead
>> >> OPS4J Pax for Vaadin
>> >> <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> Commiter & Project
>> >> Lead
>> >> blog <http://notizblog.nierbeck.de/>
>> >>
>> >
>> >
>> >
>> > --
>> > --
>> > Scott England-Sullivan
>> > ----------------------------------
>> > FuseSource
>> > Web: http://www.fusesource.com
>> > Blog: http://sully6768.blogspot.com
>> > Twitter: sully6768
>>
>
>
>
> --
> --
> Scott England-Sullivan
> ----------------------------------
> FuseSource
> Web: http://www.fusesource.com
> Blog: http://sully6768.blogspot.com
> Twitter: sully6768
Re: Adding Webconsole Plugin for SCR
Posted by Scott England-Sullivan <su...@gmail.com>.
Something like the following? Add an attribute that would mark a bundle as
a named dependency of a parent feature?
<feature resolver="(obr)" description="Declarative Service support" version=
"3.0.0-SNAPSHOT" name="scr">
.... snip ....
<bundle start-level="30" feature-dependency="webconsole">
mvn:org.apache.karaf.scr/org.apache.karaf.scr.webconsole.plugin/3.0.0-SNAPSHOT
</bundle>
</feature>
On Tue, Jul 24, 2012 at 10:22 PM, Andreas Pieber <an...@gmail.com> wrote:
> not so sure if we don't mix up this with KARAF-201 [1]. Scanned the
> mailing list, the jira and my brain for a discussion for such a
> mechanism and couldn't find one. While it might be possible doing
> something like this with post-scripts (as described in [1]) it might
> still be better to have something dedicated for this --> It might be a
> good idea discussing this now and trying to forge an issue from it
> :-).
>
> One idea which jumps into my mind is something like: add a new tag to
> the features.xml; something like optional-extension. If you enter scr
> and webconsole there it could be installed automatically once both of
> the others are installed. We can scan for such features after each
> feature install. I think it wouldn't be too hard to implement that way
> and could come in quite handy for the current webconsole and the
> future karaf-webconsole.
>
> WDYT?
>
> Kind regards,
> Andreas
>
> [1] https://issues.apache.org/jira/browse/KARAF-201
>
> On Tue, Jul 24, 2012 at 10:35 PM, Scott England-Sullivan
> <su...@gmail.com> wrote:
> > Having a trigger mechanism for features would be very useful. It dawned
> on
> > me while looking into this so its good to hear that it is already in
> > discussion.
> >
> > I will just go with webconsole-scr for the moment and add some doco to
> the
> > Karaf site.
> >
> > Thanks for the input. :-)
> >
> > Best Regards,
> > Scott ES
> >
> > On Tue, Jul 24, 2012 at 2:34 PM, Achim Nierbeck <bcanhome@googlemail.com
> >wrote:
> >
> >> Hi
> >>
> >> yeah, somewhere in the dev threads there is a discussion about this :)
> >> There should be even some issue for this.
> >> It was decided to postpone this to 3.1 :)
> >>
> >> regards, Achim
> >>
> >>
> >> 2012/7/24 Ioannis Canellos <io...@gmail.com>:
> >> > In the past in a similar situation we had something like somefeature
> and
> >> > webconsole-somefeature.
> >> >
> >> > Now, I think that it was Andreas or Achim that proposed to extend the
> >> > feature service to support something like triggers that would install
> >> extra
> >> > bundles for a feature when some conditions are meet.
> >> > In that case it would install webconsone-scr if scr is installed and
> >> > webconsole is also installed.
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> > --
> >> > *Ioannis Canellos*
> >> > *
> >> > FuseSource <http://fusesource.com>
> >> >
> >> > **
> >> > Blog: http://iocanel.blogspot.com
> >> > **
> >> > Twitter: iocanel
> >> > *
> >>
> >>
> >>
> >> --
> >>
> >> Apache Karaf <http://karaf.apache.org/> Committer & PMC
> >> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/>
> >> Committer & Project Lead
> >> OPS4J Pax for Vaadin
> >> <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> Commiter & Project
> >> Lead
> >> blog <http://notizblog.nierbeck.de/>
> >>
> >
> >
> >
> > --
> > --
> > Scott England-Sullivan
> > ----------------------------------
> > FuseSource
> > Web: http://www.fusesource.com
> > Blog: http://sully6768.blogspot.com
> > Twitter: sully6768
>
--
--
Scott England-Sullivan
----------------------------------
FuseSource
Web: http://www.fusesource.com
Blog: http://sully6768.blogspot.com
Twitter: sully6768
Re: Adding Webconsole Plugin for SCR
Posted by Andreas Pieber <an...@gmail.com>.
not so sure if we don't mix up this with KARAF-201 [1]. Scanned the
mailing list, the jira and my brain for a discussion for such a
mechanism and couldn't find one. While it might be possible doing
something like this with post-scripts (as described in [1]) it might
still be better to have something dedicated for this --> It might be a
good idea discussing this now and trying to forge an issue from it
:-).
One idea which jumps into my mind is something like: add a new tag to
the features.xml; something like optional-extension. If you enter scr
and webconsole there it could be installed automatically once both of
the others are installed. We can scan for such features after each
feature install. I think it wouldn't be too hard to implement that way
and could come in quite handy for the current webconsole and the
future karaf-webconsole.
WDYT?
Kind regards,
Andreas
[1] https://issues.apache.org/jira/browse/KARAF-201
On Tue, Jul 24, 2012 at 10:35 PM, Scott England-Sullivan
<su...@gmail.com> wrote:
> Having a trigger mechanism for features would be very useful. It dawned on
> me while looking into this so its good to hear that it is already in
> discussion.
>
> I will just go with webconsole-scr for the moment and add some doco to the
> Karaf site.
>
> Thanks for the input. :-)
>
> Best Regards,
> Scott ES
>
> On Tue, Jul 24, 2012 at 2:34 PM, Achim Nierbeck <bc...@googlemail.com>wrote:
>
>> Hi
>>
>> yeah, somewhere in the dev threads there is a discussion about this :)
>> There should be even some issue for this.
>> It was decided to postpone this to 3.1 :)
>>
>> regards, Achim
>>
>>
>> 2012/7/24 Ioannis Canellos <io...@gmail.com>:
>> > In the past in a similar situation we had something like somefeature and
>> > webconsole-somefeature.
>> >
>> > Now, I think that it was Andreas or Achim that proposed to extend the
>> > feature service to support something like triggers that would install
>> extra
>> > bundles for a feature when some conditions are meet.
>> > In that case it would install webconsone-scr if scr is installed and
>> > webconsole is also installed.
>> >
>> >
>> >
>> >
>> >
>> >
>> > --
>> > *Ioannis Canellos*
>> > *
>> > FuseSource <http://fusesource.com>
>> >
>> > **
>> > Blog: http://iocanel.blogspot.com
>> > **
>> > Twitter: iocanel
>> > *
>>
>>
>>
>> --
>>
>> Apache Karaf <http://karaf.apache.org/> Committer & PMC
>> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/>
>> Committer & Project Lead
>> OPS4J Pax for Vaadin
>> <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> Commiter & Project
>> Lead
>> blog <http://notizblog.nierbeck.de/>
>>
>
>
>
> --
> --
> Scott England-Sullivan
> ----------------------------------
> FuseSource
> Web: http://www.fusesource.com
> Blog: http://sully6768.blogspot.com
> Twitter: sully6768
Re: Adding Webconsole Plugin for SCR
Posted by Scott England-Sullivan <su...@gmail.com>.
Having a trigger mechanism for features would be very useful. It dawned on
me while looking into this so its good to hear that it is already in
discussion.
I will just go with webconsole-scr for the moment and add some doco to the
Karaf site.
Thanks for the input. :-)
Best Regards,
Scott ES
On Tue, Jul 24, 2012 at 2:34 PM, Achim Nierbeck <bc...@googlemail.com>wrote:
> Hi
>
> yeah, somewhere in the dev threads there is a discussion about this :)
> There should be even some issue for this.
> It was decided to postpone this to 3.1 :)
>
> regards, Achim
>
>
> 2012/7/24 Ioannis Canellos <io...@gmail.com>:
> > In the past in a similar situation we had something like somefeature and
> > webconsole-somefeature.
> >
> > Now, I think that it was Andreas or Achim that proposed to extend the
> > feature service to support something like triggers that would install
> extra
> > bundles for a feature when some conditions are meet.
> > In that case it would install webconsone-scr if scr is installed and
> > webconsole is also installed.
> >
> >
> >
> >
> >
> >
> > --
> > *Ioannis Canellos*
> > *
> > FuseSource <http://fusesource.com>
> >
> > **
> > Blog: http://iocanel.blogspot.com
> > **
> > Twitter: iocanel
> > *
>
>
>
> --
>
> Apache Karaf <http://karaf.apache.org/> Committer & PMC
> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/>
> Committer & Project Lead
> OPS4J Pax for Vaadin
> <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> Commiter & Project
> Lead
> blog <http://notizblog.nierbeck.de/>
>
--
--
Scott England-Sullivan
----------------------------------
FuseSource
Web: http://www.fusesource.com
Blog: http://sully6768.blogspot.com
Twitter: sully6768
Re: Adding Webconsole Plugin for SCR
Posted by Achim Nierbeck <bc...@googlemail.com>.
Hi
yeah, somewhere in the dev threads there is a discussion about this :)
There should be even some issue for this.
It was decided to postpone this to 3.1 :)
regards, Achim
2012/7/24 Ioannis Canellos <io...@gmail.com>:
> In the past in a similar situation we had something like somefeature and
> webconsole-somefeature.
>
> Now, I think that it was Andreas or Achim that proposed to extend the
> feature service to support something like triggers that would install extra
> bundles for a feature when some conditions are meet.
> In that case it would install webconsone-scr if scr is installed and
> webconsole is also installed.
>
>
>
>
>
>
> --
> *Ioannis Canellos*
> *
> FuseSource <http://fusesource.com>
>
> **
> Blog: http://iocanel.blogspot.com
> **
> Twitter: iocanel
> *
--
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/>
Committer & Project Lead
OPS4J Pax for Vaadin
<http://team.ops4j.org/wiki/display/PAXVAADIN/Home> Commiter & Project
Lead
blog <http://notizblog.nierbeck.de/>
Re: Adding Webconsole Plugin for SCR
Posted by Ioannis Canellos <io...@gmail.com>.
In the past in a similar situation we had something like somefeature and
webconsole-somefeature.
Now, I think that it was Andreas or Achim that proposed to extend the
feature service to support something like triggers that would install extra
bundles for a feature when some conditions are meet.
In that case it would install webconsone-scr if scr is installed and
webconsole is also installed.
--
*Ioannis Canellos*
*
FuseSource <http://fusesource.com>
**
Blog: http://iocanel.blogspot.com
**
Twitter: iocanel
*