auditable | version tracking library for Rails | Application Framework library

So I am not totally sure what you are after however this may work

I was able to fix the issue by clearing the entity manager right before the findAllById call. This seems to break the reference to the previously fetched objects allowing me to add new instances to every element in the loop.

Though am not facing any other issues in the code or object retrieval/persist due to this, i am not 100% sure that this is the correct solution.

For now my issue is solved.

Just add this bean convert the ObjectId to String.

Dependency

I found a workaround. If you remove the import and instead put the fully qualified class name in the config item, it works fine. I don't really like this because I don't understand why it works when the import doesn't.

A quick solution is to use adaptive, which sounds a lot like what you are interested in and has very cool visualisation of progress. (update: oops, just noticed that there is a contributor to adaptive with the same name as yours, so there is a good chance you know about this package.)

Some suggestions on your code:

• right now the computation is serial: the while loop blocks until each task is computed (due to .result). A somewhat better way might be to use .map to submit multiple values for evaluation.

Should State Changes generated at the read side create more events?

"State changes generated at the read side" is a very... odd... spelling to use in the CQRS pattern.

In the usual arrangement, information from "the outside" is delivered to the write model, and that's where we perform our computation to decide what the new "authoritative" state of the entity is.

The read model is a non-authoritative copy of state; accurate as of some point in the past, but not necessary up to date. Think "cache".

State changes generated by the cache is weird, because the cache is reflection of the write model.

Now, what will sometimes happen, is that we have two models, and the second model will be interested in changes that happen to the first model.

In that case, we use some form of plumbing to connect the outputs of one model to the inputs of the other.

So we have Alice doing her work, and one of the reports (read model) produced by Alice's work becomes one of Bob's inputs as he does his work.

Now, you might -- as a matter of optimization -- broadcast "events" when the caches update, so that subscribers can know that there is information available for processing. But you probably shouldn't be framing these as "state changes" in the sense of being changes to the entities in your domain model. Those changes have already happened, under the governance of the write model.

[UPDATED]

Based on the controller code you showed, it didn't work because your code is being called using Builder style, and the package only works when it is called using Eloquent style.

Documentation link

So, maybe you need to change your code to:

Fix, I don't need to implement Auditable since I already use @EntityListeners(AuditingEntityListener.class).

If you would call the pre-destroy method manually like appContext.getBean(Application.class).destroy(), the aspect would be triggered. But in the part of the lifecycle where the application is being destroyed, no aspects seem to be applied anymore.

According to the @PreDestroy javadoc, the annotated target method may be private and even final, i.e. two characteristics contradicting proxy-based Spring AOP usage. I am not a Spring or Java EE user at all and I might be wrong, but to me it looks as though this is not supposed to be working the way you expect it to. Spring experts around here like M. Deinum or R.G might be able to shed more light onto this issue.