René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"bug: document_symbol only respecting spring-boot client","articleBody":"### Did you check docs and existing issues?\n\n- [x] I have read all the plugin docs\n- [x] I have searched the existing issues\n- [x] I have searched the existing issues of plugins related to this issue\n\n### Neovim version (nvim -v)\n\n0.11.5\n\n### Operating system/version\n\nWin11/WSL Ubuntu 24.04\n\n### Describe the bug\n\nUsing current version of this plugin, it looks like document_symbol (via telescope, fzflua or just :lua vim.lsp.buf.document_symbol()) just returns values for the spring-boot client. For a minimal setup I've used the devcontainer init.lua available in this repo.\n\nAll symbols returned are just spring-boot annotations\n\nLazy (should be nvim-java 4.0.1?)\n\n ● nvim-java 21.46ms  start\n        dir    /home/soenke/.local/share/nvim/lazy/nvim-java\n        url    https://github.com/nvim-java/nvim-java\n        branch main\n        commit 389ef7c\n        readme README.md\n        help   |nvim-java.txt|\n\n- jdk 21\n- jdtls 1.54.0\n\nWhen setting lsp loglevel to debug, this is the whole output i'm getting:\n\n```\n[DEBUG][2025-12-08 23:25:36] ...m/lsp/client.lua:674    \"LSP[spring-boot]\"      \"client.request\"        1       \"textDocument/documentSymbol\"   { textDocument = { uri = \"\u003c\u003e.java\" } } \u003cfunction 1\u003e    1\n[DEBUG][2025-12-08 23:25:36] .../vim/lsp/rpc.lua:277    \"rpc.send\"      { id = 15, jsonrpc = \"2.0\", method = \"textDocument/documentSymbol\", params = { textDocument = { uri = \"\u003c\u003e.java\" } } }\n[DEBUG][2025-12-08 23:25:36] .../vim/lsp/rpc.lua:391    \"rpc.receive\"   { id = 15, jsonrpc = \"2.0\", result = { { kind = 11, location = { range = { [\"end\"] = { character = 15, line = 21 }, start = { character = 0, line = 21 } }, uri = \"\u003c\u003e.java\" }, name = \"@+ '\u003c\u003e' (@RestController \u003c: @Controller, @Component) \u003c\u003eController\" }, { kind = 11, location = { range = { [\"end\"] = { character = 98, line = 37 }, start = { character = 1, line = 36 } }, uri = \"\u003c\u003e.java\" }, name = \"@/** -- POST - Accept: application/\u003c\u003e - Content-Type: application/\u003c\u003e\" }, { kind = 11, location = { range = { [\"end\"] = { character = 42, line = 38 }, start = { character = 30, line = 38 } }, uri = \"\u003c\u003e.java\" }, name = \"@RequestBody\" }, { kind = 11, location = { range = { [\"end\"] = { character = 87, line = 59 }, start = { character = 1, line = 59 } }, uri = \"\u003c\u003e.java\" }, name = \"@/**/{request:.+} -- GET - Content-Type: application/\u003c\u003e\" }, { kind = 11, location = { range = { [\"end\"] = { character = 53, line = 60 }, start = { character = 29, line = 60 } }, uri = \"\u003c\u003er.java\" }, name = '@PathVariable(\"request\")' } } }\n```\n\n\n### Steps To Reproduce\n\n1. use devcontainer config, or add nvim-java as plugin to kickstart nvim\n2. open spring boot object (e.g. petclinic)\n3. open a controller\n4. run `:lua vim.lsp.buf.document_symbol()` (or telescope/fzflua equivalent)\n\n### Expected Behavior\n\nI'd expect seeing symbols returned by jdtls as well, instead of only spring boot annotations.\nI looked for similar issues, and one of them suggested adding more documentSymbol types to jdtls. however, when using jdtls on it's own it returned the expected symbols just fine\n\n\nI am not that familiar with nvim plugins, but if anyone has an idea where the problem lies or what needs to be done, I'd gladly try to work on a PR myself","author":{"url":"https://github.com/soenkekrusche","@type":"Person","name":"soenkekrusche"},"datePublished":"2025-12-08T22:34:52.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":8},"url":"https://github.com/447/nvim-java/issues/447"}