Hi Jaap-
There does not need to be only one Karaf instance. A well designed modular
application can have co-located services or remote services. Karaf gives you
the option to have everything all-in-one for development and then split things
out (frontend, backend and/or service apis) at deployme
Hi,
We need to go a little deeper with springboot, we have already noted
this point here:
https://github.com/apache/karaf-minho/issues/7
regards,
Francois
On 10/11/2022 15:26, Jaap Gordijn wrote:
No one who can help me here?
Essentially, to build a dynamic frontend/backend plugin system w
Appreciate the response!
I'm currently using karaf with apache camel and Spring/osgi apps.
I think where I was getting confused is that I saw a kubernetes cluster using
cellar.. which in my head didn't make a lot of sense.
Think I'm going to play with clustering karaf with cellar, and deploying
- Spring Cloud: usually small balls of mud interacting, no crash barriers build
in for designing a clean modular and loosely coupled architecture
- Apache Karaf: OSGi providing the crash barriers to guide developers in making
the right choices creating modules by separation of concerns and commun
Hi
OK - please then change "helloboard" to "/helloboard" in your
Web-ContextPath manifest header. context path without slash is wrong
according to specification.
regards
Grzegorz Grzybek
czw., 10 lis 2022 o 15:25 Prashanth Ettaboina
napisał(a):
> Hi Grzybek,
>
> Thank you for your response.
>
No one who can help me here?
Essentially, to build a dynamic frontend/backend plugin system we have to
decide to go for:
- Spring Cloud (large community, but needs many processes / JVMs to build it
, so it seems not very efficient
- Apache Karaf (efficient system as there needs only to be one JVM,
Hi,
I'm joining JB, it's depend how you want to scale your Karaf instance,
if you don't need hot configuration reloading or dynamic feature
deployment synchronization you can use only K8S.
regards,
Francois
On 10/11/2022 10:29, Jean-Baptiste Onofré wrote:
Hi,
Actually, you can use both.
Hello
czw., 10 lis 2022 o 11:29 Prashanth Ettaboina
napisał(a):
> Hi Team,
>
> I have upgraded my Application from Karaf 4.2.15 to 4.4.1 version.
>
> As per release notes (4.4.0 and 4.4.1) I have updated Pax Web dependency
> to 8.0.6 along with Jetty to 9.4.46.v20220331
>
> The issue is Pax web
Hi,
Actually, you can use both.
Cellar brings synchronize of Karaf running instances (live, without
restarting the instances), whereas K8S can orchestrate the startup of
the Karaf instances.
Regards
JB
On Mon, Nov 7, 2022 at 7:51 PM Dana Shaw wrote:
>
> Was going thru the documentation and som
Hi Martin,
Generally speaking, I would recommend bootFeatures (startupFeatures
are more for Karaf internals or specific use cases).
Regards
JB
On Wed, Nov 9, 2022 at 11:24 AM Martin Zukal via user
wrote:
>
> Hi,
> Thanks for pointing me to the right documentation.
> So the best practice is to u
Oh by the way, Minho moved to Apache Karaf umbrella now:
https://github.com/apache/karaf-minho
Regards
JB
On Mon, Nov 7, 2022 at 12:04 PM frm wrote:
>
> Hi,
>
> I've looked at the githib repo (https://github.com/jbonofre/karaf5) at
> Minho.
> It looks very interesting to me, as I want to host mu
Hi Jaap,
We are working on the examples (we are planning several examples,
including multi spring boot apps in minho, I'm working on minho k8s
controller example, etc).
We are working on it.
Right now, the loading approach is static (at bootstrap), but if we
have user request to support dynamic l
12 matches
Mail list logo
