Add a common shared contract for the sessions

[DavideD]

See quarkusio/quarkus#46091 (comment)

[gavinking]

@FroMage do you really need this. I'm not very keen on it.

[DavideD]

I'm not sure about the extra .find methods of the original request, but what's the problem with having the Query creation methods in a separate interface, similar if not equal to QueryProducer? Isn't ORM already doing something similar?

[FroMage]

@FroMage do you really need this. I'm not very keen on it.

I don't really need it, I've abstracted around it using inheritance and subclasses to deal with the two session types, but they're calling the same damn methods with the same name and signature. And ORM has SharedSessionContract where these live.

Looks to me like this is an improvement worth having, and is in line with the ORM sessions types.

Not absolutely necessary, but definitely easier to deal with mixed session types, for 5-6 methods.

[gavinking]

The reason I'm hesitant is that these things are inner types and it's already a PITA to navigate around inside the Mutiny and Stage outer interfaces.

I mean, it's not a strong objection.

Also:

1. we would have to find a name for this thing because SharedSessionContract is a mouthful, and
2. in your proposal you have given this thing a find() method, but StatelessSession does not have find().

Perhaps it's an analog of QueryProducer you're looking for.

[FroMage]

in your proposal you have given this thing a find() method, but StatelessSession does not have find().

Yeah, I suppose this one has different names, we can leave it out.

[FroMage]

I'll need a few more operations, hold on.

[gavinking]

Yeah, I suppose this one has different names

Well, not just different names; different semantics.

[FroMage]

potato, tomato 😅

[FroMage]

"get me this thing by id"

[gavinking]

"Get me a managed object" and "get me a detached object" are pretty different.

[FroMage]

I've heard you say that, and yet the query operations are the same to get one or the other type :)

[FroMage]

Two more methods needed:

	Filter enableFilter(String filterName);
	void disableFilter(String filterName);