Suche
Kategorien
Über…
Das ist das Blog von Sven Hasselbach über Themen aus der Entwicklung und alles, was ihm sonst so durch den Kopf geht.
Seit 2003 als freiberuflicher Entwickler deutschlandweit im Einsatz, mit dem Schwerpunkten Lotus Notes & XPages, Spring, Java & OSGi
IBM ICS Champion 2013
Um Kontakt mit mir aufzunehmen, einfach eine eMail an contact<at>hasselba.ch schicken oder mich bei XING finden:
Projektanfragen sind immer willkommen!-
Neueste Beiträge
Neueste Kommentare
- Chris Eggenberger bei xsp.application.context.proxy
- Chris Eggenberger bei xsp.application.context.proxy
- Displaying Markdown in an XPage using the showdown.js library - wp2020.focul.net bei XPages: Inject CSJS code at page top
Archive
Meta
Archiv der Kategorie: Web
Migrating OSGi Plugins to standalone applications
I have created an example project for migrating an OSGI-based Spring Boot application into a standalone application (in the „Maven“ branch): https://github.com/hasselbach/domino-springboot/blob/maven/domino-springboot.plugin The application runs in the JVM of the Notes Client, only a user id is required, not a … Weiterlesen
Dropping Domino’s HTTP task (3): WebSSO Integration (Part 1)
To integrate the new HTTP stack into the existing environment, we can use LTPA tokens. These tokens are cookies which store the authentication information and allow to share them betweeen different participating Domino servers. A users must log on only … Weiterlesen
Veröffentlicht unter Java, Server, Web
Verschlagwortet mit Java, Server, Spring Boot, Web
Schreib einen Kommentar
Dropping Domino’s HTTP task (2): Running in User Context
To use the approach as an alternative to Domino’s HTTP task, we need support for the different user contexts, because using NotesFactory.createSession() just creates a session for the current Notes ID used. This goal can be achived by using the … Weiterlesen
Veröffentlicht unter Java, Server, Web
Verschlagwortet mit Java, Server, Spring Boot, Web
5 Kommentare
Dropping Domino’s HTTP task
Instead of waiting for updates of the Domino HTTP task any longer I was thinking about how to use modern HTTP technologies on top of Domino. But instead of implementing it in the Domino stack, I think I found a … Weiterlesen
HCL, Domino & node.js
I am very happy to hear that HCL invests in Domino and improves the existing technology stack. But as a German, I have to be sceptical (it’s in our genes), because I can not see any advantage in the integration … Weiterlesen
Veröffentlicht unter ExtLib, Java Script, REST, Server, Spring, XPages
Verschlagwortet mit Domino, Java 8, REST, Spring Boot
4 Kommentare
Domino & Spring Boot: How does it work
The example Spring Boot Plugin I have published two days ago is a full working example to run Spring Boot applications directly in the Domino HTTP task. It is designed as an OSGi plugin and runs inside the servlet container, … Weiterlesen
Veröffentlicht unter Java, OSGi, Server, Spring, Web
Verschlagwortet mit Domino, Spring Boot, Web
3 Kommentare
Domino & Spring Boot: An example project
I have uploaded an example for running Spring Boot applications on top of Domino. You can find it here: https://github.com/hasselbach/domino-springboot This solution is running for years in productive environments. Hopefully I will find some time to explain how it works.
Veröffentlicht unter Java, OSGi, REST, Spring, Web
Verschlagwortet mit Domino, Java, Spring Boot, Web
4 Kommentare
Domino & Spring Boot: ScheduledTasks
When developing Spring Boot applications running on Domino, there is a feature which runs out of the box and makes developers happy: ScheduledTasks. These are the equivalent for agents, but they are running directly in the HTTP task (which allows … Weiterlesen
Re: Domino REST performance analysis
I have created a Quick-n-Dirty performance test for Csaba’s „10K record test“: Loading time 200 ms overall, 60 ms TTFB. Do you want to know how this works? Feel free to come to SNoUG next week or to Rudi’s EntwicklerCamp and … Weiterlesen
Domino & REST: Debug your Plugin
When developing OSGi Plugins, you should have your own development server running on your local machine. Not only because of the faster deployment of changes (a new version of a plugin must always deployed with a HTTP restart), but because … Weiterlesen