Xavier Dury

You may be right but this kind of API seems to be really at odd with the rest of JPA where most of the mapping is done in a declarative...

Shouldn't a `getVersion(entity)` method be added to the `PersistenceUnitUtil` class where there's already a `getIdentifier(entity)` method? In the meantime, `emf.getMetamodel().entity(entityType).getVersion().getJavaMember()` could be used.

Alternatively, a `ParamConverterProvider` facade (which would combine all registered `ParamConverterProvider`s) could be injected with `@Context` or `@Inject` to be used inside the resource. @Context private ParamConverterProvider paramConverterProvider;

This begs another question: should JAX-RS implementations return built-in `ParamConverterProvider`s for basic types? For example, I was expecting `ResteasyProviderFactory.getInstance().getParamConverter(...)` to give me basic converters for `Integer`, `UUID` and other simple...

Instead of having special rules for security roles, could we have a more general dynamic/runtime disambiguation mechanism that could be used when more than one resource match a request?

I would really like `MessageBodyReader` and `MessageBodyWriter` to be redesigned like this: public interface MessageBodyContext { Class getType(); Type getGenericType(); Annotation[] getAnnotations(); MediaType getMediaType(); MultivaluedMap getHttpHeaders(); Object getProperty(String name); Collection...

Enlarging the number of injectable items would be nice. Do you think it would also be possible to inject `Properties` and `Client` into the MBR/MBW? When my MBR/MBW need some...

@chkal If Jakarta EE specs are going to change their namespace/package, that will break backwards compatibility anyway. So, isn't it the perfect (and only) opportunity to fix some methods signatures...

Could you please foresee in the spec all the extension/configuration points needed by a standalone client (not deployed in a EE container) to use CDI-SE?

Are you sure the reference to the JIRA issue is correct? The title says: "_Does slf4j 1.6.3 support for Java 11? If not, any timeline or recommendation?_"