MyDslValidator instances between different injectos

[AhmedMahmoud98]

Hello,

In my Xtext project, I'm defining MyDslValidator class with some custom @check methods. MyDslValidator Class is binded at RuntimeModule as follows:

       @SingletonBinding(eager=true)
	public Class<? extends MyDslValidator> bindMyDslValidator() {
		return MyDslValidator.class;
	}

I've a problem, whatever injector is used. And although multiple instances of the MyDslValidator class are created per injector, always the first created instance is executed, which is something that I want to avoid, as somehow I want to keep some state and It's different for different injectors/runs.

I suspect that @SingletonBinding(eager=true) Annotation could be the problem, but removing it or setting eager to false prevents MyDslValidator from being executed at all. Could you please help to ensure that the MyDslValidator instance isn't cached somewhere, and the newly created instance is executed and not always the first one?

Thanks in advance

[cdietrich]

this is intentional. also how the validation registry deals with them.
can you explain your "keeping state" usecase.
maybe

• IResourceScopeCache
• and depending on usecase AbstractDeclarativeValidator.getContext()

are better options for caching

[cdietrich]

hmmm. as said you should do all these things somewhere else. for me i dont see more than one instance ever created in tests

[AhmedMahmoud98]

Is this behaviour of always executing first instance not avoidable by any means?

[cdietrich]

as said. i dont manage to get more than once instance, so yes
of course you always can override change anything.
but this would be up to you

[cdietrich]

but i really believe this is not needed in your usecase.

[AhmedMahmoud98]

Thanks for this discussion. I believe I got my answer and how I could step forward