Language Server for Apache Camel: Java/Eclipse plugin developer perspective
summary
A Java language server for Apache Camel uses LSP4J and implements completion, validation and hover for the Camel URI in both XML and Java DSLs, deployed to Eclipse, VS Code and Eclipse Che after a few weeks of work and now seeing a few hundred installs. Challenges include writing small IDE-specific clients and marketplace packaging, so the recommended approach is start with single-file support, use textDocumentDidChange (full) for simplicity and provide a VS Code extension as the reference client.
AI-written summary · about
chapters (11)
- 0:00Intro
- 0:39What to expect?
- 4:37CONTEXT
- 7:14How to write the server? Let's search for examples!
- 11:36Now test with IDE!
- 13:06With which IDE to start?
- 18:11Technical advice - IDE integration Eclipse Desktop (1/2)
- 21:02Technical advice - IDE integration VS Code (1/2)
- 23:51Eclipse Che 6 - OpenShift.io
- 26:58In a nutshell
- 30:00What's next?
related talks
44mDeveloping a Language Plugin: LSP versus the Joy of Learning
36mExperiences Building a Language Server Protocol Plugin
33mDeveloping Java applications using Visual Studio Code
22mEclipse Che and the Language Server Protocol
30mImproving the development experience with language servers
31mDeveloping Java Apps using Visual Studio Code
44mThe Language Server Protocol Why The Hype
28mBuilding Tools for Jakarta EE and MicroProfile Developers