Re: PAX-WEB does not register servlet
Hi Richard,
not sure if this issue is still open for you, but what I observed in a
similar case is, that if there are two servlets with the same name in the
same context, this leads to one of them not being registered.
As the default name for your servlet would be javax.servlet.Servlet this
might cause your observed behavior.
In my case I solved this, by explicitly naming all my Servlets
via @HttpWhiteboardServletName("my-unique-name")
Hope that helps.
Kind regards,
Thomas
Am Di., 16. Aug. 2022 um 12:50 Uhr schrieb Grzegorz Grzybek <
gr.grzy...@gmail.com>:
> Hello
>
> If you set DEBUG logging level for org.ops4j.pax.web logger, you should
> see A LOT of information about how servlets are discovered and registered
> into the runtime. Without the logs, I can't tell much - especially if (as
> you've mentioned) it's sporadic problem...
>
> regards
> Grzegorz Grzybek
>
> pon., 8 sie 2022 o 08:23 Richard Hierlmeier
> napisał(a):
>
>>
>> I upgraded last week a system to Karaf 4.4.1. I have a sporadic problem
>> with this system.
>>
>> The system contains a small bundle with this default servlet:
>>
>> @Component(service = Servlet.class, scope = ServiceScope.PROTOTYPE)
>> @HttpWhiteboardServletPattern("/")
>> @HttpWhiteboardContextSelect("(osgi.http.whiteboard.context.path=/)")
>> public class RootServlet extends HttpServlet {
>>
>> @Override
>> protected void doGet(final HttpServletRequest req, final
>> HttpServletResponse resp)
>> throws ServletException, IOException {
>> resp.sendRedirect("/welcome/welcome.html");
>> }
>> }
>>
>> However sometimes after the start of Karaf the bundle is active but this
>> servlet is not available:
>>
>> de@root()> la -u | grep web-root
>> 37 | Active | 80 | 1.0.0.SNAPSHOT |
>> mvn:de.hierlmeier.testPaxWeb8/web-root/1.0.0-SNAPSHOT
>>
>> de@root()> ls javax.servlet.Servlet
>> [javax.servlet.Servlet]
>> ---
>> component.id = 20
>> component.name = de.hierlmeier.testPaxWeb8.webRoot.RootServlet
>> osgi.ds.satisfying.condition.target = (osgi.condition.id=true)
>> osgi.http.whiteboard.context.select =
>> (osgi.http.whiteboard.context.path=/)
>> osgi.http.whiteboard.servlet.pattern = [/]
>> service.bundleid = 37
>> service.id = 206
>> service.scope = prototype
>> Provided by :
>> web-root (37)
>> Used by:
>> web-root (37)
>>
>> de@root()> web:servlet-list | grep RootServlet
>> de@root()>
>>
>> How can I diagnose this problem?
>>
>> I am running Karaf 4.4.1 with PAX-WEB 8.0.6 on Java 8.
>>
>> Regards
>>
>> Richard
>>
>>
>>
>>
>>
>>
>>
>>
>>
Re: Karaf 4.3.3 feature:refresh results in StackOverflowError
Hi Łukasz,
thanks for that in-depth explanation.
I will have a look at my feature dependencies and come back to you.
Strangely enough, this issue seems to have solved itself since some days.
At least I can not reproduce it anymore :/
Kind regards,
Thomas
Am Mi., 29. Sept. 2021 um 22:50 Uhr schrieb Łukasz Dywicki <
l...@code-house.org>:
> Hey Thomas,
> I just got stack overflow myself and began to look for solution of my
> issue.
>
> From my past experiences I can tell you that stack overflow prior 4.3.x
> was usually result of multiple feature repositories (uris) delivering
> same feature. This might happen if you have several KARs/generated
> feature sets pulled into another feature/final assembly. All works
> separatelly but breaks when paths are crossed and packed together.
>
> You can search for it manually or simply with bash helper:
> find . -name "*.xml" -exec grep -C 4 -i "name=\"co7io-chrono" "{}" \;
> -print
>
> In my case I know issue is related to co7io-chrono feature because I
> attached debugger to see what is at the very top of stack overflow
> listed in .. stack trace. Turns out to be this feature.
>
> With above command I see that same feature is listed in few places.
>
> ./features/org.co7io.addons.feature.openhab/target/feature/feature.xml
> ./features/org.co7io.addons.feature.profile/target/feature/feature.xml
> ./bundles/org.co7io.chrono/target/test-classes/feature.xml (source)
>
> Situation for me is rather obvious the "chrono" stuff brings own feature
> descriptor which reffered in "openhab" and "profile" feature sets. Quite
> natural, isn't it? Yet due to use of feature aggregation the chrono
> feature is embedded into openhab and profile feature descriptors.
> Effectively I got 3 "co7io-chrono" features defined in three descriptors.
>
> After looking at dependency tree I found that all three feature sets are
> reffered in one build which might confuse resolver.
>
> Can you do similar deduction for your build and see if similar situation
> occurs there too?
>
> Best regards,
> Łukasz
>
>
> On 27.09.2021 15:25, Thomas Driessen wrote:
> > Hi J.B. :)
> >
> > just wanted to ask if you did find some spare time to have a look at
> > that issue?
> >
> > Kind regards,
> > Thomas
> >
> > Am Mo., 20. Sept. 2021 um 07:50 Uhr schrieb Thomas Driessen
> > mailto:thomas.driessen...@gmail.com>>:
> >
> > Hi J.B.,
> >
> > I've sent you the contents directly to your email :)
> >
> > Am Mo., 20. Sept. 2021 um 07:43 Uhr schrieb Jean-Baptiste Onofre
> > mailto:j...@nanthrax.net>>:
> >
> > Hi Thomas,
> >
> > Would it be possible to have your features definition ? I will
> > be able to take a look.
> >
> > Thanks
> > Regards
> > JB
> >
> > > Le 20 sept. 2021 à 07:27, Thomas Driessen
> > > <mailto:thomas.driessen...@gmail.com>> a écrit :
> > >
> > > Hi J.B. , hi Francois,
> > >
> > > thanks for your quick answer and sorry for the delay.
> > >
> > > Is there any way to detect such a cycle, i.e. is there a
> > command such as feature:tree like for the dependency tree in
> > maven that could help me identifying such cycles?
> > >
> > > Strange thing is: the exact same setup worked fine with Karaf
> > 4.3.2. So probably one of our referenced features in other
> > feature repositories causes this behavior.
> > >
> > >
> > > Kind regards,
> > > Thomas
> > >
> > > Am Sa., 18. Sept. 2021 um 06:22 Uhr schrieb Jean-Baptiste
> > Onofre mailto:j...@nanthrax.net>>:
> > > Hi Thomas,
> > >
> > > I think you have a loop in your features (a feature A require
> > feature B that require feature A).
> > >
> > > I know that Pax CDI has a cycle like this (I have a fix but
> > not yet released).
> > >
> > > Regards
> > > JB
> > >
> > > > Le 17 sept. 2021 à 17:00, Thomas Driessen
> > > <mailto:thomas.driessen...@gmail.com>> a écrit :
> > > >
> > > > Hi,
> > > >
>
Re: Karaf 4.3.3 feature:refresh results in StackOverflowError
Hi J.B. :) just wanted to ask if you did find some spare time to have a look at that issue? Kind regards, Thomas Am Mo., 20. Sept. 2021 um 07:50 Uhr schrieb Thomas Driessen < thomas.driessen...@gmail.com>: > Hi J.B., > > I've sent you the contents directly to your email :) > > Am Mo., 20. Sept. 2021 um 07:43 Uhr schrieb Jean-Baptiste Onofre < > j...@nanthrax.net>: > >> Hi Thomas, >> >> Would it be possible to have your features definition ? I will be able to >> take a look. >> >> Thanks >> Regards >> JB >> >> > Le 20 sept. 2021 à 07:27, Thomas Driessen >> a écrit : >> > >> > Hi J.B. , hi Francois, >> > >> > thanks for your quick answer and sorry for the delay. >> > >> > Is there any way to detect such a cycle, i.e. is there a command such >> as feature:tree like for the dependency tree in maven that could help me >> identifying such cycles? >> > >> > Strange thing is: the exact same setup worked fine with Karaf 4.3.2. So >> probably one of our referenced features in other feature repositories >> causes this behavior. >> > >> > >> > Kind regards, >> > Thomas >> > >> > Am Sa., 18. Sept. 2021 um 06:22 Uhr schrieb Jean-Baptiste Onofre < >> j...@nanthrax.net>: >> > Hi Thomas, >> > >> > I think you have a loop in your features (a feature A require feature B >> that require feature A). >> > >> > I know that Pax CDI has a cycle like this (I have a fix but not yet >> released). >> > >> > Regards >> > JB >> > >> > > Le 17 sept. 2021 à 17:00, Thomas Driessen < >> thomas.driessen...@gmail.com> a écrit : >> > > >> > > Hi, >> > > >> > > we just updated to the new Karaf 4.3.3 and suddenly we always get a >> StackOverflowError as soon as we try to do a feature:refresh: >> > > >> > > 2021-09-17T14:56:44,239 | ERROR | Karaf local console user karaf | >> ShellUtil| 44 - org.apache.karaf.shell.core - 4.3.3 >> | Exception caught while executing command >> > > java.util.concurrent.ExecutionException: java.lang.StackOverflowError >> > > at >> java.util.concurrent.FutureTask.report(FutureTask.java:122) ~[?:?] >> > > at java.util.concurrent.FutureTask.get(FutureTask.java:191) >> ~[?:?] >> > > at >> org.apache.felix.gogo.runtime.CommandSessionImpl$JobImpl.run(CommandSessionImpl.java:855) >> ~[?:?] >> > > at >> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) >> ~[?:?] >> > > at java.util.concurrent.FutureTask.run(FutureTask.java:264) >> ~[?:?] >> > > at >> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) >> ~[?:?] >> > > at >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) >> ~[?:?] >> > > at java.lang.Thread.run(Thread.java:829) [?:?] >> > > Caused by: java.lang.StackOverflowError >> > > at >> org.apache.karaf.features.internal.region.Subsystem.(Subsystem.java:149) >> ~[?:?] >> > > at >> org.apache.karaf.features.internal.region.SubsystemResolver.prepare(SubsystemResolver.java:127) >> ~[?:?] >> > > at >> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:390) >> ~[?:?] >> > > at >> org.apache.karaf.features.internal.service.Deployer.handlePrerequisites(Deployer.java:1121) >> ~[?:?] >> > > at >> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:394) >> ~[?:?] >> > > at >> org.apache.karaf.features.internal.service.Deployer.handlePrerequisites(Deployer.java:1121) >> ~[?:?] >> > > at >> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:394) >> ~[?:?] >> > > at >> org.apache.karaf.features.internal.service.Deployer.handlePrerequisites(Deployer.java:1121) >> ~[?:?] >> > > at >> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:394) >> ~[?:?] >> > > at >> org.apache.karaf.features.internal.service.Deployer.handlePrerequisites(Deployer.java:1121) >> ~[?:?] >> > > at >> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:394) >> ~[
Re: Karaf 4.3.3 feature:refresh results in StackOverflowError
Hi J.B., I've sent you the contents directly to your email :) Am Mo., 20. Sept. 2021 um 07:43 Uhr schrieb Jean-Baptiste Onofre < j...@nanthrax.net>: > Hi Thomas, > > Would it be possible to have your features definition ? I will be able to > take a look. > > Thanks > Regards > JB > > > Le 20 sept. 2021 à 07:27, Thomas Driessen > a écrit : > > > > Hi J.B. , hi Francois, > > > > thanks for your quick answer and sorry for the delay. > > > > Is there any way to detect such a cycle, i.e. is there a command such as > feature:tree like for the dependency tree in maven that could help me > identifying such cycles? > > > > Strange thing is: the exact same setup worked fine with Karaf 4.3.2. So > probably one of our referenced features in other feature repositories > causes this behavior. > > > > > > Kind regards, > > Thomas > > > > Am Sa., 18. Sept. 2021 um 06:22 Uhr schrieb Jean-Baptiste Onofre < > j...@nanthrax.net>: > > Hi Thomas, > > > > I think you have a loop in your features (a feature A require feature B > that require feature A). > > > > I know that Pax CDI has a cycle like this (I have a fix but not yet > released). > > > > Regards > > JB > > > > > Le 17 sept. 2021 à 17:00, Thomas Driessen < > thomas.driessen...@gmail.com> a écrit : > > > > > > Hi, > > > > > > we just updated to the new Karaf 4.3.3 and suddenly we always get a > StackOverflowError as soon as we try to do a feature:refresh: > > > > > > 2021-09-17T14:56:44,239 | ERROR | Karaf local console user karaf | > ShellUtil| 44 - org.apache.karaf.shell.core - 4.3.3 > | Exception caught while executing command > > > java.util.concurrent.ExecutionException: java.lang.StackOverflowError > > > at java.util.concurrent.FutureTask.report(FutureTask.java:122) > ~[?:?] > > > at java.util.concurrent.FutureTask.get(FutureTask.java:191) > ~[?:?] > > > at > org.apache.felix.gogo.runtime.CommandSessionImpl$JobImpl.run(CommandSessionImpl.java:855) > ~[?:?] > > > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) > ~[?:?] > > > at java.util.concurrent.FutureTask.run(FutureTask.java:264) > ~[?:?] > > > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > ~[?:?] > > > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > ~[?:?] > > > at java.lang.Thread.run(Thread.java:829) [?:?] > > > Caused by: java.lang.StackOverflowError > > > at > org.apache.karaf.features.internal.region.Subsystem.(Subsystem.java:149) > ~[?:?] > > > at > org.apache.karaf.features.internal.region.SubsystemResolver.prepare(SubsystemResolver.java:127) > ~[?:?] > > > at > org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:390) > ~[?:?] > > > at > org.apache.karaf.features.internal.service.Deployer.handlePrerequisites(Deployer.java:1121) > ~[?:?] > > > at > org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:394) > ~[?:?] > > > at > org.apache.karaf.features.internal.service.Deployer.handlePrerequisites(Deployer.java:1121) > ~[?:?] > > > at > org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:394) > ~[?:?] > > > at > org.apache.karaf.features.internal.service.Deployer.handlePrerequisites(Deployer.java:1121) > ~[?:?] > > > at > org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:394) > ~[?:?] > > > at > org.apache.karaf.features.internal.service.Deployer.handlePrerequisites(Deployer.java:1121) > ~[?:?] > > > at > org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:394) > ~[?:?] > > > at > org.apache.karaf.features.internal.service.Deployer.handlePrerequisites(Deployer.java:1121) > ~[?:?] > > > at > org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:394) > ~[?:?] > > > at > org.apache.karaf.features.internal.service.Deployer.handlePrerequisites(Deployer.java:1121) > ~[?:?] > > > at > org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:394) > ~[?:?] > > > at > org.apache.karaf.features.internal.service.Deployer.handlePrerequisites(Deployer.java:1121) > ~[?:?] > > > at > org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:394) > ~[?:?] > > > at > org.apache.karaf.features.internal.service.Deployer.handlePrerequisites(Deployer.java:1121) > ~[?:?] > > > at > org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:394) > ~[?:?] > > > > > > Is this a known bug? Or is there anyone else experiencing this? > > > > > > Kind regards, > > > Thomas > > > >
Re: Karaf 4.3.3 feature:refresh results in StackOverflowError
Hi J.B. , hi Francois, thanks for your quick answer and sorry for the delay. Is there any way to detect such a cycle, i.e. is there a command such as feature:tree like for the dependency tree in maven that could help me identifying such cycles? Strange thing is: the exact same setup worked fine with Karaf 4.3.2. So probably one of our referenced features in other feature repositories causes this behavior. Kind regards, Thomas Am Sa., 18. Sept. 2021 um 06:22 Uhr schrieb Jean-Baptiste Onofre < j...@nanthrax.net>: > Hi Thomas, > > I think you have a loop in your features (a feature A require feature B > that require feature A). > > I know that Pax CDI has a cycle like this (I have a fix but not yet > released). > > Regards > JB > > > Le 17 sept. 2021 à 17:00, Thomas Driessen > a écrit : > > > > Hi, > > > > we just updated to the new Karaf 4.3.3 and suddenly we always get a > StackOverflowError as soon as we try to do a feature:refresh: > > > > 2021-09-17T14:56:44,239 | ERROR | Karaf local console user karaf | > ShellUtil| 44 - org.apache.karaf.shell.core - 4.3.3 > | Exception caught while executing command > > java.util.concurrent.ExecutionException: java.lang.StackOverflowError > > at java.util.concurrent.FutureTask.report(FutureTask.java:122) > ~[?:?] > > at java.util.concurrent.FutureTask.get(FutureTask.java:191) > ~[?:?] > > at > org.apache.felix.gogo.runtime.CommandSessionImpl$JobImpl.run(CommandSessionImpl.java:855) > ~[?:?] > > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) > ~[?:?] > > at java.util.concurrent.FutureTask.run(FutureTask.java:264) > ~[?:?] > > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > ~[?:?] > > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > ~[?:?] > > at java.lang.Thread.run(Thread.java:829) [?:?] > > Caused by: java.lang.StackOverflowError > > at > org.apache.karaf.features.internal.region.Subsystem.(Subsystem.java:149) > ~[?:?] > > at > org.apache.karaf.features.internal.region.SubsystemResolver.prepare(SubsystemResolver.java:127) > ~[?:?] > > at > org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:390) > ~[?:?] > > at > org.apache.karaf.features.internal.service.Deployer.handlePrerequisites(Deployer.java:1121) > ~[?:?] > > at > org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:394) > ~[?:?] > > at > org.apache.karaf.features.internal.service.Deployer.handlePrerequisites(Deployer.java:1121) > ~[?:?] > > at > org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:394) > ~[?:?] > > at > org.apache.karaf.features.internal.service.Deployer.handlePrerequisites(Deployer.java:1121) > ~[?:?] > > at > org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:394) > ~[?:?] > > at > org.apache.karaf.features.internal.service.Deployer.handlePrerequisites(Deployer.java:1121) > ~[?:?] > > at > org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:394) > ~[?:?] > > at > org.apache.karaf.features.internal.service.Deployer.handlePrerequisites(Deployer.java:1121) > ~[?:?] > > at > org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:394) > ~[?:?] > > at > org.apache.karaf.features.internal.service.Deployer.handlePrerequisites(Deployer.java:1121) > ~[?:?] > > at > org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:394) > ~[?:?] > > at > org.apache.karaf.features.internal.service.Deployer.handlePrerequisites(Deployer.java:1121) > ~[?:?] > > at > org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:394) > ~[?:?] > > at > org.apache.karaf.features.internal.service.Deployer.handlePrerequisites(Deployer.java:1121) > ~[?:?] > > at > org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:394) > ~[?:?] > > > > Is this a known bug? Or is there anyone else experiencing this? > > > > Kind regards, > > Thomas > >
Karaf 4.3.3 feature:refresh results in StackOverflowError
Hi, we just updated to the new Karaf 4.3.3 and suddenly we always get a StackOverflowError as soon as we try to do a feature:refresh: 2021-09-17T14:56:44,239 | ERROR | Karaf local console user karaf | ShellUtil| 44 - org.apache.karaf.shell.core - 4.3.3 | Exception caught while executing command java.util.concurrent.ExecutionException: java.lang.StackOverflowError at java.util.concurrent.FutureTask.report(FutureTask.java:122) ~[?:?] at java.util.concurrent.FutureTask.get(FutureTask.java:191) ~[?:?] at org.apache.felix.gogo.runtime.CommandSessionImpl$JobImpl.run(CommandSessionImpl.java:855) ~[?:?] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) ~[?:?] at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) ~[?:?] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) ~[?:?] at java.lang.Thread.run(Thread.java:829) [?:?] Caused by: java.lang.StackOverflowError at org.apache.karaf.features.internal.region.Subsystem.(Subsystem.java:149) ~[?:?] at org.apache.karaf.features.internal.region.SubsystemResolver.prepare(SubsystemResolver.java:127) ~[?:?] at org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:390) ~[?:?] at org.apache.karaf.features.internal.service.Deployer.handlePrerequisites(Deployer.java:1121) ~[?:?] at org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:394) ~[?:?] at org.apache.karaf.features.internal.service.Deployer.handlePrerequisites(Deployer.java:1121) ~[?:?] at org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:394) ~[?:?] at org.apache.karaf.features.internal.service.Deployer.handlePrerequisites(Deployer.java:1121) ~[?:?] at org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:394) ~[?:?] at org.apache.karaf.features.internal.service.Deployer.handlePrerequisites(Deployer.java:1121) ~[?:?] at org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:394) ~[?:?] at org.apache.karaf.features.internal.service.Deployer.handlePrerequisites(Deployer.java:1121) ~[?:?] at org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:394) ~[?:?] at org.apache.karaf.features.internal.service.Deployer.handlePrerequisites(Deployer.java:1121) ~[?:?] at org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:394) ~[?:?] at org.apache.karaf.features.internal.service.Deployer.handlePrerequisites(Deployer.java:1121) ~[?:?] at org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:394) ~[?:?] at org.apache.karaf.features.internal.service.Deployer.handlePrerequisites(Deployer.java:1121) ~[?:?] at org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:394) ~[?:?] Is this a known bug? Or is there anyone else experiencing this? Kind regards, Thomas
Re: [X-Mas Gift] Panel discussion about Karaf 5
Hi J.B. :) as you already teasered me, I would love to join ;) Kind regards, Thomas Oleg Cohen schrieb am Di., 15. Dez. 2020, 19:03: > Hi JB, > > Great news! This is awesome. I would love to join. > > Best regards, > Oleg > > Sent from my iPhone > > > On Dec 15, 2020, at 12:32 PM, Jean-Baptiste Onofre > wrote: > > > > Hi guys, > > > > Maybe some of you know that I started to work on Karaf 5. > > > > I have something that it’s almost "usable". > > > > Before sending a global discussion thread on the mailing list, I would > like to evaluate the ideas & big changes I did. > > > > I would like to know if some of you would be interested by a panel > discussion call to introduce Karaf 5 (limited audience at first step). > > > > The agenda of this call would be: > > 1. Pros/Cons about Karaf as it is today > > 2. Concepts in Karaf 5 (module, extension, …) > > 3. Building & running > > 4. Live demo > > > > It could be recorded/webinar style (not necessary live call) for about > 20 people at first step (both Karaf developers and users). > > The purpose is to evaluate the direction. > > > > Thoughts ? > > Who would be interested ? > > > > Thanks, > > Regards > > JB >
