Ladislav Thon
Ladislav Thon
No, that's a completely different problem. Here, we're making it possible for a bean to become "inactive", throwing an exception when someone tries to create an instance anyway.
Get rid of it, yes please! :-)
I guess that makes sense, at least by default.
I'm thinking perhaps just 2 hard-coded profiles would be enough: - `SPECIFICATION`, which follows the JLS, and - `ERGONOMIC`, which is roughly what Gizmo 1 did (types and methods are...
I think the API is not terribly friendly to `final` fields by default. But fair, we can have an open-ended set of profiles.
I guess it should be enough to publicly expose `withoutFlags()` (or an equivalent). I wouldn't want fields to be `final` by default just because it's so easy to define a...
Yeah, I wonder as well. I don't see a good way, to be honest. Do you?
Hmm, I guess something like this might work? `FaultTolerance.java`: ```java /** * Creates a copy of this {@link FaultTolerance} object containing the same fault tolerance strategies, * but guarding an...
> This looks good to me, maybe there should be a different name than `copy()`. If you have a suggestion, I'm all ears. > I was wondering if we can...
This looks like an oversight to me.