Weaver | Dependency Injection framework for Swift | Dependency Injection library

I am not a Spring user, but when answering AspectJ LTW questions here I often noticed a certain discrepancy between the Spring documentation mentioning the need for the Spring Instrument Java agent only and the real situation in which there are ways to configure Spring like that, but it is tricky. The simplest approach by far is to also add the AspectJ Weaver agent to the command line, i.e. to use something like (on a single line, of course)

A simple change in your for iteration would help:

You can do it with the $event parameter. Make sure to compare your values safely.

If your value is not in the right type or has spaces or unwanted chars, this c.state == val might not work.

You can use the trim function to compare your value safely: c.state.trim() == val.trim()

HTML

Firstly, you cannot replace a returned object from within the constructor execution(), because a constructor is not a normal method which could e.g. have a supertype or interface as return type. A constructor always returns exactly the object of the defined type, nothing else. This is not even an AspectJ limitation but a JVM limitation. With a byte code engineering library such as ASM you would have the same limitation.

So the best you can do in AspectJ is to replace the returned object in the constructor call(), but the object must also match the expected type. Unfortunately, OpenTelemetry returns a lambda instance which cannot be cast to the exact anonymous Callable subtype you have in your code. This means, there is nothing you can do here with that kind of code structure.

As a workaround, you can intercept calls to methods taking Callable instances, such as ExecutorService.submit(Callable). You just need to make sure to capture all relevant ones. For example:

A simple solution/workaround was to add aspectj-maven-plugin for compile-time weaving(in this case aop.xml file is not needed anymore)

and package projects with its dependencies in to executable jar using maven-assembly-plugin (there are other ways also to package executable jars with libs/dependencies)

pom.xml

My first guess, not having seen your real project, is that you should move the weaver options out of the aspect declaration section like this:

Your program is throwing an std::bad_alloc exception at some point and, since your are not handling this exception, it halts. This is due to some flaw on memory management.

Check your bubble-sort algorithm. Specifically, the for loop:

You are using AspectJ Maven Plugin, i.e. you are going to use compile-time weaving. Therefore, you do not need aop.xml because that one is used for load-time weaving. So you can delete it.

During compilation you should get a compile error:

Your "data" is an object of JSON, but not an array.