On Emacs, eclipse, and other things that take my fancy
🌐 Visit Steinar.bang.priv.no
🌐 Steinar.bang.priv.no besuchen
✍️Write rieview ✍️Rezension schreiben 🏷️Get Badge! 🏷️Abzeichen holen! ⚙️Edit entry ⚙️Eintrag bearbeiten 📰News 📰Neuigkeiten
Tags:
… reposted this!
7.3.2025 20:38Comment on Convert react/redux webapp from saga/axios to RTK query and RTK listener by Steinar Bang[…] I’m not opposed to learning new stuff, but I can be quite reluctant to let go of stuff I like, and I was really happy about redux saga as outlined in Yep, I’m still using redux. […]
7.3.2025 20:33Comment on Yep, I’m still using redux by Convert react/redux webapp from saga/axios to RTK query and RTK listener | Steinar Bangs bloggRedux saga is a core component of my react/redux applications. Unfortuately Redux Saga has been deprecated and haven’t seen an upgrade in the last year. This blog posts covers the replacement of redux saga and axios with RTK query and RTK listener in a react redux webapp. Introduction The structure of this blog post, is: … Continue reading Convert react/redux webapp from saga/axios to RTK query and RTK listener
7.3.2025 10:32Convert react/redux webapp from saga/axios to RTK query and RTK listener[…] is the vite.config.js file of Convert react app built with frontend-maven-plugin from webpack to vite with a plugin to extract router paths added (explanations follow the […]
27.2.2025 16:57Comment on Convert react app built with frontend-maven-plugin from webpack to vite by Export react-router routes for use in Java servlet | Steinar Ban...[…] If routes are built dynamically based on the data in the applications database (as is the case for 1990-ies picture archives in modern skin), then the servlet serving the frontend need to replicate the logic setting up the dynamic routes […]
27.2.2025 16:57Comment on 1990-ies picture archives in modern skin by Export react-router routes for use in Java servlet | Steinar Bangs bloggThis blog post describes a vite plugin that can export static react router routes into a text file, one route per line, that can be easily parsed in a Java servlet to make it possible to reload the react router paths. Summary When the react-router is used to navigate in a reactjs web application, the … Continue reading Export react-router routes for use in Java servlet
26.2.2025 19:09Export react-router routes for use in Java servlet<!-- wp:paragraph --> <p>karaf 4.4.7 has been packaged and deployed to the repository at apt.bang.priv.no.</p> <!-- /wp:paragraph --><!-- wp:paragraph --> <p>The package has been tested with openjdk-17 on debian 12.9 “bookworm” on amd64.</p> <!-- /wp:paragraph -->
4.2.2025 18:14Comment on Installing apache karaf on debian by steinarbangfrontend-karaf-demo is a small demo application that uses frontend-maven-plugin and webpack to compile a react application into static files that are included as classpath resources into a jar file together with a servlet. This blogpost describes converting the build of this application from webpack to vite
12.10.2024 11:42Convert react app built with frontend-maven-plugin from webpack to vite[…] Edit: I no longer use beans with builders, I Build Java records with builders […]
12.5.2024 09:12Comment on Build Java records with builders by Build beans better with builders | Steinar Bangs blogg[…] Java record withers what and when I discovered that the Java beans with builders resulting from Build beans better with builders could have their boiler plate code size reduced to half, if they were turned into records instead […]
12.5.2024 09:03Comment on Build beans better with builders by Build Java records with builders | Steinar Bangs blogg[…] writing Java record withers what and when I discovered that the Java beans with builders resulting from Build beans better with builders […]
12.5.2024 09:03Comment on Java record withers what and when by Build Java records with builders | Steinar Bangs bloggWhen writing Java record withers what and when I discovered that the Java beans with builders resulting from Build beans better with builders could have their boiler plate code size reduced to half, if they were turned into records instead of beans. This is the story of switching my Java beans to records and how … Continue reading Build Java records with builders
10.5.2024 21:54Build Java records with builders[…] Build beans better with builders I concluded that I would continue with my practice of hand-writing read-only beans with builders, […]
9.5.2024 20:29Comment on Build beans better with builders by Java record withers what and when | Steinar Bangs bloggThis blog post is the result of searching the internet to find out what Java records with “withers” will look like and in what version of Java records with withers will arrive. In addition, while trying to figure out Java withers, I discovered that reforming my current beans with builders into records with builders, I … Continue reading Java record withers what and when
9.5.2024 17:35Java record withers what and when<!-- wp:paragraph --> <p>karaf 4.4.6 has been packaged and deployed to the repository at apt.bang.priv.no.</p> <!-- /wp:paragraph --><!-- wp:paragraph --> <p>The package has been tested with openjdk-17 on debian 12.5 “bookworm” on amd64.</p> <!-- /wp:paragraph -->
30.4.2024 20:16Comment on Installing apache karaf on debian by steinarbangIntroduction On November 11 2021 I put trying out tailwindcss on my personal TODO list. In January 2024 I got around to trying out tailwindcss on a react.js web application and this blogpost first describes how I used it and then what I think about it. The application used in the tailwind test The test … Continue reading Trying out Tailwind CSS on a react webapp
2.2.2024 17:08Trying out Tailwind CSS on a react webappkaraf 4.4.5 has been packaged and deployed to the repository at apt.bang.priv.no. The package has been tested with openjdk-17 on debian 12.4 “bookworm” on amd64.
12.1.2024 18:26Comment on Installing apache karaf on debian by steinarbangKaraf 4.4.3 was been packaged and deployed to to the repository, January 21 2023. Karaf4.4.3 has been running both with openjdk-11 on debian 11 and openjdk-17 on debian 12. It was replaced by Karaf 4.4.4 on October 28 2023, when karaf 4.4.4 was packaged as a debian package and replaced to the repository. The karaf 4.4.4 package has been testet on openjdk-17 on debian 12.2 "bookworm" on amd64, but should in theory work on debian 12 on all architectures.
29.10.2023 08:40Comment on Installing apache karaf on debian by steinarbangIn reply to <a href="https://steinar.bang.priv.no/2018/02/10/develop-osgi-applications-using-karaf/comment-page-1/#comment-16078">aloraine2014</a>. Hi, This blog post is pretty old. 5 years is a long time in this business. :-) I first tried downloading karaf 4.1.4, but it didn't start on java17 (which is the only jre I currently have installed). So I tried with karaf 4.4.3 and followed the instructions in the blog post and got the problems you're seeing. So I tried the <a href="https://github.com/steinarb/hello-karaf-demo#how-to-install" rel="nofollow ugc">instructions in the README</a>: <code>feature:repo-add mvn:no.priv.bang.demos/hello-karaf-demo/LATEST/xml/features feature:install hello-karaf </code> and... got an error for pax-http-whiteboard missing. The built-in pax-http-whiteboard feature was renamed to just "http-whiteboard" a while back, but it looks like I didn't update the hello-karaf-demo. According to git I updated some stuff 3 months ago, but I probably never tried running it. I have now updated all maven dependencies while I was at it, and done the necessary changes for OSGi 8 SCR (which is what karaf 4.4.x uses) and the app loads from the feature So if you do <code>git pull mvn clean install</code> and then in the karaf console do <code>feature:repo-add mvn:no.priv.bang.demos/hello-karaf-demo/LATEST/xml/features feature:install hello-karaf</code> then the app should be up and running at http://localhost:8181/hello Note that I have since made more comprehensive demos than hello-karaf-demo, the last, and most complete, being https://github.com/steinarb/sampleapp (it has liquibase database setup and authentication and authorization by apache shiro)
2.7.2023 12:04Comment on Develop OSGi applications using karaf by steinarbangHi!
I am trying to run your excellent tutorial but have run into a problem.
I followed the steps exactly but got an error when I ran this step:
bundle:start mvn:no.priv.bang.demos/hello-karaf-demo/1.0.0-SNAPSHOT
The error is:
Error executing command: Error executing command on bundles:
Error starting bundle 101: Unable to resolve no.priv.bang.debug-utils.hello-karaf-demo [101](R 101.0): missing requirement [no.priv.bang.debug-utils.hello-karaf-demo [101](R 101.0)] osgi.wiring.package; (&(osgi.wiring.package=no.priv.bang.osgi.service.adapters.logservice)(version>=1.1.0)(!(version>=2.0.0))) Unresolved requirements: [[no.priv.bang.debug-utils.hello-karaf-demo [101](R 101.0)] osgi.wiring.package; (&(osgi.wiring.package=no.priv.bang.osgi.service.adapters.logservice)(version>=1.1.0)(!(version>=2.0.0)))]
I checked to see if any of the previous steps have loaded a bundle that exports no.priv.bang.osgi.service.adapters.logservice, using this command:
karaf@root()> exports | grep no.priv.bang.osgi.service.adapters.logservice
no.priv.bang.osgi.service.adapters.logservice │ 1.0.0 │ 52 │ no.priv.bang.osgi.service.adapters.logservice
This shows there is indeed a bundle that is exporting the required package no.priv.bang.osgi.service.adapters.logservice.
However, the packaged exported is version 1.0.0, and the application requires version 1.1.0 or higher and lower than 2.0.0.
Bundles currently loaded include:
karaf@root()> list --no-format
START LEVEL 100 , List Threshold: 50
32 Active 80 4.3.9 Apache Karaf :: OSGi Services :: Event
52 Active 80 1.0.0 Adapter for OSGi log service
61 Active 80 4.21.0 Apache XBean :: OSGI Bundle Utilities
62 Active 80 4.21.0 Apache XBean :: Classpath Resource Finder
90 Active 80 9.4.0 org.objectweb.asm
91 Active 80 9.4.0 org.objectweb.asm.commons
92 Active 80 9.4.0 org.objectweb.asm.tree
93 Active 80 9.4.0 org.objectweb.asm.tree.analysis
94 Active 80 9.4.0 org.objectweb.asm.util
101 Installed 80 1.0.0.SNAPSHOT Pax Web Whiteboard extender hello world application
Bundle 52 exports:
karaf@root()> exports -b 52 --no-format
no.priv.bang.osgi.service.adapters.logservice 1.0.0 52 no.priv.bang.osgi.service.adapters.logservice
Thank you very much
Ann
In reply to <a href="https://steinar.bang.priv.no/2016/09/08/making-a-java-windows-service-in-10-minutes/comment-page-1/#comment-16034">Pertimoidian</a>. (not sure how that would work, or even that it wouldn't get an error when running mvn...? But I'm approving anyway in case something has gone missing? A maven-compiler-plugin config, maybe...?)
17.12.2022 10:27Comment on Making a Java windows service in 10 minutes by steinarbangIn reply to <a href="https://steinar.bang.priv.no/2016/09/08/making-a-java-windows-service-in-10-minutes/comment-page-1/#comment-49">Runi</a>. add this at the end of the pom (but still inside project label) 1.8 1.8
13.12.2022 11:21Comment on Making a Java windows service in 10 minutes by Pertimoidiankaraf 4.4.2 has been packaged and deployed to the repository. The package has been tested with openjdk-11 on debian 11.5 “bullseye” on amd64.
2.11.2022 22:09Comment on Installing apache karaf on debian by steinarbangI discovered a while back that rename of local variables in eclipse had stopped working, and today I eventually got around to dig into it. Turns out this was caused by the lombok plugin. https://bugs.eclipse.org/bugs/show_bug.cgi?id=579168dbspy I guess another reason not to use it, no matter how nice lombok's behaviour is. A comment in the bug, said that upgrading the lombok plugin from v1.18.22 to v1.18.24 made rename in eclipse work again, and I can confirm that upgrading the plugin fixed renaming for me as well.
24.9.2022 16:41Comment on Build beans better with builders by steinarbang[…] Set up dnsmasq in my rPi raspbian router/firewall (Using a Raspberry Pi 2 Model B as a router/firewall for the home LAN) […]
31.7.2022 21:20Comment on Using a Raspberry Pi 2 Model B as a router/firewall for the home LAN by Installing debian 11 “bullseye” using PXE boot on an Acer Aspire 5 ...[…] Debian with Gnome 2, was what the netbooks were running until their SSDs died. Debian with Gnome 2, was also what I installed on what was until now, my latest linux laptop install Installing debian “squeeze” with PXE boot on a Samsung N145 Plus netbook. […]
31.7.2022 21:20Comment on Installing debian “squeeze” with PXE boot on a Samsung N145 Plus netbook by Installing debian 11 “bullseye” using PXE boot on an Acer Aspir...I installed GNU/linux on a laptop, for the first time since 2012. And the install was mostly trouble free. I spent a little time on getting the PXE boot working and getting the wireless NIC working, but other than that everything I’ve tried has been working smoothly (display, sound, keyboard, touchpad and suspend/resume). Back in … Continue reading Installing debian 11 “bullseye” using PXE boot on an Acer Aspire 5 A515-45 laptop
31.7.2022 15:26Installing debian 11 “bullseye” using PXE boot on an Acer Aspire 5 A515-45 laptopkaraf 4.4.1 has been packaged and deployed to the repository. The package has been tested with openjdk-11 on debian 11.4 "bullseye" on amd64. Maintenance update to karaf 4.4.1 (upgrade to Pax Web 8.0.6, Pax URL 2.6.11, Pax Logging 2.1.3).
25.7.2022 09:31Comment on Installing apache karaf on debian by steinarbangWhy I’m still using redux and how I’m currently using redux. One thing I’ve heard a lot recently, when other frontend people have taken a look at my code, is the question “Are you still using redux? That’s so wonderfully quaint and old fashioned. When we threw it out and started using useState() hooks our … Continue reading Yep, I’m still using redux
28.6.2022 20:08Yep, I’m still using redux[…] It’s convenient to use redux actions for things not releated to the redux store (in my case: asynchronous network traffic and react-router navigation, for example it was the combination of redux actions and the react-router that gave me a simple way to implement navigation on swipe left and right, in 1990-ies picture archives in modern skin) […]
28.6.2022 20:07Comment on 1990-ies picture archives in modern skin by Yep, I’m still using redux | Steinar Bangs bloggI replaced “react-datepicker” in two of my react applications, with the built-in <input type=”date”/> date picker, and the resulting reductions in bundle.js size were so significant I felt the need to blog about it. I recently was told about <input type=”date”/> by a colleague, who described as “the simplest datepicker you can use”. At the … Continue reading Replacing react-datepicker with HTML input element of type date
18.6.2022 14:35Replacing react-datepicker with HTML input element of type datekaraf 4.4.0 has been packaged and deployed to the repository. The package has been tested with openjdk-11 on debian 11.3 "bullseye" on amd64. This version uses OSGi 8 and pax-web 8.0.x and pax logging 2.1.x, Note: this version uses an embedded OSGi framework, since the debian-packaged OSGi framework is still OSGi 7. Note2: if pax-web won't start, check that the settings in /etc/karaf/org.ops4j.pax.web.cfg refer to files in /etc/karaf/ rather than /usr/local/karaf/etc/, and edit org.ops4j.pax.web.cfg and restart karaf, if the settings need to be changed.
2.6.2022 15:23Comment on Installing apache karaf on debian by steinarbangkaraf 4.3.7 has been packaged and deployed to the repository. The package has been tested with openjdk-11 on debian 11.3 "bullseye" on amd64. When upgrading from 4.3.6, the config.properties files is seen as modified by user. Just pick the maintainer’s version.
22.5.2022 07:51Comment on Installing apache karaf on debian by steinarbang[…] This is an apache karaf based webapp consisting of multiple maven modules loaded together in different combinations, as outlined in Composing applications with karaf features. […]
14.2.2022 20:40Comment on Composing applications with karaf features by 1990-ies picture archives in modern skin | Steinar Bangs blogg[…] To support all web crawlers, server side rendering of the pages would need to be done, and that won’t happen with the architecture I have chosen (Simplified delivery of react.js from apache karaf). […]
12.2.2022 18:45Comment on Simplified delivery of react.js from apache karaf by 1990-ies picture archives in modern skin | Steinar Bangs bloggI have written a reactjs web application, that displays images from a 1990-is picture archive in a modern, mobile friendly UI, that also tries to use the available space on large displays (responsive layout from bootstrap v4). The URLs of both the individual pictures and albums, contains opengraph and twitter card meta tags, that makes … Continue reading 1990-ies picture archives in modern skin
12.2.2022 18:451990-ies picture archives in modern skinEdit: I no longer use beans with builders, I Build Java records with builders Builders provide a nice, if verbose, way to create immutable java beans. The upsides are a nice syntax for creating immutable beans, and a way to provide copy-on-write behaviour for immutable objects. The downsides are the need for verbose boilerplate code, … Continue reading Build beans better with builders
27.1.2022 23:10Build beans better with buildersExample code for this blog post, with unit tests, can be found at https://github.com/steinarb/optionaldemo
23.1.2022 15:59Comment on Chaining Optionals using flatMap and map by steinarbang[…] see also Chaining Optionals using flatMap and map for a different way of chaining optional […]
23.1.2022 15:58Comment on Chaining Optionals using flatMap and map by How I learnt to like Optional | Steinar Bangs blogg[…] blog post How I learnt to like Optional shows an example of how to chain Optional values safely, using Optional.orElse() to provide empty […]
23.1.2022 10:05Comment on How I learnt to like Optional by Chaining Optionals using flatMap and map | Steinar Bangs bloggThe blog post How I learnt to like Optional shows an example of how to chain Optional values safely, using Optional.orElse() to provide empty objects for the next level in the chain. This blog post uses Optional.flatMap() and Optional.map(), to achieve the same thing, without having to create the empty objects, and without doing any … Continue reading Chaining Optionals using flatMap and map
18.1.2022 16:58Chaining Optionals using flatMap and mapExample code for this blog post can be found at https://github.com/steinarb/optionaldemo
17.1.2022 22:50Comment on How I learnt to like Optional by steinarbangkaraf 4.3.6 has been packaged and deployed to the repository. Important fixes wrt karaf 4.3.5: - upgrade to Pax Logging 2.0.14 with log4j 2.17.1 (fixing CVE-2021-44832) - fix deployment issue by upgrading to Apache Felix FileInstall 3.7.4 In addition, the embedded OSGi framework has been replaced with a dependency on the debian packaged OSGi framework, since the debian packaged OSGi framwork is version 7 in the current debian stable (11.2 "bullseye"). The package has been tested with openjdk-11 on debian 11.2 “bullseye” on amd64. When upgrading from 4.3.5, the config.properties files is seen as modified by user. Just pick the maintainer’s version.
15.1.2022 13:53Comment on Installing apache karaf on debian by steinarbangThank you so much for the article, saved my day!
4.1.2022 15:24Comment on How to get test coverage back in sonarcloud maven builds by Logankaraf 4.3.5 has been packaged and deployed to the repository. More logging fixes wrt karaf 4.3.4: - with logback 1.2.9 upgrade, fixing CVE-2021-42550 - with log4j 2.17.0 upgrade, fixing CVE-2021-45105 The package has been tested with openjdk-11 on debian 11.2 “bullseye” on amd64. When upgrading from 4.3.4, the config.properties files is seen as modified by user. Just pick the maintainer’s version.
28.12.2021 21:09Comment on Installing apache karaf on debian by steinarbangI used to see Optional<Something> as a completely useless addition to Java, adding to the bloat of Java without being any clearer than checking if a reference is null. I have changed my mind, and now think Optional<> can be useful in making code simpler, easier to understand, and more robust. The reason I changed … Continue reading How I learnt to like Optional
28.12.2021 07:17How I learnt to like Optionalkaraf 4.3.4 has been packaged and deployed to the repository. This version fixes the log4j vulnerability issue The package has been tested with openjdk-11 on debian 11.2 “bullseye” on amd64. When upgrading from 4.3.3, the config.properties files is seen as modified by user. Just pick the maintainer’s version.
27.12.2021 19:17Comment on Installing apache karaf on debian by steinarbangkaraf 4.3.3 has been packaged and deployed to the repository. The package has been tested with openjdk-11 on debian 11.1 “bullseye” on amd64. When upgrading from 4.3.2, the config.properties files is seen as modified by user. Just pick the maintainer's version. There was no need to modify config files to re-open ssh after the upgrade. Don't know if this means the defaults have changed on karaf, or if my modifications in the previous comment was preserved...?
10.10.2021 17:07Comment on Installing apache karaf on debian by steinarbangkaraf 4.3.2 has been packaged and deployed to the repository. The package has been tested with openjdk-11 on debian 10.9 “buster” on amd64 Note on this release: karaf 4.3.2 comes with a users.properties file with the users and groups commented out and the .deb package will replace your /etc/karaf/users.properties with this file. And with users and groups in users.properties commented out it will not be possible to ssh in. So you will need to either not let the .deb package replace your users.properties file or fix the one the .deb package puts in after the install.
22.5.2021 21:21Comment on Installing apache karaf on debian by steinarbangNote that the project has been updated and the react frontend has been rewritten to use redux toolkit and restructured to match modern react/redux applications.
9.5.2021 18:07Comment on Deliver react.js from apache karaf by steinarbangkaraf 4.3.0 has been packaged and deployed to the repository. The package has been tested with openjdk-11 on debian 10.9 "buster" on amd64
13.4.2021 17:09Comment on Installing apache karaf on debian by steinarbangThank you for your tutorial. It seems that pk-update-icon will become obsolete. The new package responsible for updates notifications is called package-update-indicator.
25.9.2020 06:41Comment on Get update notifications in the MATE desktop on debian jessie by LiviuKaraf 4.2.9 has been packaged and deployed to the repository. The package has been testet with openjdk-11 on debian 10.5 "buster" on amd64. <em>Note!</em> The release have been signed with the same key as karaf 4.2.8. If you added this key to apt with 4.2.8 you don't' have to do anything, but if not the key must be added (adding the key is part of the apt-key command example of the blog post).
20.9.2020 14:20Comment on Installing apache karaf on debian by steinarbang[…] differs from twitter in that, like diaspora, it is not under corporate control. Also like diaspora, Mastodon is a non-profit, user-owned, […]
27.6.2020 12:03Comment on Join diaspora and slowly posting a wordpress RSS/atom feed by Join mastodon and slowly posting a wordpress RSS/atom feed | Steinar Bangs bl...Mastodon is a social network that appears similar to twitter: you get a feed where you can see “toots” instead of “tweets” and you can send your own toots that will be seen by others listening to you or looking for a hashtag found in your toot. Mastodon differs from twitter in that, like diaspora, … Continue reading Join mastodon and slowly posting a wordpress RSS/atom feed
27.6.2020 11:59Join mastodon and slowly posting a wordpress RSS/atom feedDiaspora is a social network that appears to similar to Facebook in its behaviour: you get a web UI with a feed, and what ends up in that feed comes from your friends and your groups and what hashtags you filter for. Diaspora differs from Facebook in that it is not under corporate control. Diaspora, … Continue reading Join diaspora and slowly posting a wordpress RSS/atom feed
17.6.2020 16:05Join diaspora and slowly posting a wordpress RSS/atom feed[…] Edit: I got tired of copy-pasting the above code, so I packed it up in a base class and deployed it to maven central. It’s available under the Apache v2 license (see also Simplified delivery of react.js from apache karaf) […]
2.5.2020 08:43Comment on Simplified delivery of react.js from apache karaf by A Java programmers guide to delivering webapp frontends | Steinar Bangs blogg[…] I have a maven-centric approach to web frontends, instead of the more common node centric approach. I won’t detail the approach here, since I’ve already done so in Deliver react.js from apache karaf and Simplified delivery of react.js from apache karaf. […]
5.4.2020 13:06Comment on Simplified delivery of react.js from apache karaf by Composing applications with karaf features | Steinar Bangs blogg[…] node centric approach. I won’t detail the approach here, since I’ve already done so in Deliver react.js from apache karaf and Simplified delivery of react.js from apache […]
5.4.2020 13:06Comment on Deliver react.js from apache karaf by Composing applications with karaf features | Steinar Bangs blogg[…] I create a DS component that subclasses the Jersey ServletContainer and exposes Servlet as an OSGi interface, hooking into the OSGi web whiteboard and the webcontext created by the web securiy bundle (I have created a ServletContainer subclass that simplifies this process) […]
5.4.2020 13:06Comment on Simplified REST APIs from karaf using Jersey by Composing applications with karaf features | Steinar Bangs bloggI create web applications by first creating a set of OSGi bundles that form the building blocks of the application, and then use karaf features to pull the building blocks together to create complete applications that run inside apache karaf. The bundles are (in order of initial creation, and (more or less) order of maven … Continue reading Composing applications with karaf features
5.4.2020 13:03Composing applications with karaf featuresI use travis-ci to build my github projects and use sonarcloud to do analysis of the builds. In the start of January 2020, the test coverage percentage on all sonarcloud projects suddenly dropped to 0%. This blog post explains why coverage percentage dropped to 0% and how to get the test coverage back in the … Continue reading How to get test coverage back in sonarcloud maven builds
30.3.2020 19:51How to get test coverage back in sonarcloud maven builds[…] creating a REST API using jersey has been made simpler, see Simplified REST APIs from karaf using Jersey for […]
20.3.2020 22:04Comment on Simplified REST APIs from karaf using Jersey by Use Jersey to provide REST APIs from karaf applications | Steinar Bangs blogg[…] delivering react.js has been made simpler, see Simplified delivery of react.js from apache karaf for […]
20.3.2020 22:01Comment on Simplified delivery of react.js from apache karaf by Deliver react.js from apache karaf | Steinar Bangs blogg[…] The JerseyServlet simplifies the approach outlined in Use Jersey to provide REST APIs from karaf applications. […]
20.3.2020 17:27Comment on Use Jersey to provide REST APIs from karaf applications by Simplified REST APIs from karaf using Jersey | Steinar Bangs bloggI have written the Java class JerseyServlet which is intended as a base class for DS (Declarative Services) components providing Servlet services to the OSGi web whiteboard. The JerseyServlet simplifies the approach outlined in Use Jersey to provide REST APIs from karaf applications. The JerseyServlet extends the Jersey ServletContainer to add two things: A default value … Continue reading Simplified REST APIs from karaf using Jersey
20.3.2020 17:27Simplified REST APIs from karaf using Jersey[…] go into the structure of the files that must be served. See Deliver react.js from apache karaf and A Java programmers guide to delivering webapp frontends to get an overview of […]
16.3.2020 19:56Comment on A Java programmer’s guide to delivering webapp frontends by Simplified delivery of react.js from apache karaf | Steinar Bangs blogg[…] article won’t go into the structure of the files that must be served. See Deliver react.js from apache karaf and A Java programmers guide to delivering webapp frontends to get an overview of […]
16.3.2020 19:56Comment on Deliver react.js from apache karaf by Simplified delivery of react.js from apache karaf | Steinar Bangs bloggThis article is about a new servlet base class I have created to simplify serving up javascript frontends from the OSGi web whiteboard. This article won’t go into the structure of the files that must be served. See Deliver react.js from apache karaf and A Java programmers guide to delivering webapp frontends to get an overview … Continue reading Simplified delivery of react.js from apache karaf
16.3.2020 19:56Simplified delivery of react.js from apache karafKaraf 4.2.8 has been packaged and deployed to the repository. The package has been testet with openjdk-11. <em>Note</em>! I needed to sign with a different gpg key because of <a href="https://github.com/aptly-dev/aptly/issues/628" rel="nofollow ugc">an aptly bug</a>, so this key must be added to apt. I have added install of maven_pub.gpg to the apt-key command example in the blog post above <em>Note2</em>! There is <a href="https://issues.apache.org/jira/browse/KARAF-6613" rel="nofollow ugc">a bug in karaf 4.2.8 that makes paste not work in an ssh login</a>. This means that e..g. copy/pasting in config examples and install command examples does not work in karaf 4.2.8
9.2.2020 13:55Comment on Installing apache karaf on debian by steinarbangEdited the line added to /etc/apt/sources.list to add "[trusted=yes]". Without this setting "apt updated" refuses to use the repository.
8.2.2020 19:24Comment on Faking a debian repository for package development by steinarbangOSGi is a Java plugin framework and module system that were initially created for supporting embdedded applications in the automotive industry. OSGi also forms the foundations for the Eclipse IDE plugin model. The plugin model of OSGi consists of components waiting for services and starting and exposing services when all of the dependencies are satsified. … Continue reading My OSGi story
23.12.2019 08:42My OSGi story[…] I no longer use this approach. I use pax-jdbc-config instead. See the article Rewriting applications to use pax-jdbc-config and liquibase for […]
15.12.2019 17:44Comment on Rewriting applications to use pax-jdbc-config and liquibase by Pluggable databases for apache karaf applications | Steinar Bangs blogg[…] creating the post Pluggable databases for apache karaf applications I posted a link to the blog post in the karaf user mailing list, and the immediate response was, […]
15.12.2019 17:42Comment on Pluggable databases for apache karaf applications by Rewriting applications to use pax-jdbc-config and liquibase | Steinar Bangs bloggAfter creating the post Pluggable databases for apache karaf applications I posted a link to the blog post in the karaf user mailing list, and the immediate response was, “why didn’t I just pax-jdbc-config instead?“. The answer to that is that I didn’t know about pax-jdbc-config. I started using pax-jdbc in the summer of 2016, … Continue reading Rewriting applications to use pax-jdbc-config and liquibase
30.11.2019 11:51Rewriting applications to use pax-jdbc-config and liquibase[…] webapps had no performance issues on my development machine even when running with a full desktop, IDE and other stuff. The webapps on the VPS also seemed to […]
28.11.2019 22:17Comment on Debian “jessie” on Intel “Skylake” by How I learnt about linux’ “OOM Killer” | Steinar Bangs bloggThis blog post describes how I discovered a linux feature called “OOM Killer” that can have strange effects if it interrupts a program at a place where it really shouldn’t be interrupted. I have a low-end VPS (Virtual Private Server), or at least: it used to be low-end, now it’s at least one step above … Continue reading How I learned about linux’ “OOM Killer”
28.11.2019 22:17How I learned about linux’ “OOM Killer”Edit: I no longer use this approach. I use pax-jdbc-config instead. See the article Rewriting applications to use pax-jdbc-config and liquibase for details When creating databases for my apache karaf based web applications, I want the following things: A database-independent schema creation using liquibase (i.e. supporting multiple relational database systems) Pluggable databases (each web application typically … Continue reading Pluggable databases for apache karaf applications
26.10.2019 10:17Pluggable databases for apache karaf applicationsWhen I started investigating (googling) web frontends, I found tutorials for various frameworks and I found tutorials using node.js to deliver frontends to web browsers on localhost. What I did not find, was something telling me how I should pack up and deliver the webapp frontend from my production system, so that comes here: A … Continue reading A Java programmer’s guide to delivering webapp frontends
12.10.2019 17:33A Java programmer’s guide to delivering webapp frontendsHi, there isn't anything in the https://github.com/steinarb/hello-karaf-demo that pulls in stuff from camel so that's not surprising. :-) Here's a karaf exampe that uses camel with OSGi blueprint (which is a different dependency injection method to SCR aka. DS ("Declarative Services") that the hello-karaf example uses): https://github.com/apache/karaf/tree/master/examples/karaf-camel-example Here's some dated (4 year old) documentation that describes how to use camel with SCR/DS: https://cwiki.apache.org/confluence/display/CAMEL/Camel+and+SCR (all maven references are probably dated, but the SCR annotations like e.g. @Component looks current) Unfortunately I don't use camel myself so that's the best I can do. But it might be an idea to as the karaf-users list for tips: https://cwiki.apache.org/confluence/display/KARAF/Mailing+Lists
7.10.2019 15:26Comment on Develop OSGi applications using karaf by steinarbangUsing above example, I tried start camel context using init method of servlet but it is gibving below error:- org.apache.camel.RuntimeCamelException: java.lang.ClassNotFoundException: org.apache.camel.converter.stream.StreamCacheConverterLoader at org.apache.camel.RuntimeCamelException.wrapRuntimeException(RuntimeCamelException.java:68) at org.apache.camel.support.service.ServiceSupport.start(ServiceSupport.java:112) at org.apache.camel.support.service.ServiceHelper.startService(ServiceHelper.java:71) at org.apache.camel.impl.engine.AbstractCamelContext.internalAddService(AbstractCamelContext.java:1407) at org.apache.camel.impl.engine.AbstractCamelContext.doAddService(AbstractCamelContext.java:1357) at org.apache.camel.impl.engine.AbstractCamelContext.doAddService(AbstractCamelContext.java:1352) at org.apache.camel.impl.engine.AbstractCamelContext.doAddService(AbstractCamelContext.java:1348) at org.apache.camel.impl.engine.AbstractCamelContext.setTypeConverter(AbstractCamelContext.java:1699) at org.apache.camel.impl.engine.AbstractCamelContext.getTypeConverter(AbstractCamelContext.java:1691) at org.apache.camel.impl.engine.AbstractCamelContext.doStartStandardServices(AbstractCamelContext.java:3306) at org.apache.camel.impl.AbstractModelCamelContext.doStartStandardServices(AbstractModelCamelContext.java:283) at org.apache.camel.impl.engine.AbstractCamelContext.forceLazyInitialization(AbstractCamelContext.java:3296) at org.apache.camel.impl.engine.AbstractCamelContext.doStartCamel(AbstractCamelContext.java:2550) at org.apache.camel.impl.engine.AbstractCamelContext.lambda$doStart$2(AbstractCamelContext.java:2439) at org.apache.camel.impl.engine.AbstractCamelContext.doWithDefinedClassLoader(AbstractCamelContext.java:2456) at org.apache.camel.impl.engine.AbstractCamelContext.doStart(AbstractCamelContext.java:2437) at org.apache.camel.support.service.ServiceSupport.start(ServiceSupport.java:99) at org.apache.camel.impl.engine.AbstractCamelContext.start(AbstractCamelContext.java:2346) at co.hotwax.initializers.CamelService.init(CamelService.java:56) at javax.servlet.GenericServlet.init(GenericServlet.java:244)
7.10.2019 09:32Comment on Develop OSGi applications using karaf by JaiprakashIf your plugin gets startup problems and you finds messages like this in karaf.log, then the problem is receiving javax.inject from multiple bundles: <code> 2019-03-09T12:33:14,425 | WARN | features-1-thread-1 | authservice | 1127 - org.eclipse.jetty.util - 9.3.24.v20180605 | unavailable java.lang.IllegalStateException: InjectionManagerFactory not found. at org.glassfish.jersey.internal.inject.Injections.lambda$lookupInjectionManagerFactory$0(Injections.java:98) ~[1147:org.glassfish.jersey.core.jersey-common:2.27.0] at java.util.Optional.orElseThrow(Optional.java:290) ~[?:?] at org.glassfish.jersey.internal.inject.Injections.lookupInjectionManagerFactory(Injections.java:98) ~[1147:org.glassfish.jersey.core.jersey-common:2.27.0] at org.glassfish.jersey.internal.inject.Injections.createInjectionManager(Injections.java:93) ~[1147:org.glassfish.jersey.core.jersey-common:2.27.0] at org.glassfish.jersey.server.ApplicationHandler.(ApplicationHandler.java:282) ~[1148:org.glassfish.jersey.core.jersey-server:2.27.0] at org.glassfish.jersey.servlet.WebComponent.(WebComponent.java:335) ~[1145:org.glassfish.jersey.containers.jersey-container-servlet-core:2.27.0] at org.glassfish.jersey.servlet.ServletContainer.init(ServletContainer.java:178) ~[1145:org.glassfish.jersey.containers.jersey-container-servlet-core:2.27.0] at no.priv.bang.authservice.web.security.AuthserviceServlet.init(AuthserviceServlet.java:69) ~[1093:no.priv.bang.authservice.web.security:1.0.0.SNAPSHOT] at org.glassfish.jersey.servlet.ServletContainer.init(ServletContainer.java:370) ~[1145:org.glassfish.jersey.containers.jersey-container-servlet-core:2.27.0] at javax.servlet.GenericServlet.init(GenericServlet.java:244) ~[1086:javax.servlet-api:3.1.0] at org.eclipse.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:643) ~[1125:org.eclipse.jetty.servlet:9.3.24.v20180605] at org.eclipse.jetty.servlet.ServletHolder.initialize(ServletHolder.java:422) ~[1125:org.eclipse.jetty.servlet:9.3.24.v20180605] at org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:892) ~[1125:org.eclipse.jetty.servlet:9.3.24.v20180605] at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:349) ~[1125:org.eclipse.jetty.servlet:9.3.24.v20180605] at org.ops4j.pax.web.service.jetty.internal.HttpServiceContext.startContext(HttpServiceContext.java:444) ~[1159:org.ops4j.pax.web.pax-web-jetty:6.0.11] at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:778) ~[1124:org.eclipse.jetty.server:9.3.24.v20180605] at org.eclipse.jetty.servlet.ServletContextHandler.doStart(ServletContextHandler.java:262) ~[1125:org.eclipse.jetty.servlet:9.3.24.v20180605] at org.ops4j.pax.web.service.jetty.internal.HttpServiceContext.doStart(HttpServiceContext.java:270) ~[1159:org.ops4j.pax.web.pax-web-jetty:6.0.11] at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) ~[1127:org.eclipse.jetty.util:9.3.24.v20180605] at org.ops4j.pax.web.service.jetty.internal.JettyServerImpl$1.start(JettyServerImpl.java:328) ~[1159:org.ops4j.pax.web.pax-web-jetty:6.0.11] at org.ops4j.pax.web.service.internal.HttpServiceStarted.registerFilter(HttpServiceStarted.java:626) ~[?:?] at org.ops4j.pax.web.service.internal.HttpServiceStarted.registerFilter(HttpServiceStarted.java:598) ~[?:?] at org.ops4j.pax.web.service.internal.HttpServiceProxy.registerFilter(HttpServiceProxy.java:212) ~[?:?] at org.ops4j.pax.web.extender.whiteboard.internal.element.FilterWebElement.register(FilterWebElement.java:61) ~[?:?] at org.ops4j.pax.web.extender.whiteboard.internal.WebApplication.registerWebElement(WebApplication.java:392) ~[?:?] at org.ops4j.pax.web.extender.whiteboard.internal.WebApplication.addWebElement(WebApplication.java:199) ~[?:?] at org.ops4j.pax.web.extender.whiteboard.internal.tracker.AbstractTracker.addingService(AbstractTracker.java:193) ~[?:?] at org.ops4j.pax.web.extender.whiteboard.internal.tracker.AbstractTracker.addingService(AbstractTracker.java:46) ~[?:?] at org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:941) ~[?:?] at org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:870) ~[?:?] at org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:256) ~[?:?] at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:229) ~[?:?] at org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:901) ~[?:?] at org.apache.felix.framework.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:990) ~[?:?] at org.apache.felix.framework.EventDispatcher.fireEventImmediately(EventDispatcher.java:838) ~[?:?] at org.apache.felix.framework.EventDispatcher.fireServiceEvent(EventDispatcher.java:545) ~[?:?] at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:4595) ~[?:?] at org.apache.felix.framework.Felix.registerService(Felix.java:3587) ~[?:?] at org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:348) ~[?:?] at org.apache.felix.scr.impl.manager.AbstractComponentManager$3.register(AbstractComponentManager.java:903) ~[?:?] at org.apache.felix.scr.impl.manager.AbstractComponentManager$3.register(AbstractComponentManager.java:890) ~[?:?] at org.apache.felix.scr.impl.manager.RegistrationManager.changeRegistration(RegistrationManager.java:132) ~[?:?] at org.apache.felix.scr.impl.manager.AbstractComponentManager.registerService(AbstractComponentManager.java:957) ~[?:?] at org.apache.felix.scr.impl.manager.AbstractComponentManager.activateInternal(AbstractComponentManager.java:741) ~[?:?] at org.apache.felix.scr.impl.manager.AbstractComponentManager.enableInternal(AbstractComponentManager.java:675) ~[?:?] at org.apache.felix.scr.impl.manager.AbstractComponentManager.enable(AbstractComponentManager.java:430) ~[?:?] at org.apache.felix.scr.impl.manager.ConfigurableComponentHolder.enableComponents(ConfigurableComponentHolder.java:657) ~[?:?] at org.apache.felix.scr.impl.BundleComponentActivator.initialEnable(BundleComponentActivator.java:341) ~[?:?] at org.apache.felix.scr.impl.Activator.loadComponents(Activator.java:387) ~[?:?] at org.apache.felix.scr.impl.Activator.access$200(Activator.java:52) ~[?:?] at org.apache.felix.scr.impl.Activator$ScrExtension.start(Activator.java:262) ~[?:?] at org.apache.felix.scr.impl.AbstractExtender.createExtension(AbstractExtender.java:196) ~[?:?] at org.apache.felix.scr.impl.AbstractExtender.modifiedBundle(AbstractExtender.java:169) ~[?:?] at org.apache.felix.scr.impl.AbstractExtender.modifiedBundle(AbstractExtender.java:49) ~[?:?] at org.osgi.util.tracker.BundleTracker$Tracked.customizerModified(BundleTracker.java:482) ~[?:?] at org.osgi.util.tracker.BundleTracker$Tracked.customizerModified(BundleTracker.java:415) ~[?:?] at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:232) ~[?:?] at org.osgi.util.tracker.BundleTracker$Tracked.bundleChanged(BundleTracker.java:444) ~[?:?] at org.apache.felix.framework.EventDispatcher.invokeBundleListenerCallback(EventDispatcher.java:915) ~[?:?] at org.apache.felix.framework.EventDispatcher.fireEventImmediately(EventDispatcher.java:834) ~[?:?] at org.apache.felix.framework.EventDispatcher.fireBundleEvent(EventDispatcher.java:516) ~[?:?] at org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:4579) ~[?:?] at org.apache.felix.framework.Felix.startBundle(Felix.java:2174) ~[?:?] at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:998) ~[?:?] at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:984) ~[?:?] at org.apache.karaf.features.internal.service.FeaturesServiceImpl.startBundle(FeaturesServiceImpl.java:1361) ~[?:?] at org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:894) ~[?:?] at org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1248) ~[?:?] at org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$1(FeaturesServiceImpl.java:1147) ~[?:?] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?] at java.lang.Thread.run(Thread.java:748) [?:?] 2019-03-09T12:33:14,441 | ERROR | features-1-thread-1 | HttpServiceStarted | - - | Could not start the servlet context for context path [authservice] javax.servlet.ServletException: authservice@e8f8bc0d==no.priv.bang.authservice.web.security.AuthserviceServlet,jsp=null,order=-1,inst=false at org.eclipse.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:664) ~[?:?] at org.eclipse.jetty.servlet.ServletHolder.initialize(ServletHolder.java:422) ~[?:?] at org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:892) ~[?:?] at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:349) ~[?:?] at org.ops4j.pax.web.service.jetty.internal.HttpServiceContext.startContext(HttpServiceContext.java:444) ~[?:?] at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:778) ~[?:?] at org.eclipse.jetty.servlet.ServletContextHandler.doStart(ServletContextHandler.java:262) ~[?:?] at org.ops4j.pax.web.service.jetty.internal.HttpServiceContext.doStart(HttpServiceContext.java:270) ~[?:?] at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) ~[?:?] at org.ops4j.pax.web.service.jetty.internal.JettyServerImpl$1.start(JettyServerImpl.java:328) ~[?:?] at org.ops4j.pax.web.service.internal.HttpServiceStarted.registerFilter(HttpServiceStarted.java:626) ~[?:?] at org.ops4j.pax.web.service.internal.HttpServiceStarted.registerFilter(HttpServiceStarted.java:598) ~[?:?] at org.ops4j.pax.web.service.internal.HttpServiceProxy.registerFilter(HttpServiceProxy.java:212) ~[?:?] at org.ops4j.pax.web.extender.whiteboard.internal.element.FilterWebElement.register(FilterWebElement.java:61) ~[?:?] at org.ops4j.pax.web.extender.whiteboard.internal.WebApplication.registerWebElement(WebApplication.java:392) ~[?:?] at org.ops4j.pax.web.extender.whiteboard.internal.WebApplication.addWebElement(WebApplication.java:199) ~[?:?] at org.ops4j.pax.web.extender.whiteboard.internal.tracker.AbstractTracker.addingService(AbstractTracker.java:193) ~[?:?] at org.ops4j.pax.web.extender.whiteboard.internal.tracker.AbstractTracker.addingService(AbstractTracker.java:46) ~[?:?] at org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:941) ~[?:?] at org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:870) ~[?:?] at org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:256) ~[?:?] at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:229) ~[?:?] at org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:901) ~[?:?] at org.apache.felix.framework.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:990) ~[?:?] at org.apache.felix.framework.EventDispatcher.fireEventImmediately(EventDispatcher.java:838) ~[?:?] at org.apache.felix.framework.EventDispatcher.fireServiceEvent(EventDispatcher.java:545) ~[?:?] at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:4595) ~[?:?] at org.apache.felix.framework.Felix.registerService(Felix.java:3587) ~[?:?] at org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:348) ~[?:?] at org.apache.felix.scr.impl.manager.AbstractComponentManager$3.register(AbstractComponentManager.java:903) ~[?:?] at org.apache.felix.scr.impl.manager.AbstractComponentManager$3.register(AbstractComponentManager.java:890) ~[?:?] at org.apache.felix.scr.impl.manager.RegistrationManager.changeRegistration(RegistrationManager.java:132) ~[?:?] at org.apache.felix.scr.impl.manager.AbstractComponentManager.registerService(AbstractComponentManager.java:957) ~[?:?] at org.apache.felix.scr.impl.manager.AbstractComponentManager.activateInternal(AbstractComponentManager.java:741) ~[?:?] at org.apache.felix.scr.impl.manager.AbstractComponentManager.enableInternal(AbstractComponentManager.java:675) ~[?:?] at org.apache.felix.scr.impl.manager.AbstractComponentManager.enable(AbstractComponentManager.java:430) ~[?:?] at org.apache.felix.scr.impl.manager.ConfigurableComponentHolder.enableComponents(ConfigurableComponentHolder.java:657) ~[?:?] at org.apache.felix.scr.impl.BundleComponentActivator.initialEnable(BundleComponentActivator.java:341) ~[?:?] at org.apache.felix.scr.impl.Activator.loadComponents(Activator.java:387) ~[?:?] at org.apache.felix.scr.impl.Activator.access$200(Activator.java:52) ~[?:?] at org.apache.felix.scr.impl.Activator$ScrExtension.start(Activator.java:262) ~[?:?] at org.apache.felix.scr.impl.AbstractExtender.createExtension(AbstractExtender.java:196) ~[?:?] at org.apache.felix.scr.impl.AbstractExtender.modifiedBundle(AbstractExtender.java:169) ~[?:?] at org.apache.felix.scr.impl.AbstractExtender.modifiedBundle(AbstractExtender.java:49) ~[?:?] at org.osgi.util.tracker.BundleTracker$Tracked.customizerModified(BundleTracker.java:482) ~[?:?] at org.osgi.util.tracker.BundleTracker$Tracked.customizerModified(BundleTracker.java:415) ~[?:?] at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:232) ~[?:?] at org.osgi.util.tracker.BundleTracker$Tracked.bundleChanged(BundleTracker.java:444) ~[?:?] at org.apache.felix.framework.EventDispatcher.invokeBundleListenerCallback(EventDispatcher.java:915) ~[?:?] at org.apache.felix.framework.EventDispatcher.fireEventImmediately(EventDispatcher.java:834) ~[?:?] at org.apache.felix.framework.EventDispatcher.fireBundleEvent(EventDispatcher.java:516) ~[?:?] at org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:4579) ~[?:?] at org.apache.felix.framework.Felix.startBundle(Felix.java:2174) ~[?:?] at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:998) ~[?:?] at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:984) ~[?:?] at org.apache.karaf.features.internal.service.FeaturesServiceImpl.startBundle(FeaturesServiceImpl.java:1361) ~[?:?] at org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:894) ~[?:?] at org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1248) ~[?:?] at org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$1(FeaturesServiceImpl.java:1147) ~[?:?] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?] at java.lang.Thread.run(Thread.java:748) [?:?] Caused by: java.lang.IllegalStateException: InjectionManagerFactory not found. at org.glassfish.jersey.internal.inject.Injections.lambda$lookupInjectionManagerFactory$0(Injections.java:98) ~[?:?] at java.util.Optional.orElseThrow(Optional.java:290) ~[?:?] at org.glassfish.jersey.internal.inject.Injections.lookupInjectionManagerFactory(Injections.java:98) ~[?:?] at org.glassfish.jersey.internal.inject.Injections.createInjectionManager(Injections.java:93) ~[?:?] at org.glassfish.jersey.server.ApplicationHandler.(ApplicationHandler.java:282) ~[?:?] at org.glassfish.jersey.servlet.WebComponent.(WebComponent.java:335) ~[?:?] at org.glassfish.jersey.servlet.ServletContainer.init(ServletContainer.java:178) ~[?:?] at no.priv.bang.authservice.web.security.AuthserviceServlet.init(AuthserviceServlet.java:69) ~[?:?] at org.glassfish.jersey.servlet.ServletContainer.init(ServletContainer.java:370) ~[?:?] at javax.servlet.GenericServlet.init(GenericServlet.java:244) ~[?:?] at org.eclipse.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:643) ~[?:?] ... 62 more 2019-03-09T12:33:14,460 | INFO | features-1-thread-1 | FeaturesServiceImpl | 10 - org.apache.karaf.features.core - 4.1.7 | org.glassfish.hk2.locator/2.5.0.b42 2019-03-09T12:33:14,460 | INFO | features-1-thread-1 | FeaturesServiceImpl | 10 - org.apache.karaf.features.core - 4.1.7 | org.glassfish.jersey.inject.jersey-hk2/2.27.0 2019-03-09T12:33:14,461 | INFO | features-1-thread-1 | FeaturesServiceImpl | 10 - org.apache.karaf.features.core - 4.1.7 | org.glassfish.hk2.utils/2.5.0.b42 2019-03-09T12:33:14,461 | INFO | features-1-thread-1 | FeaturesServiceImpl | 10 - org.apache.karaf.features.core - 4.1.7 | org.glassfish.hk2.api/2.5.0.b42 2019-03-09T12:33:14,462 | INFO | features-1-thread-1 | FeaturesServiceImpl | 10 - org.apache.karaf.features.core - 4.1.7 | javax.ws.rs-api/2.1.0 2019-03-09T12:33:14,462 | INFO | features-1-thread-1 | FeaturesServiceImpl | 10 - org.apache.karaf.features.core - 4.1.7 | org.glassfish.jersey.core.jersey-common/2.27.0 2019-03-09T12:33:14,462 | INFO | features-1-thread-1 | FeaturesServiceImpl | 10 - org.apache.karaf.features.core - 4.1.7 | Done. </code> Run the command <code> bundle:list </code> and look for bundles with inject in their name. The only bundle that should be there, is jersey-inject-hk2: <code> 125 │ Active │ 80 │ 2.28.0 │ jersey-inject-hk2 </code> The way to eliminate undesirable javax.inject runtime dependencies is to look at the transitive maven dependencies with "mvn dependency:tree" and then exclude the transitive dependencies from the depdencies that pull them in.
19.8.2019 19:54Comment on Use Jersey to provide REST APIs from karaf applications by steinarbangKaraf 4.2.6 has been packaged and deployed to the repository. I have tested that the packaged karaf runs with both openjdk-8 and openjdk-11. Note that even though the package can be upgraded from 4.1.x with "apt-get dist-upgrade", the old /etc/karaf/host.key won't work, and need to be removed and karaf restarted before ssh can be used.
8.7.2019 15:46Comment on Installing apache karaf on debian by steinarbangHi, Why are you using version 1.0.7-SNAPSHOT instead of 1.0.6 as in the example? I tried building https://github.com/sbang/ansmtpserver and it built after I added a google guava dependcy to the config of maven-windows-service-installer-plugin
11.12.2018 18:56Comment on Making a Java windows service in 10 minutes by steinarbangThanks for this. But I have one problem, where is the parent pom? Could not find artifact com.alexkasko.installer:windows-service-installer-parent:pom:1.0.7-SNAPSHOT
11.12.2018 12:26Comment on Making a Java windows service in 10 minutes by CryptoScalpelKaraf 4.1.7 has been packaged and deployed to the repository. This will probably be the last 4.1.x version I'll package. I plan to package a 4.2.x version as the next version of the debian package.
1.12.2018 20:32Comment on Installing apache karaf on debian by steinarbang[…] Install apache karaf and start it according to the karaf quick start guide (alternatively, see Develop OSGi applications using karaf) […]
3.8.2018 20:46Comment on Develop OSGi applications using karaf by Use Jersey to provide REST APIs from karaf applications | Steinar Bangs bloggEdit: creating a REST API using jersey has been made simpler, see Simplified REST APIs from karaf using Jersey for details. The sample application https://github.com/steinarb/jersey-demo demonstrates how to use Jersey to provide a REST API from a Declarative Services (DS) component registering with the Pax Web Whiteboard Extender in apache karaf. The way Jersey works is that it … Continue reading Use Jersey to provide REST APIs from karaf applications
3.8.2018 20:46Use Jersey to provide REST APIs from karaf applications[…] Install apache karaf and start it according to the karaf quick start guide (alternatively, see Develop OSGi applications using karaf) […]
26.6.2018 20:08Comment on Develop OSGi applications using karaf by Deliver react.js from apache karaf | Steinar Bangs bloggEdit: delivering react.js has been made simpler, see Simplified delivery of react.js from apache karaf for details. A small barebones demo application/testbed, delivering a single-page web application from apache karaf, can be found at https://github.com/steinarb/frontend-karaf-demo The JavaScript framework used to write the application is react.js The frontend application is webpack‘d into a single bundle.js file. The … Continue reading Deliver react.js from apache karaf
26.6.2018 20:08Deliver react.js from apache karaf[…] faire une copie des données de la partition avant le reboot il existe des scripts sur le web : 1, 2, […]
12.4.2018 06:01Comment on Logging to persistent tmpfs on Raspbian “jessie” by Redémarrer un RaspberryPi quand RAMDisk plein[…] use aptly to deliver my unofficial debian packages both to myself and others that might be […]
17.2.2018 11:50Comment on Installing apache karaf on debian by Faking a debian repository for package development | Steinar Bangs blogg[…] I use aptly to deliver my unofficial debian packages both to myself and others that might be interested. […]
17.2.2018 11:50Comment on Setting up a debian package archive with aptly by Faking a debian repository for package development | Steinar Bangs bloggI use aptly to deliver my unofficial debian packages both to myself and others that might be interested. However I’ve found that using aptly to do package development is a bad idea, because you can’t (by design, probably) overwrite packages in an aptly archive. You can only create new versions. For some installation tests it’s … Continue reading Faking a debian repository for package development
17.2.2018 11:49Faking a debian repository for package developmentApache Karaf is a good platform for deploying OSGi based applications. Karaf is also a good platform for testing and debugging these applications. This article describes how to test and debug OSGi bundles and OSGi applications with karaf and eclipse. The basic flow of development, is: Build the application with maven Start karaf as your … Continue reading Develop OSGi applications using karaf
10.2.2018 15:02Develop OSGi applications using karaf<em>Note! Because the home directory of the karaf user has been changed to <a href="https://lintian.debian.org/tags/maintainer-script-should-not-use-adduser-system-without-home.html" rel="nofollow">satisfy lintian</a> it is recommended to purge karaf and reinstall, if you're currently on karaf 4.1.4-8~9.30.</em> <p>To purge, do the following as root: [code]apt-get purge karaf mv /home/karaf/.m2 /var/lib/karaf/ mv /home/karaf/.karaf /var/lib/karaf/ apt-get update apt-get install karaf [/code]
27.1.2018 11:46Comment on Installing apache karaf on debian by steinarbang[…] Until the RFP (Request For Packaging) bug for karaf in the debian bug tracker is resolved, here is an APT archive with a karaf package for debian (architecture “all”). The package is created using native debian packaging tools, and built from a source tarball and the APT archive itself is created, using aptly. […]
24.1.2018 16:33Comment on Setting up a debian package archive with aptly by Installing apache karaf on debian | Steinar Bangs blogg[…] on debian without building it yourself, the package installed is not the one described here, but the new and improved package built from source with native debian packaging tools, that can be found […]
23.1.2018 22:15Comment on Packaging karaf with native debian packaging tools by Installing apache karaf on debian stretch | Steinar Bangs blogg[…] It is now possible to install karaf on debian without building it yourself, the package installed is not the one described here, but the new and improved package built from […]
23.1.2018 22:15Comment on Installing apache karaf on debian by Installing apache karaf on debian stretch | Steinar Bangs blogg[…] Until the RFP (Request For Packaging) bug for karaf in the debian bug tracker is resolved, here is an APT archive with a karaf package for debian (architecture “all”). The package is created using native debian packaging tools, and built from a source tarball. […]
23.1.2018 22:09Comment on Packaging karaf with native debian packaging tools by Installing apache karaf on debian | Steinar Bangs blogg