Maksim Myshkin

Hi. What purpose of interDocumentCrossReferencesPrefix parameter? I found code that causes the issue (file DefinitionDocumentResolverFromOperation) but I don't understand hot to fix it right. If it something like base path...

Hi. I think separatedDefinitionsEnabled is false by default because in most cases you will generate single file (pdf or html) from markdown/asciidoc sources. In this case you need that references...

Ok. I will try when I will have a time. Looks like an easy fix.

With spring-kafka 2.8+ it can be implemented simply as: ```kotlin class TracingRecordInterceptor( private val kafkaTracing: KafkaTracing, private val tracer: Tracer, ) : ConsumerAwareRecordInterceptor { private var span: ThreadLocal = ThreadLocal()...

No, not tried it yet. For old spring-kafka versions we additionally set errorHandler in @KafkaListener annotations. This kind of error handlers are executing within tracing scope. However this solution is...

Also noticed that any exception not inherited from ResponseStatusException, annotated with @ResponseStatus or handled with @ExceptionHandler explicitly returning in old (not problem detail) format.

As workaround (for Spring) I just quoted value for property `spring.liquibase.default-schema="${application.datasource.schema}"` and left unqouted for `spring.liquibase.liquibase-schema=${application.datasource.schema}`. As raw liquibase properties I guess it be default-schema-name and liquibase-schema-name respectively.

Same here. How to solve this?

Maybe it will help someone. I have some two wsdl files for external system. One of them includes the other and it (that have include statement) don't have any schema...