Risto Seene

In regards to getting information about the TSL state after the refresh, in the current Digidoc4j (version 4.3.0), the summary of the TSL validation can be queried via `configuration.getTSL().getSummary()`. An...

What kind of parameters are you configuring via _Configuration_ to enable proxying? What type of authentication is your proxy using? Are you using the same proxy for proxying both HTTP...

> We actually found an inconvenient way to disable proxy for TSL only using the internal registry. By "internal registry", do you mean the _ConfigurationRegistry_ instance inside the _org.digidoc4j.Configuration_ class?...

Hello! What exactly is causing out of memory errors? Signature files themselves are already loaded fully into memory in `AsicContainerParser` prior to calling the `parseSignatures` method. Only thing that comes...

The _ExecutorService_ configurable via _Configuration#setThreadExecutor(ExecutorService)_ is meant for signature validation only. It wouldn't be advisable to use the same _ExecutorService_ for both signature validation and TSL loading, because TSL loading...

> As a side note, calling tsl.refresh() blocks the calling thread, even if the actual refresh happens in another thread. The blocking happens in the underlying DSS library level, so...