I have his WARN

/edge/processor/AdapterFilterMethodReader.java:19: error: package edge.marshallable does not exist
    private edge.marshallable.Tick writearg0;


 WARN  - Failed to compile generated method reader - falling back to proxy method reader. Please report this failure as support for proxy method readers will be dropped in x.25.

Java Code

    private MethodReader methodReader;
    @Override
    public void configure() {
        // queue input
        methodReader = tailer.methodReader(tickWriter);
    }

where tickWriter is instance of /edge/processor/AdapterFilter, so I do understand that class AdapterFilterMethodReader is generated by Chronicle but compilation fails as edge package is not present

Chronicle JARs as described in here: #spring-boot-and-dynamic-compilation-in-chronicle-wire are extracted to TEMP dir but still

I have that only while running FAT JAR from CLI. It is not present when I run from inside IntelliJ. Was trying different settings but nothing seems to help..

How to handle / workaround that? How to force Chronicle to generate and compile that class beforehand during JAR construction?

I have his WARN

/edge/processor/AdapterFilterMethodReader.java:19: error: package edge.marshallable does not exist
    private edge.marshallable.Tick writearg0;


 WARN  - Failed to compile generated method reader - falling back to proxy method reader. Please report this failure as support for proxy method readers will be dropped in x.25.

Java Code

    private MethodReader methodReader;
    @Override
    public void configure() {
        // queue input
        methodReader = tailer.methodReader(tickWriter);
    }

where tickWriter is instance of /edge/processor/AdapterFilter, so I do understand that class AdapterFilterMethodReader is generated by Chronicle but compilation fails as edge package is not present

Chronicle JARs as described in here: https://github/OpenHFT/Chronicle-Wire?tab=readme-ov-file#spring-boot-and-dynamic-compilation-in-chronicle-wire are extracted to TEMP dir but still

I have that only while running FAT JAR from CLI. It is not present when I run from inside IntelliJ. Was trying different settings but nothing seems to help..

How to handle / workaround that? How to force Chronicle to generate and compile that class beforehand during JAR construction?

• chronicle

1 Answer 1

You can see other generated code if you use -Ddump.code on the command line.
You can also run the program in debug mode, and it should add the generated code to the target/generated test-sources. Either way, you can copy that code into your project, and if the class already exists, it uses that instead of generating it.