arosien commented on issue #66: URL: https://github.com/apache/daffodil-vscode/issues/66#issuecomment-1018658277
> You actually don't need to have the jar in the class path if you have something like this it should also work > > `"daffodilDebugClasspath": "/FULL/PATH/TO/dfdl-ethernet/src/main/resources:/FULL/PATH/TO/dfdl-pcap/src/main/resources"` Ah, that's cool, one can have both a directory with files and a jar file in that classpath 👍 . However, this only makes it possible for the Daffodil running in the debugger process to load the imported schema, not for VS Code to "follow links" from the main schema to the imported schema, like via Cmd-click. We'd have to teach VS Code how to navigate those references explicitly, since a reference like `/com/blah/foo.schema` might actually be on some directory path `/somewhere/else/com/blah/foo.schema`. It may be possible to use the DAP protocol's [`LoadedSource`](https://microsoft.github.io/debug-adapter-protocol/specification#Events_LoadedSource) functionality to have the Daffodil debugger be the source of truth (content) for imported schema that aren't necessarily directly available as files (and may be in jar files, etc.), but this still doesn't solve the VS Code navigation issue. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
