You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@karaf.apache.org by Łukasz Dywicki <lu...@code-house.org> on 2011/09/02 16:38:38 UTC
[WebConsole] Roadmap sketch discussion
Hey guys,
Since we have bunch of features in current prototype I would like to start talking about roadmap and other communities involvement.
What we currently have:
- Security layer integrated with JAAS, also with support for roles (based on Ioannis jaas-blog example).
Every subpage can have different set of principals allowed to watch it - for example we can introduce karaf-manager and developer roles and so on.
- Support for basic OSGi operations
Start, stop, refresh and uninstall operations on bundles
- Extensible bundles view which allows to add new columns
As an example you can check blueprint module
- Support for basic karaf operations
Viewing, installing features, listing repositories and adding new ones
- Extensible dashboard with widgets possible to be added dynamically by webconsole modules
- Example ServiceMix extension which lists endpoints, exchanges and exchange details
- Support for translations throught wicket i18n mechanism
- Support for branding based on OSGi BrandProvider services, not only on fragment resource overrides.
Felix WebConsole contains much more features eg. viewing the logs, editing the configurations (it's broken currently in our case) managing Karaf instances and so on. I started thinking about announcing our work to these user communities who may be interested in extensions. With them we can discuss scope of webconsole (and their extensions). I think we are close to stabilize core APIs and start working on first version which should be released before end of this year.
Communities which may be involved:
- servicemix (especially in context of smx5)
- camel
- felix
- sling
- geronimo (since it is OSGi based)
- activemq?
- cxf?
WDYT, are we ready to ask them for help and cooperation?
Best regards,
Lukasz
Re: [WebConsole] Roadmap sketch discussion
Posted by Łukasz Dywicki <lu...@code-house.org>.
Hey,
I've created in September project called jsr330 [1] for pax-wicket which allows to run wicket applications with @Inject annotations without direct dependency to pax-wicket nor any other dependency injection framework. It's possible to run same code with different injection sources as WAR or OSGi bundle.
It uses same concepts as pax-wicket and wicket - scaning for annotations and injecting possible services. Injection provider is set in application factory and might be used also in typical web applications [2].
There is still many things to do, but as you see it is possible to run same code and components in different environments.
Best regards,
Lukasz
[1] https://github.com/splatch/pax-wicket-jsr330
[2] https://github.com/splatch/pax-wicket-jsr330/blob/master/test/src/main/java/org/ops4j/pax/wicket/jsr330_test/WicketApplicationFactory.java
> Hey Guillaume,
> You're right we use PaxWicket as an glue to connect all pieces together, but pax in fact is an wicket extension which manages classloaders and wraps some elements (look for @PaxWicketMountPoint annotations, @PaxWicketBean).
>
> Best regards,
> Lukasz
>
>
>> If the console can be run without osgi, the problem becomes slightly
>> different, I agree.
>> If we can provide a basic infrastructure for running the same code in
>> osgi and in a war, it becomes very interesting.
>> But I thought it was based on pax-wicket which afaik is slightly
>> different than pure wicket, but I haven't really looked at it, so not
>> sure about that.
>>
>> Also, camel and activemq consoles are based on top of a rest api which
>> is already provided by those frameworks.
>> For ServiceMix 5, I was considering going the same direction too.
>>
>> 2011/9/8 Łukasz Dywicki <lu...@code-house.org>:
>>> Hey Guillaume,
>>>
>>> Any tool listed below have own 'management' tool, and that's main problem. We (generaly people involved in webconsole development) wish to propose solution without forcing anybody to using or extending it. It will depend on developers and users community if they will see benefits from webconsole extensions or not.
>>> From other hand camel svn repository contains code which is stricly related to Karaf - the commands and some community members support it even if not everyone uses it. In fact 50% of camel code is not widely used, but that is not reason to remove it from source tree, isn't?
>>>
>>> I think also we will be able to provide *web* distribution of webconsole without bigger problems. Code uses plain wicket structures and may be embedded in any WAR so it may be easier to switch webconsole from osgi to war than servicemix from osgi to tomcat.
>>>
>>> Best regards,
>>> Lukasz
>>>
>>>
>>>> 2011/9/2 Łukasz Dywicki <lu...@code-house.org>:
>>>>> Hey guys,
>>>>> Since we have bunch of features in current prototype I would like to start talking about roadmap and other communities involvement.
>>>>>
>>>>> What we currently have:
>>>>> - Security layer integrated with JAAS, also with support for roles (based on Ioannis jaas-blog example).
>>>>> Every subpage can have different set of principals allowed to watch it - for example we can introduce karaf-manager and developer roles and so on.
>>>>> - Support for basic OSGi operations
>>>>> Start, stop, refresh and uninstall operations on bundles
>>>>> - Extensible bundles view which allows to add new columns
>>>>> As an example you can check blueprint module
>>>>> - Support for basic karaf operations
>>>>> Viewing, installing features, listing repositories and adding new ones
>>>>> - Extensible dashboard with widgets possible to be added dynamically by webconsole modules
>>>>> - Example ServiceMix extension which lists endpoints, exchanges and exchange details
>>>>> - Support for translations throught wicket i18n mechanism
>>>>> - Support for branding based on OSGi BrandProvider services, not only on fragment resource overrides.
>>>>>
>>>>> Felix WebConsole contains much more features eg. viewing the logs, editing the configurations (it's broken currently in our case) managing Karaf instances and so on. I started thinking about announcing our work to these user communities who may be interested in extensions. With them we can discuss scope of webconsole (and their extensions). I think we are close to stabilize core APIs and start working on first version which should be released before end of this year.
>>>>>
>>>>> Communities which may be involved:
>>>>> - servicemix (especially in context of smx5)
>>>>> - camel
>>>>> - felix
>>>>> - sling
>>>>> - geronimo (since it is OSGi based)
>>>>> - activemq?
>>>>> - cxf?
>>>>
>>>> Afaik, Geronimo has its own console.
>>>> Camel and ActiveMQ are not OSGi based so I doubt they could benefit
>>>> from this work.
>>>> For ServiceMix, we were also discussing allowing ServiceMix added
>>>> value to run on non OSGi based deployment such as tomcat, so that may
>>>> be a bit problematic too.
>>>>
>>>>> WDYT, are we ready to ask them for help and cooperation?
>>>>>
>>>>> Best regards,
>>>>> Lukasz
>>>>
>>>>
>>>>
>>>> --
>>>> ------------------------
>>>> Guillaume Nodet
>>>> ------------------------
>>>> Blog: http://gnodet.blogspot.com/
>>>> ------------------------
>>>> Open Source SOA
>>>> http://fusesource.com
>>>
>>>
>>
>>
>>
>> --
>> ------------------------
>> Guillaume Nodet
>> ------------------------
>> Blog: http://gnodet.blogspot.com/
>> ------------------------
>> Open Source SOA
>> http://fusesource.com
>
Re: [WebConsole] Roadmap sketch discussion
Posted by Łukasz Dywicki <lu...@code-house.org>.
Guillaume,
I think that it should not take more than day or two to let core run without osgi (with @Inject annotations).
The biggest problem is to look up services or create JMX proxies for them. For example experimental camel plugin uses direct CamelContext istances. ServiceMix plugin uses NMR instance and so on.
Lukasz
> Btw, do you have any idea how much work would be required to run the
> console as a plain war without osgi?
>
> 2011/9/8 Łukasz Dywicki <lu...@code-house.org>
>
>> Hey Guillaume,
>> You're right we use PaxWicket as an glue to connect all pieces together,
>> but pax in fact is an wicket extension which manages classloaders and wraps
>> some elements (look for @PaxWicketMountPoint annotations, @PaxWicketBean).
>>
>> Best regards,
>> Lukasz
>>
>>
>>> If the console can be run without osgi, the problem becomes slightly
>>> different, I agree.
>>> If we can provide a basic infrastructure for running the same code in
>>> osgi and in a war, it becomes very interesting.
>>> But I thought it was based on pax-wicket which afaik is slightly
>>> different than pure wicket, but I haven't really looked at it, so not
>>> sure about that.
>>>
>>> Also, camel and activemq consoles are based on top of a rest api which
>>> is already provided by those frameworks.
>>> For ServiceMix 5, I was considering going the same direction too.
>>>
>>> 2011/9/8 Łukasz Dywicki <lu...@code-house.org>:
>>>> Hey Guillaume,
>>>>
>>>> Any tool listed below have own 'management' tool, and that's main
>> problem. We (generaly people involved in webconsole development) wish to
>> propose solution without forcing anybody to using or extending it. It will
>> depend on developers and users community if they will see benefits from
>> webconsole extensions or not.
>>>> From other hand camel svn repository contains code which is stricly
>> related to Karaf - the commands and some community members support it even
>> if not everyone uses it. In fact 50% of camel code is not widely used, but
>> that is not reason to remove it from source tree, isn't?
>>>>
>>>> I think also we will be able to provide *web* distribution of
>> webconsole without bigger problems. Code uses plain wicket structures and
>> may be embedded in any WAR so it may be easier to switch webconsole from
>> osgi to war than servicemix from osgi to tomcat.
>>>>
>>>> Best regards,
>>>> Lukasz
>>>>
>>>>
>>>>> 2011/9/2 Łukasz Dywicki <lu...@code-house.org>:
>>>>>> Hey guys,
>>>>>> Since we have bunch of features in current prototype I would like to
>> start talking about roadmap and other communities involvement.
>>>>>>
>>>>>> What we currently have:
>>>>>> - Security layer integrated with JAAS, also with support for roles
>> (based on Ioannis jaas-blog example).
>>>>>> Every subpage can have different set of principals allowed to
>> watch it - for example we can introduce karaf-manager and developer roles
>> and so on.
>>>>>> - Support for basic OSGi operations
>>>>>> Start, stop, refresh and uninstall operations on bundles
>>>>>> - Extensible bundles view which allows to add new columns
>>>>>> As an example you can check blueprint module
>>>>>> - Support for basic karaf operations
>>>>>> Viewing, installing features, listing repositories and adding
>> new ones
>>>>>> - Extensible dashboard with widgets possible to be added dynamically
>> by webconsole modules
>>>>>> - Example ServiceMix extension which lists endpoints, exchanges and
>> exchange details
>>>>>> - Support for translations throught wicket i18n mechanism
>>>>>> - Support for branding based on OSGi BrandProvider services, not only
>> on fragment resource overrides.
>>>>>>
>>>>>> Felix WebConsole contains much more features eg. viewing the logs,
>> editing the configurations (it's broken currently in our case) managing
>> Karaf instances and so on. I started thinking about announcing our work to
>> these user communities who may be interested in extensions. With them we
>> can discuss scope of webconsole (and their extensions). I think we are
>> close to stabilize core APIs and start working on first version which
>> should be released before end of this year.
>>>>>>
>>>>>> Communities which may be involved:
>>>>>> - servicemix (especially in context of smx5)
>>>>>> - camel
>>>>>> - felix
>>>>>> - sling
>>>>>> - geronimo (since it is OSGi based)
>>>>>> - activemq?
>>>>>> - cxf?
>>>>>
>>>>> Afaik, Geronimo has its own console.
>>>>> Camel and ActiveMQ are not OSGi based so I doubt they could benefit
>>>>> from this work.
>>>>> For ServiceMix, we were also discussing allowing ServiceMix added
>>>>> value to run on non OSGi based deployment such as tomcat, so that may
>>>>> be a bit problematic too.
>>>>>
>>>>>> WDYT, are we ready to ask them for help and cooperation?
>>>>>>
>>>>>> Best regards,
>>>>>> Lukasz
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> ------------------------
>>>>> Guillaume Nodet
>>>>> ------------------------
>>>>> Blog: http://gnodet.blogspot.com/
>>>>> ------------------------
>>>>> Open Source SOA
>>>>> http://fusesource.com
>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> ------------------------
>>> Guillaume Nodet
>>> ------------------------
>>> Blog: http://gnodet.blogspot.com/
>>> ------------------------
>>> Open Source SOA
>>> http://fusesource.com
>>
>>
>
>
> --
> ------------------------
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
> ------------------------
> Open Source SOA
> http://fusesource.com
Re: [WebConsole] Roadmap sketch discussion
Posted by Guillaume Nodet <gn...@gmail.com>.
Btw, do you have any idea how much work would be required to run the
console as a plain war without osgi?
2011/9/8 Łukasz Dywicki <lu...@code-house.org>
> Hey Guillaume,
> You're right we use PaxWicket as an glue to connect all pieces together,
> but pax in fact is an wicket extension which manages classloaders and wraps
> some elements (look for @PaxWicketMountPoint annotations, @PaxWicketBean).
>
> Best regards,
> Lukasz
>
>
> > If the console can be run without osgi, the problem becomes slightly
> > different, I agree.
> > If we can provide a basic infrastructure for running the same code in
> > osgi and in a war, it becomes very interesting.
> > But I thought it was based on pax-wicket which afaik is slightly
> > different than pure wicket, but I haven't really looked at it, so not
> > sure about that.
> >
> > Also, camel and activemq consoles are based on top of a rest api which
> > is already provided by those frameworks.
> > For ServiceMix 5, I was considering going the same direction too.
> >
> > 2011/9/8 Łukasz Dywicki <lu...@code-house.org>:
> >> Hey Guillaume,
> >>
> >> Any tool listed below have own 'management' tool, and that's main
> problem. We (generaly people involved in webconsole development) wish to
> propose solution without forcing anybody to using or extending it. It will
> depend on developers and users community if they will see benefits from
> webconsole extensions or not.
> >> From other hand camel svn repository contains code which is stricly
> related to Karaf - the commands and some community members support it even
> if not everyone uses it. In fact 50% of camel code is not widely used, but
> that is not reason to remove it from source tree, isn't?
> >>
> >> I think also we will be able to provide *web* distribution of
> webconsole without bigger problems. Code uses plain wicket structures and
> may be embedded in any WAR so it may be easier to switch webconsole from
> osgi to war than servicemix from osgi to tomcat.
> >>
> >> Best regards,
> >> Lukasz
> >>
> >>
> >>> 2011/9/2 Łukasz Dywicki <lu...@code-house.org>:
> >>>> Hey guys,
> >>>> Since we have bunch of features in current prototype I would like to
> start talking about roadmap and other communities involvement.
> >>>>
> >>>> What we currently have:
> >>>> - Security layer integrated with JAAS, also with support for roles
> (based on Ioannis jaas-blog example).
> >>>> Every subpage can have different set of principals allowed to
> watch it - for example we can introduce karaf-manager and developer roles
> and so on.
> >>>> - Support for basic OSGi operations
> >>>> Start, stop, refresh and uninstall operations on bundles
> >>>> - Extensible bundles view which allows to add new columns
> >>>> As an example you can check blueprint module
> >>>> - Support for basic karaf operations
> >>>> Viewing, installing features, listing repositories and adding
> new ones
> >>>> - Extensible dashboard with widgets possible to be added dynamically
> by webconsole modules
> >>>> - Example ServiceMix extension which lists endpoints, exchanges and
> exchange details
> >>>> - Support for translations throught wicket i18n mechanism
> >>>> - Support for branding based on OSGi BrandProvider services, not only
> on fragment resource overrides.
> >>>>
> >>>> Felix WebConsole contains much more features eg. viewing the logs,
> editing the configurations (it's broken currently in our case) managing
> Karaf instances and so on. I started thinking about announcing our work to
> these user communities who may be interested in extensions. With them we
> can discuss scope of webconsole (and their extensions). I think we are
> close to stabilize core APIs and start working on first version which
> should be released before end of this year.
> >>>>
> >>>> Communities which may be involved:
> >>>> - servicemix (especially in context of smx5)
> >>>> - camel
> >>>> - felix
> >>>> - sling
> >>>> - geronimo (since it is OSGi based)
> >>>> - activemq?
> >>>> - cxf?
> >>>
> >>> Afaik, Geronimo has its own console.
> >>> Camel and ActiveMQ are not OSGi based so I doubt they could benefit
> >>> from this work.
> >>> For ServiceMix, we were also discussing allowing ServiceMix added
> >>> value to run on non OSGi based deployment such as tomcat, so that may
> >>> be a bit problematic too.
> >>>
> >>>> WDYT, are we ready to ask them for help and cooperation?
> >>>>
> >>>> Best regards,
> >>>> Lukasz
> >>>
> >>>
> >>>
> >>> --
> >>> ------------------------
> >>> Guillaume Nodet
> >>> ------------------------
> >>> Blog: http://gnodet.blogspot.com/
> >>> ------------------------
> >>> Open Source SOA
> >>> http://fusesource.com
> >>
> >>
> >
> >
> >
> > --
> > ------------------------
> > Guillaume Nodet
> > ------------------------
> > Blog: http://gnodet.blogspot.com/
> > ------------------------
> > Open Source SOA
> > http://fusesource.com
>
>
--
------------------------
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com
Re: [WebConsole] Roadmap sketch discussion
Posted by Łukasz Dywicki <lu...@code-house.org>.
Hey Guillaume,
You're right we use PaxWicket as an glue to connect all pieces together, but pax in fact is an wicket extension which manages classloaders and wraps some elements (look for @PaxWicketMountPoint annotations, @PaxWicketBean).
Best regards,
Lukasz
> If the console can be run without osgi, the problem becomes slightly
> different, I agree.
> If we can provide a basic infrastructure for running the same code in
> osgi and in a war, it becomes very interesting.
> But I thought it was based on pax-wicket which afaik is slightly
> different than pure wicket, but I haven't really looked at it, so not
> sure about that.
>
> Also, camel and activemq consoles are based on top of a rest api which
> is already provided by those frameworks.
> For ServiceMix 5, I was considering going the same direction too.
>
> 2011/9/8 Łukasz Dywicki <lu...@code-house.org>:
>> Hey Guillaume,
>>
>> Any tool listed below have own 'management' tool, and that's main problem. We (generaly people involved in webconsole development) wish to propose solution without forcing anybody to using or extending it. It will depend on developers and users community if they will see benefits from webconsole extensions or not.
>> From other hand camel svn repository contains code which is stricly related to Karaf - the commands and some community members support it even if not everyone uses it. In fact 50% of camel code is not widely used, but that is not reason to remove it from source tree, isn't?
>>
>> I think also we will be able to provide *web* distribution of webconsole without bigger problems. Code uses plain wicket structures and may be embedded in any WAR so it may be easier to switch webconsole from osgi to war than servicemix from osgi to tomcat.
>>
>> Best regards,
>> Lukasz
>>
>>
>>> 2011/9/2 Łukasz Dywicki <lu...@code-house.org>:
>>>> Hey guys,
>>>> Since we have bunch of features in current prototype I would like to start talking about roadmap and other communities involvement.
>>>>
>>>> What we currently have:
>>>> - Security layer integrated with JAAS, also with support for roles (based on Ioannis jaas-blog example).
>>>> Every subpage can have different set of principals allowed to watch it - for example we can introduce karaf-manager and developer roles and so on.
>>>> - Support for basic OSGi operations
>>>> Start, stop, refresh and uninstall operations on bundles
>>>> - Extensible bundles view which allows to add new columns
>>>> As an example you can check blueprint module
>>>> - Support for basic karaf operations
>>>> Viewing, installing features, listing repositories and adding new ones
>>>> - Extensible dashboard with widgets possible to be added dynamically by webconsole modules
>>>> - Example ServiceMix extension which lists endpoints, exchanges and exchange details
>>>> - Support for translations throught wicket i18n mechanism
>>>> - Support for branding based on OSGi BrandProvider services, not only on fragment resource overrides.
>>>>
>>>> Felix WebConsole contains much more features eg. viewing the logs, editing the configurations (it's broken currently in our case) managing Karaf instances and so on. I started thinking about announcing our work to these user communities who may be interested in extensions. With them we can discuss scope of webconsole (and their extensions). I think we are close to stabilize core APIs and start working on first version which should be released before end of this year.
>>>>
>>>> Communities which may be involved:
>>>> - servicemix (especially in context of smx5)
>>>> - camel
>>>> - felix
>>>> - sling
>>>> - geronimo (since it is OSGi based)
>>>> - activemq?
>>>> - cxf?
>>>
>>> Afaik, Geronimo has its own console.
>>> Camel and ActiveMQ are not OSGi based so I doubt they could benefit
>>> from this work.
>>> For ServiceMix, we were also discussing allowing ServiceMix added
>>> value to run on non OSGi based deployment such as tomcat, so that may
>>> be a bit problematic too.
>>>
>>>> WDYT, are we ready to ask them for help and cooperation?
>>>>
>>>> Best regards,
>>>> Lukasz
>>>
>>>
>>>
>>> --
>>> ------------------------
>>> Guillaume Nodet
>>> ------------------------
>>> Blog: http://gnodet.blogspot.com/
>>> ------------------------
>>> Open Source SOA
>>> http://fusesource.com
>>
>>
>
>
>
> --
> ------------------------
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
> ------------------------
> Open Source SOA
> http://fusesource.com
Re: [WebConsole] Roadmap sketch discussion
Posted by Guillaume Nodet <gn...@gmail.com>.
If the console can be run without osgi, the problem becomes slightly
different, I agree.
If we can provide a basic infrastructure for running the same code in
osgi and in a war, it becomes very interesting.
But I thought it was based on pax-wicket which afaik is slightly
different than pure wicket, but I haven't really looked at it, so not
sure about that.
Also, camel and activemq consoles are based on top of a rest api which
is already provided by those frameworks.
For ServiceMix 5, I was considering going the same direction too.
2011/9/8 Łukasz Dywicki <lu...@code-house.org>:
> Hey Guillaume,
>
> Any tool listed below have own 'management' tool, and that's main problem. We (generaly people involved in webconsole development) wish to propose solution without forcing anybody to using or extending it. It will depend on developers and users community if they will see benefits from webconsole extensions or not.
> From other hand camel svn repository contains code which is stricly related to Karaf - the commands and some community members support it even if not everyone uses it. In fact 50% of camel code is not widely used, but that is not reason to remove it from source tree, isn't?
>
> I think also we will be able to provide *web* distribution of webconsole without bigger problems. Code uses plain wicket structures and may be embedded in any WAR so it may be easier to switch webconsole from osgi to war than servicemix from osgi to tomcat.
>
> Best regards,
> Lukasz
>
>
>> 2011/9/2 Łukasz Dywicki <lu...@code-house.org>:
>>> Hey guys,
>>> Since we have bunch of features in current prototype I would like to start talking about roadmap and other communities involvement.
>>>
>>> What we currently have:
>>> - Security layer integrated with JAAS, also with support for roles (based on Ioannis jaas-blog example).
>>> Every subpage can have different set of principals allowed to watch it - for example we can introduce karaf-manager and developer roles and so on.
>>> - Support for basic OSGi operations
>>> Start, stop, refresh and uninstall operations on bundles
>>> - Extensible bundles view which allows to add new columns
>>> As an example you can check blueprint module
>>> - Support for basic karaf operations
>>> Viewing, installing features, listing repositories and adding new ones
>>> - Extensible dashboard with widgets possible to be added dynamically by webconsole modules
>>> - Example ServiceMix extension which lists endpoints, exchanges and exchange details
>>> - Support for translations throught wicket i18n mechanism
>>> - Support for branding based on OSGi BrandProvider services, not only on fragment resource overrides.
>>>
>>> Felix WebConsole contains much more features eg. viewing the logs, editing the configurations (it's broken currently in our case) managing Karaf instances and so on. I started thinking about announcing our work to these user communities who may be interested in extensions. With them we can discuss scope of webconsole (and their extensions). I think we are close to stabilize core APIs and start working on first version which should be released before end of this year.
>>>
>>> Communities which may be involved:
>>> - servicemix (especially in context of smx5)
>>> - camel
>>> - felix
>>> - sling
>>> - geronimo (since it is OSGi based)
>>> - activemq?
>>> - cxf?
>>
>> Afaik, Geronimo has its own console.
>> Camel and ActiveMQ are not OSGi based so I doubt they could benefit
>> from this work.
>> For ServiceMix, we were also discussing allowing ServiceMix added
>> value to run on non OSGi based deployment such as tomcat, so that may
>> be a bit problematic too.
>>
>>> WDYT, are we ready to ask them for help and cooperation?
>>>
>>> Best regards,
>>> Lukasz
>>
>>
>>
>> --
>> ------------------------
>> Guillaume Nodet
>> ------------------------
>> Blog: http://gnodet.blogspot.com/
>> ------------------------
>> Open Source SOA
>> http://fusesource.com
>
>
--
------------------------
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com
Re: [WebConsole] Roadmap sketch discussion
Posted by Łukasz Dywicki <lu...@code-house.org>.
Hey Guillaume,
Any tool listed below have own 'management' tool, and that's main problem. We (generaly people involved in webconsole development) wish to propose solution without forcing anybody to using or extending it. It will depend on developers and users community if they will see benefits from webconsole extensions or not.
From other hand camel svn repository contains code which is stricly related to Karaf - the commands and some community members support it even if not everyone uses it. In fact 50% of camel code is not widely used, but that is not reason to remove it from source tree, isn't?
I think also we will be able to provide *web* distribution of webconsole without bigger problems. Code uses plain wicket structures and may be embedded in any WAR so it may be easier to switch webconsole from osgi to war than servicemix from osgi to tomcat.
Best regards,
Lukasz
> 2011/9/2 Łukasz Dywicki <lu...@code-house.org>:
>> Hey guys,
>> Since we have bunch of features in current prototype I would like to start talking about roadmap and other communities involvement.
>>
>> What we currently have:
>> - Security layer integrated with JAAS, also with support for roles (based on Ioannis jaas-blog example).
>> Every subpage can have different set of principals allowed to watch it - for example we can introduce karaf-manager and developer roles and so on.
>> - Support for basic OSGi operations
>> Start, stop, refresh and uninstall operations on bundles
>> - Extensible bundles view which allows to add new columns
>> As an example you can check blueprint module
>> - Support for basic karaf operations
>> Viewing, installing features, listing repositories and adding new ones
>> - Extensible dashboard with widgets possible to be added dynamically by webconsole modules
>> - Example ServiceMix extension which lists endpoints, exchanges and exchange details
>> - Support for translations throught wicket i18n mechanism
>> - Support for branding based on OSGi BrandProvider services, not only on fragment resource overrides.
>>
>> Felix WebConsole contains much more features eg. viewing the logs, editing the configurations (it's broken currently in our case) managing Karaf instances and so on. I started thinking about announcing our work to these user communities who may be interested in extensions. With them we can discuss scope of webconsole (and their extensions). I think we are close to stabilize core APIs and start working on first version which should be released before end of this year.
>>
>> Communities which may be involved:
>> - servicemix (especially in context of smx5)
>> - camel
>> - felix
>> - sling
>> - geronimo (since it is OSGi based)
>> - activemq?
>> - cxf?
>
> Afaik, Geronimo has its own console.
> Camel and ActiveMQ are not OSGi based so I doubt they could benefit
> from this work.
> For ServiceMix, we were also discussing allowing ServiceMix added
> value to run on non OSGi based deployment such as tomcat, so that may
> be a bit problematic too.
>
>> WDYT, are we ready to ask them for help and cooperation?
>>
>> Best regards,
>> Lukasz
>
>
>
> --
> ------------------------
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
> ------------------------
> Open Source SOA
> http://fusesource.com
Re: [WebConsole] Roadmap sketch discussion
Posted by Guillaume Nodet <gn...@gmail.com>.
2011/9/2 Łukasz Dywicki <lu...@code-house.org>:
> Hey guys,
> Since we have bunch of features in current prototype I would like to start talking about roadmap and other communities involvement.
>
> What we currently have:
> - Security layer integrated with JAAS, also with support for roles (based on Ioannis jaas-blog example).
> Every subpage can have different set of principals allowed to watch it - for example we can introduce karaf-manager and developer roles and so on.
> - Support for basic OSGi operations
> Start, stop, refresh and uninstall operations on bundles
> - Extensible bundles view which allows to add new columns
> As an example you can check blueprint module
> - Support for basic karaf operations
> Viewing, installing features, listing repositories and adding new ones
> - Extensible dashboard with widgets possible to be added dynamically by webconsole modules
> - Example ServiceMix extension which lists endpoints, exchanges and exchange details
> - Support for translations throught wicket i18n mechanism
> - Support for branding based on OSGi BrandProvider services, not only on fragment resource overrides.
>
> Felix WebConsole contains much more features eg. viewing the logs, editing the configurations (it's broken currently in our case) managing Karaf instances and so on. I started thinking about announcing our work to these user communities who may be interested in extensions. With them we can discuss scope of webconsole (and their extensions). I think we are close to stabilize core APIs and start working on first version which should be released before end of this year.
>
> Communities which may be involved:
> - servicemix (especially in context of smx5)
> - camel
> - felix
> - sling
> - geronimo (since it is OSGi based)
> - activemq?
> - cxf?
Afaik, Geronimo has its own console.
Camel and ActiveMQ are not OSGi based so I doubt they could benefit
from this work.
For ServiceMix, we were also discussing allowing ServiceMix added
value to run on non OSGi based deployment such as tomcat, so that may
be a bit problematic too.
> WDYT, are we ready to ask them for help and cooperation?
>
> Best regards,
> Lukasz
--
------------------------
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com
Re: [WebConsole] Roadmap sketch discussion
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Lukasz,
thanks for the update.
I worked on the webconsole this morning. I will start some commits, and
propose some "skin" and "branding" support (as we have for Karaf shell
console).
Regards
JB
On 09/08/2011 12:42 PM, Łukasz Dywicki wrote:
> Hey,
> As discussed earlier in '[PROPOSAL] Promote Cave and WebConsole as Karaf sub-projects' topic and on IRC - I've decreased version of webconsole to 0.3.0-SNAPSHOT (from 1.0.0). Please be aware about this. You will need to re-install development versions on your local machines.
>
> Best regards,
> Lukasz
>
>
>> Nope, typically I startup the env. using pax-exam and running the web-based
>> tests then using htmlunit.
>>
>> Kind regards,
>> Andreas
>>
>> 2011/9/6 Łukasz Dywicki<lu...@code-house.org>
>>
>>> Yeah,
>>> Integration tests will be very useful for feature installation verification
>>> (something we don't verify even in karaf core).
>>> Anyway, will we be able to test webconsole with wicket-tester which runs in
>>> pax-exam managed container?
>>>
>>> Best regards,
>>> Lukasz
>>>
>>>> Great work Lukasz. I'll contribute some integration tests the next days.
>>>> This should increase the coverage by far and also show if something
>>>> fundamental goes wrong suddenly.
>>>>
>>>> Kind regards,
>>>> Andreas
>>>>
>>>> 2011/9/6 Łukasz Dywicki<lu...@code-house.org>
>>>>
>>>>> Hi,
>>>>> I worked a bit on unit tests and now we have few in core. They covers
>>> base
>>>>> elements - including BasePage, SecuredPage, authentication and
>>>>> authorization. Also I've updated manual (which is still small) - now we
>>> have
>>>>> small set of documentation about extensions, security and branding.
>>>>>
>>>>> Best regards,
>>>>> Lukasz
>>>>>
>>>>>> Hey Lukas,
>>>>>>
>>>>>> Wow, the feature set growed really fast :-). Great work guys!
>>>>>>
>>>>>> Basically I think we've enough to start shouting around. Still I think
>>>>> there
>>>>>> are two things missing beforehand:
>>>>>>
>>>>>> a) We really need to introduce at least a little set of unit and
>>>>> integration
>>>>>> tests. People are in general more afraid to edit/extend not-tested code
>>>>> than
>>>>>> well tested code
>>>>>>
>>>>>> b) I think we need at least a little set of infrastructure and feature
>>>>>> documentation. That would give ppl the possibility to get a good
>>>>>> introduction and IMHO also a little bit motivation to continue it.
>>>>>>
>>>>>> @(a) I'm writing right now at a test framework to get up karaf as the
>>>>> base
>>>>>> framework in exam. The code is currently located [1]. ASAP it is stable
>>>>> I'll
>>>>>> push it into the karaf sandbox. We can base the webconsole integration
>>>>> tests
>>>>>> on that framework.
>>>>>>
>>>>>> WDYT?
>>>>>>
>>>>>> Kind regards,
>>>>>> Andreas
>>>>>>
>>>>>> [1]
>>> https://github.com/fossbrain/org.fossbrain.extensions.paxexam.karaf
>>>>>>
>>>>>> 2011/9/2 Łukasz Dywicki<lu...@code-house.org>
>>>>>>
>>>>>>> Hey guys,
>>>>>>> Since we have bunch of features in current prototype I would like to
>>>>> start
>>>>>>> talking about roadmap and other communities involvement.
>>>>>>>
>>>>>>> What we currently have:
>>>>>>> - Security layer integrated with JAAS, also with support for roles
>>>>> (based
>>>>>>> on Ioannis jaas-blog example).
>>>>>>> Every subpage can have different set of principals allowed to
>>>>> watch
>>>>>>> it - for example we can introduce karaf-manager and developer roles
>>> and
>>>>> so
>>>>>>> on.
>>>>>>> - Support for basic OSGi operations
>>>>>>> Start, stop, refresh and uninstall operations on bundles
>>>>>>> - Extensible bundles view which allows to add new columns
>>>>>>> As an example you can check blueprint module
>>>>>>> - Support for basic karaf operations
>>>>>>> Viewing, installing features, listing repositories and adding new
>>>>>>> ones
>>>>>>> - Extensible dashboard with widgets possible to be added dynamically
>>> by
>>>>>>> webconsole modules
>>>>>>> - Example ServiceMix extension which lists endpoints, exchanges and
>>>>>>> exchange details
>>>>>>> - Support for translations throught wicket i18n mechanism
>>>>>>> - Support for branding based on OSGi BrandProvider services, not only
>>> on
>>>>>>> fragment resource overrides.
>>>>>>>
>>>>>>> Felix WebConsole contains much more features eg. viewing the logs,
>>>>> editing
>>>>>>> the configurations (it's broken currently in our case) managing Karaf
>>>>>>> instances and so on. I started thinking about announcing our work to
>>>>> these
>>>>>>> user communities who may be interested in extensions. With them we can
>>>>>>> discuss scope of webconsole (and their extensions). I think we are
>>> close
>>>>> to
>>>>>>> stabilize core APIs and start working on first version which should be
>>>>>>> released before end of this year.
>>>>>>>
>>>>>>> Communities which may be involved:
>>>>>>> - servicemix (especially in context of smx5)
>>>>>>> - camel
>>>>>>> - felix
>>>>>>> - sling
>>>>>>> - geronimo (since it is OSGi based)
>>>>>>> - activemq?
>>>>>>> - cxf?
>>>>>>>
>>>>>>> WDYT, are we ready to ask them for help and cooperation?
>>>>>>>
>>>>>>> Best regards,
>>>>>>> Lukasz
>>>>>
>>>>>
>>>
>>>
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [WebConsole] Roadmap sketch discussion
Posted by Łukasz Dywicki <lu...@code-house.org>.
Hey,
As discussed earlier in '[PROPOSAL] Promote Cave and WebConsole as Karaf sub-projects' topic and on IRC - I've decreased version of webconsole to 0.3.0-SNAPSHOT (from 1.0.0). Please be aware about this. You will need to re-install development versions on your local machines.
Best regards,
Lukasz
> Nope, typically I startup the env. using pax-exam and running the web-based
> tests then using htmlunit.
>
> Kind regards,
> Andreas
>
> 2011/9/6 Łukasz Dywicki <lu...@code-house.org>
>
>> Yeah,
>> Integration tests will be very useful for feature installation verification
>> (something we don't verify even in karaf core).
>> Anyway, will we be able to test webconsole with wicket-tester which runs in
>> pax-exam managed container?
>>
>> Best regards,
>> Lukasz
>>
>>> Great work Lukasz. I'll contribute some integration tests the next days.
>>> This should increase the coverage by far and also show if something
>>> fundamental goes wrong suddenly.
>>>
>>> Kind regards,
>>> Andreas
>>>
>>> 2011/9/6 Łukasz Dywicki <lu...@code-house.org>
>>>
>>>> Hi,
>>>> I worked a bit on unit tests and now we have few in core. They covers
>> base
>>>> elements - including BasePage, SecuredPage, authentication and
>>>> authorization. Also I've updated manual (which is still small) - now we
>> have
>>>> small set of documentation about extensions, security and branding.
>>>>
>>>> Best regards,
>>>> Lukasz
>>>>
>>>>> Hey Lukas,
>>>>>
>>>>> Wow, the feature set growed really fast :-). Great work guys!
>>>>>
>>>>> Basically I think we've enough to start shouting around. Still I think
>>>> there
>>>>> are two things missing beforehand:
>>>>>
>>>>> a) We really need to introduce at least a little set of unit and
>>>> integration
>>>>> tests. People are in general more afraid to edit/extend not-tested code
>>>> than
>>>>> well tested code
>>>>>
>>>>> b) I think we need at least a little set of infrastructure and feature
>>>>> documentation. That would give ppl the possibility to get a good
>>>>> introduction and IMHO also a little bit motivation to continue it.
>>>>>
>>>>> @(a) I'm writing right now at a test framework to get up karaf as the
>>>> base
>>>>> framework in exam. The code is currently located [1]. ASAP it is stable
>>>> I'll
>>>>> push it into the karaf sandbox. We can base the webconsole integration
>>>> tests
>>>>> on that framework.
>>>>>
>>>>> WDYT?
>>>>>
>>>>> Kind regards,
>>>>> Andreas
>>>>>
>>>>> [1]
>> https://github.com/fossbrain/org.fossbrain.extensions.paxexam.karaf
>>>>>
>>>>> 2011/9/2 Łukasz Dywicki <lu...@code-house.org>
>>>>>
>>>>>> Hey guys,
>>>>>> Since we have bunch of features in current prototype I would like to
>>>> start
>>>>>> talking about roadmap and other communities involvement.
>>>>>>
>>>>>> What we currently have:
>>>>>> - Security layer integrated with JAAS, also with support for roles
>>>> (based
>>>>>> on Ioannis jaas-blog example).
>>>>>> Every subpage can have different set of principals allowed to
>>>> watch
>>>>>> it - for example we can introduce karaf-manager and developer roles
>> and
>>>> so
>>>>>> on.
>>>>>> - Support for basic OSGi operations
>>>>>> Start, stop, refresh and uninstall operations on bundles
>>>>>> - Extensible bundles view which allows to add new columns
>>>>>> As an example you can check blueprint module
>>>>>> - Support for basic karaf operations
>>>>>> Viewing, installing features, listing repositories and adding new
>>>>>> ones
>>>>>> - Extensible dashboard with widgets possible to be added dynamically
>> by
>>>>>> webconsole modules
>>>>>> - Example ServiceMix extension which lists endpoints, exchanges and
>>>>>> exchange details
>>>>>> - Support for translations throught wicket i18n mechanism
>>>>>> - Support for branding based on OSGi BrandProvider services, not only
>> on
>>>>>> fragment resource overrides.
>>>>>>
>>>>>> Felix WebConsole contains much more features eg. viewing the logs,
>>>> editing
>>>>>> the configurations (it's broken currently in our case) managing Karaf
>>>>>> instances and so on. I started thinking about announcing our work to
>>>> these
>>>>>> user communities who may be interested in extensions. With them we can
>>>>>> discuss scope of webconsole (and their extensions). I think we are
>> close
>>>> to
>>>>>> stabilize core APIs and start working on first version which should be
>>>>>> released before end of this year.
>>>>>>
>>>>>> Communities which may be involved:
>>>>>> - servicemix (especially in context of smx5)
>>>>>> - camel
>>>>>> - felix
>>>>>> - sling
>>>>>> - geronimo (since it is OSGi based)
>>>>>> - activemq?
>>>>>> - cxf?
>>>>>>
>>>>>> WDYT, are we ready to ask them for help and cooperation?
>>>>>>
>>>>>> Best regards,
>>>>>> Lukasz
>>>>
>>>>
>>
>>
Re: [WebConsole] Roadmap sketch discussion
Posted by Andreas Pieber <an...@gmail.com>.
Nope, typically I startup the env. using pax-exam and running the web-based
tests then using htmlunit.
Kind regards,
Andreas
2011/9/6 Łukasz Dywicki <lu...@code-house.org>
> Yeah,
> Integration tests will be very useful for feature installation verification
> (something we don't verify even in karaf core).
> Anyway, will we be able to test webconsole with wicket-tester which runs in
> pax-exam managed container?
>
> Best regards,
> Lukasz
>
> > Great work Lukasz. I'll contribute some integration tests the next days.
> > This should increase the coverage by far and also show if something
> > fundamental goes wrong suddenly.
> >
> > Kind regards,
> > Andreas
> >
> > 2011/9/6 Łukasz Dywicki <lu...@code-house.org>
> >
> >> Hi,
> >> I worked a bit on unit tests and now we have few in core. They covers
> base
> >> elements - including BasePage, SecuredPage, authentication and
> >> authorization. Also I've updated manual (which is still small) - now we
> have
> >> small set of documentation about extensions, security and branding.
> >>
> >> Best regards,
> >> Lukasz
> >>
> >>> Hey Lukas,
> >>>
> >>> Wow, the feature set growed really fast :-). Great work guys!
> >>>
> >>> Basically I think we've enough to start shouting around. Still I think
> >> there
> >>> are two things missing beforehand:
> >>>
> >>> a) We really need to introduce at least a little set of unit and
> >> integration
> >>> tests. People are in general more afraid to edit/extend not-tested code
> >> than
> >>> well tested code
> >>>
> >>> b) I think we need at least a little set of infrastructure and feature
> >>> documentation. That would give ppl the possibility to get a good
> >>> introduction and IMHO also a little bit motivation to continue it.
> >>>
> >>> @(a) I'm writing right now at a test framework to get up karaf as the
> >> base
> >>> framework in exam. The code is currently located [1]. ASAP it is stable
> >> I'll
> >>> push it into the karaf sandbox. We can base the webconsole integration
> >> tests
> >>> on that framework.
> >>>
> >>> WDYT?
> >>>
> >>> Kind regards,
> >>> Andreas
> >>>
> >>> [1]
> https://github.com/fossbrain/org.fossbrain.extensions.paxexam.karaf
> >>>
> >>> 2011/9/2 Łukasz Dywicki <lu...@code-house.org>
> >>>
> >>>> Hey guys,
> >>>> Since we have bunch of features in current prototype I would like to
> >> start
> >>>> talking about roadmap and other communities involvement.
> >>>>
> >>>> What we currently have:
> >>>> - Security layer integrated with JAAS, also with support for roles
> >> (based
> >>>> on Ioannis jaas-blog example).
> >>>> Every subpage can have different set of principals allowed to
> >> watch
> >>>> it - for example we can introduce karaf-manager and developer roles
> and
> >> so
> >>>> on.
> >>>> - Support for basic OSGi operations
> >>>> Start, stop, refresh and uninstall operations on bundles
> >>>> - Extensible bundles view which allows to add new columns
> >>>> As an example you can check blueprint module
> >>>> - Support for basic karaf operations
> >>>> Viewing, installing features, listing repositories and adding new
> >>>> ones
> >>>> - Extensible dashboard with widgets possible to be added dynamically
> by
> >>>> webconsole modules
> >>>> - Example ServiceMix extension which lists endpoints, exchanges and
> >>>> exchange details
> >>>> - Support for translations throught wicket i18n mechanism
> >>>> - Support for branding based on OSGi BrandProvider services, not only
> on
> >>>> fragment resource overrides.
> >>>>
> >>>> Felix WebConsole contains much more features eg. viewing the logs,
> >> editing
> >>>> the configurations (it's broken currently in our case) managing Karaf
> >>>> instances and so on. I started thinking about announcing our work to
> >> these
> >>>> user communities who may be interested in extensions. With them we can
> >>>> discuss scope of webconsole (and their extensions). I think we are
> close
> >> to
> >>>> stabilize core APIs and start working on first version which should be
> >>>> released before end of this year.
> >>>>
> >>>> Communities which may be involved:
> >>>> - servicemix (especially in context of smx5)
> >>>> - camel
> >>>> - felix
> >>>> - sling
> >>>> - geronimo (since it is OSGi based)
> >>>> - activemq?
> >>>> - cxf?
> >>>>
> >>>> WDYT, are we ready to ask them for help and cooperation?
> >>>>
> >>>> Best regards,
> >>>> Lukasz
> >>
> >>
>
>
Re: [WebConsole] Roadmap sketch discussion
Posted by Łukasz Dywicki <lu...@code-house.org>.
Yeah,
Integration tests will be very useful for feature installation verification (something we don't verify even in karaf core).
Anyway, will we be able to test webconsole with wicket-tester which runs in pax-exam managed container?
Best regards,
Lukasz
> Great work Lukasz. I'll contribute some integration tests the next days.
> This should increase the coverage by far and also show if something
> fundamental goes wrong suddenly.
>
> Kind regards,
> Andreas
>
> 2011/9/6 Łukasz Dywicki <lu...@code-house.org>
>
>> Hi,
>> I worked a bit on unit tests and now we have few in core. They covers base
>> elements - including BasePage, SecuredPage, authentication and
>> authorization. Also I've updated manual (which is still small) - now we have
>> small set of documentation about extensions, security and branding.
>>
>> Best regards,
>> Lukasz
>>
>>> Hey Lukas,
>>>
>>> Wow, the feature set growed really fast :-). Great work guys!
>>>
>>> Basically I think we've enough to start shouting around. Still I think
>> there
>>> are two things missing beforehand:
>>>
>>> a) We really need to introduce at least a little set of unit and
>> integration
>>> tests. People are in general more afraid to edit/extend not-tested code
>> than
>>> well tested code
>>>
>>> b) I think we need at least a little set of infrastructure and feature
>>> documentation. That would give ppl the possibility to get a good
>>> introduction and IMHO also a little bit motivation to continue it.
>>>
>>> @(a) I'm writing right now at a test framework to get up karaf as the
>> base
>>> framework in exam. The code is currently located [1]. ASAP it is stable
>> I'll
>>> push it into the karaf sandbox. We can base the webconsole integration
>> tests
>>> on that framework.
>>>
>>> WDYT?
>>>
>>> Kind regards,
>>> Andreas
>>>
>>> [1] https://github.com/fossbrain/org.fossbrain.extensions.paxexam.karaf
>>>
>>> 2011/9/2 Łukasz Dywicki <lu...@code-house.org>
>>>
>>>> Hey guys,
>>>> Since we have bunch of features in current prototype I would like to
>> start
>>>> talking about roadmap and other communities involvement.
>>>>
>>>> What we currently have:
>>>> - Security layer integrated with JAAS, also with support for roles
>> (based
>>>> on Ioannis jaas-blog example).
>>>> Every subpage can have different set of principals allowed to
>> watch
>>>> it - for example we can introduce karaf-manager and developer roles and
>> so
>>>> on.
>>>> - Support for basic OSGi operations
>>>> Start, stop, refresh and uninstall operations on bundles
>>>> - Extensible bundles view which allows to add new columns
>>>> As an example you can check blueprint module
>>>> - Support for basic karaf operations
>>>> Viewing, installing features, listing repositories and adding new
>>>> ones
>>>> - Extensible dashboard with widgets possible to be added dynamically by
>>>> webconsole modules
>>>> - Example ServiceMix extension which lists endpoints, exchanges and
>>>> exchange details
>>>> - Support for translations throught wicket i18n mechanism
>>>> - Support for branding based on OSGi BrandProvider services, not only on
>>>> fragment resource overrides.
>>>>
>>>> Felix WebConsole contains much more features eg. viewing the logs,
>> editing
>>>> the configurations (it's broken currently in our case) managing Karaf
>>>> instances and so on. I started thinking about announcing our work to
>> these
>>>> user communities who may be interested in extensions. With them we can
>>>> discuss scope of webconsole (and their extensions). I think we are close
>> to
>>>> stabilize core APIs and start working on first version which should be
>>>> released before end of this year.
>>>>
>>>> Communities which may be involved:
>>>> - servicemix (especially in context of smx5)
>>>> - camel
>>>> - felix
>>>> - sling
>>>> - geronimo (since it is OSGi based)
>>>> - activemq?
>>>> - cxf?
>>>>
>>>> WDYT, are we ready to ask them for help and cooperation?
>>>>
>>>> Best regards,
>>>> Lukasz
>>
>>
Re: [WebConsole] Roadmap sketch discussion
Posted by Andreas Pieber <an...@gmail.com>.
Great work Lukasz. I'll contribute some integration tests the next days.
This should increase the coverage by far and also show if something
fundamental goes wrong suddenly.
Kind regards,
Andreas
2011/9/6 Łukasz Dywicki <lu...@code-house.org>
> Hi,
> I worked a bit on unit tests and now we have few in core. They covers base
> elements - including BasePage, SecuredPage, authentication and
> authorization. Also I've updated manual (which is still small) - now we have
> small set of documentation about extensions, security and branding.
>
> Best regards,
> Lukasz
>
> > Hey Lukas,
> >
> > Wow, the feature set growed really fast :-). Great work guys!
> >
> > Basically I think we've enough to start shouting around. Still I think
> there
> > are two things missing beforehand:
> >
> > a) We really need to introduce at least a little set of unit and
> integration
> > tests. People are in general more afraid to edit/extend not-tested code
> than
> > well tested code
> >
> > b) I think we need at least a little set of infrastructure and feature
> > documentation. That would give ppl the possibility to get a good
> > introduction and IMHO also a little bit motivation to continue it.
> >
> > @(a) I'm writing right now at a test framework to get up karaf as the
> base
> > framework in exam. The code is currently located [1]. ASAP it is stable
> I'll
> > push it into the karaf sandbox. We can base the webconsole integration
> tests
> > on that framework.
> >
> > WDYT?
> >
> > Kind regards,
> > Andreas
> >
> > [1] https://github.com/fossbrain/org.fossbrain.extensions.paxexam.karaf
> >
> > 2011/9/2 Łukasz Dywicki <lu...@code-house.org>
> >
> >> Hey guys,
> >> Since we have bunch of features in current prototype I would like to
> start
> >> talking about roadmap and other communities involvement.
> >>
> >> What we currently have:
> >> - Security layer integrated with JAAS, also with support for roles
> (based
> >> on Ioannis jaas-blog example).
> >> Every subpage can have different set of principals allowed to
> watch
> >> it - for example we can introduce karaf-manager and developer roles and
> so
> >> on.
> >> - Support for basic OSGi operations
> >> Start, stop, refresh and uninstall operations on bundles
> >> - Extensible bundles view which allows to add new columns
> >> As an example you can check blueprint module
> >> - Support for basic karaf operations
> >> Viewing, installing features, listing repositories and adding new
> >> ones
> >> - Extensible dashboard with widgets possible to be added dynamically by
> >> webconsole modules
> >> - Example ServiceMix extension which lists endpoints, exchanges and
> >> exchange details
> >> - Support for translations throught wicket i18n mechanism
> >> - Support for branding based on OSGi BrandProvider services, not only on
> >> fragment resource overrides.
> >>
> >> Felix WebConsole contains much more features eg. viewing the logs,
> editing
> >> the configurations (it's broken currently in our case) managing Karaf
> >> instances and so on. I started thinking about announcing our work to
> these
> >> user communities who may be interested in extensions. With them we can
> >> discuss scope of webconsole (and their extensions). I think we are close
> to
> >> stabilize core APIs and start working on first version which should be
> >> released before end of this year.
> >>
> >> Communities which may be involved:
> >> - servicemix (especially in context of smx5)
> >> - camel
> >> - felix
> >> - sling
> >> - geronimo (since it is OSGi based)
> >> - activemq?
> >> - cxf?
> >>
> >> WDYT, are we ready to ask them for help and cooperation?
> >>
> >> Best regards,
> >> Lukasz
>
>
Re: [WebConsole] Roadmap sketch discussion
Posted by Łukasz Dywicki <lu...@code-house.org>.
Hi,
I worked a bit on unit tests and now we have few in core. They covers base elements - including BasePage, SecuredPage, authentication and authorization. Also I've updated manual (which is still small) - now we have small set of documentation about extensions, security and branding.
Best regards,
Lukasz
> Hey Lukas,
>
> Wow, the feature set growed really fast :-). Great work guys!
>
> Basically I think we've enough to start shouting around. Still I think there
> are two things missing beforehand:
>
> a) We really need to introduce at least a little set of unit and integration
> tests. People are in general more afraid to edit/extend not-tested code than
> well tested code
>
> b) I think we need at least a little set of infrastructure and feature
> documentation. That would give ppl the possibility to get a good
> introduction and IMHO also a little bit motivation to continue it.
>
> @(a) I'm writing right now at a test framework to get up karaf as the base
> framework in exam. The code is currently located [1]. ASAP it is stable I'll
> push it into the karaf sandbox. We can base the webconsole integration tests
> on that framework.
>
> WDYT?
>
> Kind regards,
> Andreas
>
> [1] https://github.com/fossbrain/org.fossbrain.extensions.paxexam.karaf
>
> 2011/9/2 Łukasz Dywicki <lu...@code-house.org>
>
>> Hey guys,
>> Since we have bunch of features in current prototype I would like to start
>> talking about roadmap and other communities involvement.
>>
>> What we currently have:
>> - Security layer integrated with JAAS, also with support for roles (based
>> on Ioannis jaas-blog example).
>> Every subpage can have different set of principals allowed to watch
>> it - for example we can introduce karaf-manager and developer roles and so
>> on.
>> - Support for basic OSGi operations
>> Start, stop, refresh and uninstall operations on bundles
>> - Extensible bundles view which allows to add new columns
>> As an example you can check blueprint module
>> - Support for basic karaf operations
>> Viewing, installing features, listing repositories and adding new
>> ones
>> - Extensible dashboard with widgets possible to be added dynamically by
>> webconsole modules
>> - Example ServiceMix extension which lists endpoints, exchanges and
>> exchange details
>> - Support for translations throught wicket i18n mechanism
>> - Support for branding based on OSGi BrandProvider services, not only on
>> fragment resource overrides.
>>
>> Felix WebConsole contains much more features eg. viewing the logs, editing
>> the configurations (it's broken currently in our case) managing Karaf
>> instances and so on. I started thinking about announcing our work to these
>> user communities who may be interested in extensions. With them we can
>> discuss scope of webconsole (and their extensions). I think we are close to
>> stabilize core APIs and start working on first version which should be
>> released before end of this year.
>>
>> Communities which may be involved:
>> - servicemix (especially in context of smx5)
>> - camel
>> - felix
>> - sling
>> - geronimo (since it is OSGi based)
>> - activemq?
>> - cxf?
>>
>> WDYT, are we ready to ask them for help and cooperation?
>>
>> Best regards,
>> Lukasz
Re: [WebConsole] Roadmap sketch discussion
Posted by Andreas Pieber <an...@gmail.com>.
Hey Lukas,
Wow, the feature set growed really fast :-). Great work guys!
Basically I think we've enough to start shouting around. Still I think there
are two things missing beforehand:
a) We really need to introduce at least a little set of unit and integration
tests. People are in general more afraid to edit/extend not-tested code than
well tested code
b) I think we need at least a little set of infrastructure and feature
documentation. That would give ppl the possibility to get a good
introduction and IMHO also a little bit motivation to continue it.
@(a) I'm writing right now at a test framework to get up karaf as the base
framework in exam. The code is currently located [1]. ASAP it is stable I'll
push it into the karaf sandbox. We can base the webconsole integration tests
on that framework.
WDYT?
Kind regards,
Andreas
[1] https://github.com/fossbrain/org.fossbrain.extensions.paxexam.karaf
2011/9/2 Łukasz Dywicki <lu...@code-house.org>
> Hey guys,
> Since we have bunch of features in current prototype I would like to start
> talking about roadmap and other communities involvement.
>
> What we currently have:
> - Security layer integrated with JAAS, also with support for roles (based
> on Ioannis jaas-blog example).
> Every subpage can have different set of principals allowed to watch
> it - for example we can introduce karaf-manager and developer roles and so
> on.
> - Support for basic OSGi operations
> Start, stop, refresh and uninstall operations on bundles
> - Extensible bundles view which allows to add new columns
> As an example you can check blueprint module
> - Support for basic karaf operations
> Viewing, installing features, listing repositories and adding new
> ones
> - Extensible dashboard with widgets possible to be added dynamically by
> webconsole modules
> - Example ServiceMix extension which lists endpoints, exchanges and
> exchange details
> - Support for translations throught wicket i18n mechanism
> - Support for branding based on OSGi BrandProvider services, not only on
> fragment resource overrides.
>
> Felix WebConsole contains much more features eg. viewing the logs, editing
> the configurations (it's broken currently in our case) managing Karaf
> instances and so on. I started thinking about announcing our work to these
> user communities who may be interested in extensions. With them we can
> discuss scope of webconsole (and their extensions). I think we are close to
> stabilize core APIs and start working on first version which should be
> released before end of this year.
>
> Communities which may be involved:
> - servicemix (especially in context of smx5)
> - camel
> - felix
> - sling
> - geronimo (since it is OSGi based)
> - activemq?
> - cxf?
>
> WDYT, are we ready to ask them for help and cooperation?
>
> Best regards,
> Lukasz