Replies: 4 comments 2 replies
-
Indeed, such an contribution allowing to pass some specific debugging configuration to LemMinX would be welcome. |
Beta Was this translation helpful? Give feedback.
-
It looks like the lemminx side has an opening to parameterize it with logging-related settings. At first it superficially seems like the WWD XML extension point's Browsing the code, it's not clear to me that the two are really connected in this way, however. Since it would take some trial and error to set up all the XML/Java/JSON artifacts and content here, I'm going to stop there and see what anyone thinks about this. Referring back to the lemminx XMLLanguageServer class, I would've hoped we could at least have leveraged the default JRE JUL config. However, the lemminx server proceeds to unregister all handlers. If it weren't for this I'd have been happy for now to have the INFO and higher messages logged to ConsoleHandler, and have this output stream redirected back to the parent Eclipse IDE (using In the meantime, I'm realizing I can workaround this by adding |
Beta Was this translation helpful? Give feedback.
-
#1040 aims at allowing LemMinX server logs. |
Beta Was this translation helpful? Give feedback.
-
Added a PR to lemminx to use the |
Beta Was this translation helpful? Give feedback.
-
Hi, I'm trying to enable trace/logging for a lemminx extension running in XML LS launched from Eclipse 2022-09 using the wildwebdeveloper XML function. The lemminx XML LS is launched as a separate JVM process in my env. The extension is now coded with java.util.logging.
I see there is a "hook" to add a debug port here but I don't see something comparable for say a JUL properties file property.
Also I know we can use the preference of Language Servers -> Logs to trace the JSON-RPC calls.. but I'm trying to trace the "internals" not just the JSON-RPC payloads.
Would this be new function needed? Or is there another way to accomplish this? Thank you!
Beta Was this translation helpful? Give feedback.
All reactions