How can I exclude EclipseStore from spring boot dev tools during live reload?

[LiveNathan]

I have created a demo project using EclipseStore and Vaadin. If I start the application with ./mvnw, then rebuild a module, live reload is triggered and I get this error:

org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'defaultStorageManager' defined in class path resource [org/eclipse/store/integrations/spring/boot/types/DefaultEclipseStoreConfiguration.class]: Failed to instantiate [org.eclipse.store.storage.embedded.types.EmbeddedStorageManager]: Factory method 'defaultStorageManager' threw exception with message: Active storage for org.eclipse.store.storage.types.Database$Default@70f01db4 "Eclipse Serializer@storage" already exists.

What's the best way to handle this? I assumed it was to exclude EclipseStore from live reload, but I tried spring.devtools.restart.exclude=**/EclipseStore/** in application.properties and it did not fix the problem.

Please let me know if the answer is already in the docs. I did not see it.

[LiveNathan]

Is it possible this has something to do with auto start?

[LiveNathan]

Turns out the issue was with spring data eclipse store

[JohannesRabauer]

The issue with the spring-dev-tools seems to be also a problem for eclipse store in general: https://docs.eclipsestore.io/manual/misc/integrations/spring-boot.html#_spring_dev_tools

[LiveNathan]

Yes! Thank you. I should have linked to that. I wish it would say exactly how to "exclude the EclipseStore classes from the classpath."

There's spring.devtools.restart.exclude, but that just excludes those files from triggering a restart, right?
I don't know how you exclude something from the classpath.

[LiveNathan]

@JohannesRabauer Would you be willing to teach me how to "exclude the EclipseStore classes from the classpath"?

Maybe you could even create a PR to help improve the documentation for everyone. :)

I see that the import for the storage manager, for example, is import org.eclipse.store.storage.embedded.types.EmbeddedStorageManager;. So in the application.properties file do I need to add spring.devtools.restart.exclude=org.eclipse.store

As I mentioned earlier, I'm confused if this is used to exclude classes that trigger a restart or the classes that are restarted.

[JohannesRabauer]

Hi @LiveNathan,
i'm curious: As far as i could tell this is a issue with eclipse store because it is difficult to handle the Reload-ClassLoader (https://docs.spring.io/spring-boot/reference/using/devtools.html#using.devtools.restart.restart-vs-reload). How did you fix the issue?

[LiveNathan]

Hey Johannes. This was a little while back. Unfortunately, I don't remember what happened. I don't have a very good memory. I haven't tried to use spring-data-eclipse-store since then. Now I just use the regular EclipseStore implementation and haven't had that particular problem again.

[JohannesRabauer]

Thanks @LiveNathan for your reply! Could you tell me what made you switch to regular EclipseStore? We are always eager to improve our Spring-Data-Implementation. Maybe your input can lead to improvements in the SDES ☺️

[LiveNathan]

Yeah, of course. Initially I was trying to get EclipseStore to work for the first time. I could never get anything to persist. I even downloaded the simple spring boot example and it didn't work. Turns out there was a bug. Anyway, I was get frustrated, then saw your video, tried it, and it worked immediately so I used it for that demo project. Later, for my next project I took the EclipseStore training, created an issue, and finally found out what I was doing wrong. I'm a beginner, but for now I like the idea of using objects directly, without translating back and forth between the domain and the repository because it seems like less work. I'm not sure if it's a better design pattern so I can see myself trying spring-data implementation again in the future, but for now I'm enjoying persisting and working the domain objects directly.

By the way, side topic, do you know anything about compiling to native image? I post a question here.

[JohannesRabauer]

Alright, thank you for that information! That sounds reasonable and is indeed the core of both libraries! Using EclipseStore for pure performance or spring-data-eclipse-store for it's simplicity.

I have tried a native image only one time and came to the same conclusion as @hg-ms. It is in theory usable with EclipseStore, but not at all in an actually used project for clients or for production.
Maybe the EclipseStore team will come up with an maven-plugin or something that generates the config @hg-ms mentioned. But until then i would not recommend using native images with EclipseStore.