Missing entries in jersey-server/module-info.java?

[theit]

I have a standalone server application using Jersey 4.0.0 as Jakarta REST implementation. The dependencies are similar to those I've described in #6041. Trying to call the login method on the server from a client also using Jersey results in the following exception logged in the server:

Dez. 09, 2025 11:01:00 AM org.glassfish.jersey.server.ServerRuntime$Responder process
WARNUNG: An exception mapping did not successfully produce and processed a response. Logging the exception propagated to the default exception mapper.
org.jboss.weld.exceptions.WeldException: WELD-001524: Unable to load proxy class for bean org.glassfish.jersey.inject.cdi.se.bean.ClassBean@5c906d08 with class class org.glassfish.jersey.server.internal.process.RequestProcessingContextReference
	at weld.core.impl@6.0.3.Final/org.jboss.weld.bean.proxy.ProxyFactory.getProxyClass(ProxyFactory.java:424)
	at weld.core.impl@6.0.3.Final/org.jboss.weld.bean.proxy.ProxyFactory.instantiateProxy(ProxyFactory.java:375)
	at weld.core.impl@6.0.3.Final/org.jboss.weld.bean.proxy.ProxyFactory.create(ProxyFactory.java:368)
	at weld.core.impl@6.0.3.Final/org.jboss.weld.bean.proxy.ClientProxyFactory.create(ClientProxyFactory.java:84)
	at weld.core.impl@6.0.3.Final/org.jboss.weld.bean.proxy.ClientProxyProvider.createClientProxy(ClientProxyProvider.java:207)
	at weld.core.impl@6.0.3.Final/org.jboss.weld.bean.proxy.ClientProxyProvider.createClientProxy(ClientProxyProvider.java:197)
	at weld.core.impl@6.0.3.Final/org.jboss.weld.bean.proxy.ClientProxyProvider$CreateClientProxy.apply(ClientProxyProvider.java:52)
	at weld.core.impl@6.0.3.Final/org.jboss.weld.bean.proxy.ClientProxyProvider$CreateClientProxy.apply(ClientProxyProvider.java:48)
	at weld.core.impl@6.0.3.Final/org.jboss.weld.util.cache.ReentrantMapBackedComputingCache.lambda$new$0(ReentrantMapBackedComputingCache.java:57)
	at weld.core.impl@6.0.3.Final/org.jboss.weld.util.LazyValueHolder$1.computeValue(LazyValueHolder.java:32)
	at weld.core.impl@6.0.3.Final/org.jboss.weld.util.LazyValueHolder.get(LazyValueHolder.java:46)
	at weld.core.impl@6.0.3.Final/org.jboss.weld.util.cache.ReentrantMapBackedComputingCache.getValue(ReentrantMapBackedComputingCache.java:74)
	at weld.core.impl@6.0.3.Final/org.jboss.weld.util.cache.ReentrantMapBackedComputingCache.getCastValue(ReentrantMapBackedComputingCache.java:80)
	at weld.core.impl@6.0.3.Final/org.jboss.weld.bean.proxy.ClientProxyProvider.getClientProxy(ClientProxyProvider.java:232)
	at weld.core.impl@6.0.3.Final/org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:720)
	at weld.core.impl@6.0.3.Final/org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:746)
	at weld.core.impl@6.0.3.Final/org.jboss.weld.util.ForwardingBeanManager.getReference(ForwardingBeanManager.java:65)
	at weld.core.impl@6.0.3.Final/org.jboss.weld.bean.builtin.BeanManagerProxy.getReference(BeanManagerProxy.java:89)
	at org.glassfish.jersey.inject.cdi2.se@4.0.0/org.glassfish.jersey.inject.cdi.se.CdiSeInjectionManager.getInstanceInternal(CdiSeInjectionManager.java:178)
	at org.glassfish.jersey.inject.cdi2.se@4.0.0/org.glassfish.jersey.inject.cdi.se.CdiSeInjectionManager.getInstance(CdiSeInjectionManager.java:161)
	at org.glassfish.jersey.core.server@4.0.0/org.glassfish.jersey.server.ApplicationHandler.lambda$initialize$4(ApplicationHandler.java:430)
	at org.glassfish.jersey.core.server@4.0.0/org.glassfish.jersey.server.internal.process.ReferencesInitializer.apply(ReferencesInitializer.java:57)
	at org.glassfish.jersey.core.server@4.0.0/org.glassfish.jersey.server.internal.process.ReferencesInitializer.apply(ReferencesInitializer.java:31)
	at org.glassfish.jersey.core.common@4.0.0/org.glassfish.jersey.process.internal.Stages$LinkedStage.apply(Stages.java:284)
	at org.glassfish.jersey.core.common@4.0.0/org.glassfish.jersey.process.internal.Stages.process(Stages.java:173)
	at org.glassfish.jersey.core.server@4.0.0/org.glassfish.jersey.server.ServerRuntime$1.run(ServerRuntime.java:266)
	at org.glassfish.jersey.core.common@4.0.0/org.glassfish.jersey.internal.Errors$1.call(Errors.java:248)
	at org.glassfish.jersey.core.common@4.0.0/org.glassfish.jersey.internal.Errors$1.call(Errors.java:244)
	at org.glassfish.jersey.core.common@4.0.0/org.glassfish.jersey.internal.Errors.process(Errors.java:292)
	at org.glassfish.jersey.core.common@4.0.0/org.glassfish.jersey.internal.Errors.process(Errors.java:274)
	at org.glassfish.jersey.core.common@4.0.0/org.glassfish.jersey.internal.Errors.process(Errors.java:244)
	at org.glassfish.jersey.core.common@4.0.0/org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:266)
	at org.glassfish.jersey.core.server@4.0.0/org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:253)
	at org.glassfish.jersey.core.server@4.0.0/org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:703)
	at org.glassfish.jersey.container.grizzly2.http@4.0.0/org.glassfish.jersey.grizzly2.httpserver.GrizzlyHttpContainer.service(GrizzlyHttpContainer.java:374)
	at org.glassfish.grizzly.http.server@4.0.2/org.glassfish.grizzly.http.server.HttpHandler$1.run(HttpHandler.java:190)
	at org.glassfish.grizzly@4.0.2/org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:535)
	at org.glassfish.grizzly@4.0.2/org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.run(AbstractThreadPool.java:515)
	at java.base/java.lang.Thread.run(Thread.java:1474)
Caused by: java.lang.IllegalAccessError: superinterface check failed: class org.glassfish.jersey.server.internal.process.RequestProcessingContextReference$Proxy$_$$_WeldClientProxy (in module org.glassfish.jersey.core.server) cannot access class org.jboss.weld.proxy.WeldClientProxy (in module weld.api) because module org.glassfish.jersey.core.server does not read module weld.api
	at java.base/java.lang.ClassLoader.defineClass0(Native Method)
	at java.base/java.lang.System$1.defineClass(System.java:2050)
	at java.base/java.lang.invoke.MethodHandles$Lookup$ClassDefiner.defineClass(MethodHandles.java:2354)
	at java.base/java.lang.invoke.MethodHandles$Lookup$ClassDefiner.defineClass(MethodHandles.java:2329)
	at java.base/java.lang.invoke.MethodHandles$Lookup.defineClass(MethodHandles.java:1753)
	at weld.core.impl@6.0.3.Final/org.jboss.weld.bean.proxy.util.WeldDefaultProxyServices.defineWithMethodLookup(WeldDefaultProxyServices.java:153)
	at weld.core.impl@6.0.3.Final/org.jboss.weld.bean.proxy.util.WeldDefaultProxyServices.defineClass(WeldDefaultProxyServices.java:62)
	at weld.core.impl@6.0.3.Final/org.jboss.weld.bean.proxy.ProxyFactory.toClass(ProxyFactory.java:975)
	at weld.core.impl@6.0.3.Final/org.jboss.weld.bean.proxy.ProxyFactory.createProxyClass(ProxyFactory.java:509)
	at weld.core.impl@6.0.3.Final/org.jboss.weld.bean.proxy.ProxyFactory.getProxyClass(ProxyFactory.java:416)
	... 38 more

With --add-reads org.glassfish.jersey.core.server=weld.api I see almost the same stacktrace, but with a slightly different cause:

(...)
Caused by: java.lang.IllegalAccessError: superinterface check failed: class org.glassfish.jersey.server.internal.process.RequestProcessingContextReference$Proxy$_$$_WeldClientProxy (in module org.glassfish.jersey.core.server) cannot access class org.jboss.weld.proxy.WeldClientProxy (in module weld.api) because module org.glassfish.jersey.core.server does not read module weld.api
	at java.base/java.lang.ClassLoader.defineClass0(Native Method)
	at java.base/java.lang.System$1.defineClass(System.java:2050)
	at java.base/java.lang.invoke.MethodHandles$Lookup$ClassDefiner.defineClass(MethodHandles.java:2354)
	at java.base/java.lang.invoke.MethodHandles$Lookup$ClassDefiner.defineClass(MethodHandles.java:2329)
	at java.base/java.lang.invoke.MethodHandles$Lookup.defineClass(MethodHandles.java:1753)
	at weld.core.impl@6.0.3.Final/org.jboss.weld.bean.proxy.util.WeldDefaultProxyServices.defineWithMethodLookup(WeldDefaultProxyServices.java:153)
	at weld.core.impl@6.0.3.Final/org.jboss.weld.bean.proxy.util.WeldDefaultProxyServices.defineClass(WeldDefaultProxyServices.java:62)
	at weld.core.impl@6.0.3.Final/org.jboss.weld.bean.proxy.ProxyFactory.toClass(ProxyFactory.java:975)
	at weld.core.impl@6.0.3.Final/org.jboss.weld.bean.proxy.ProxyFactory.createProxyClass(ProxyFactory.java:509)
	at weld.core.impl@6.0.3.Final/org.jboss.weld.bean.proxy.ProxyFactory.getProxyClass(ProxyFactory.java:416)
	... 38 more

To get rid of this exception I have to start the server application with --add-reads org.glassfish.jersey.core.server=weld.api,weld.core.impl

But:
Why is this necessary? As far as I can see jersey-server doesn't make use of Weld and its libraries, only jersey-cdi2-se.

[jansupol]

Can you provide a minimum reproducer?

[theit]

Hi,
sorry for the (very) long delay. I was quite busy with $JOB and then had some days off (and forgot to answer)...

First please excuse the above stack trace causes; they are similar. Here are the ones I have seen without additional --add-reads:

(...)
Caused by: java.lang.IllegalAccessError: superinterface check failed: class org.glassfish.jersey.server.internal.process.RequestProcessingContextReference$Proxy$_$$_WeldClientProxy (in module org.glassfish.jersey.core.server) cannot access class org.jboss.weld.interceptor.util.proxy.TargetInstanceProxy (in module weld.core.impl) because module org.glassfish.jersey.core.server does not read module weld.core.impl
	at java.base/java.lang.ClassLoader.defineClass0(Native Method)
	at java.base/java.lang.System$1.defineClass(System.java:2050)
	at java.base/java.lang.invoke.MethodHandles$Lookup$ClassDefiner.defineClass(MethodHandles.java:2354)
	at java.base/java.lang.invoke.MethodHandles$Lookup$ClassDefiner.defineClass(MethodHandles.java:2329)
	at java.base/java.lang.invoke.MethodHandles$Lookup.defineClass(MethodHandles.java:1753)
	at weld.core.impl@6.0.3.Final/org.jboss.weld.bean.proxy.util.WeldDefaultProxyServices.defineWithMethodLookup(WeldDefaultProxyServices.java:153)
	at weld.core.impl@6.0.3.Final/org.jboss.weld.bean.proxy.util.WeldDefaultProxyServices.defineClass(WeldDefaultProxyServices.java:62)
	at weld.core.impl@6.0.3.Final/org.jboss.weld.bean.proxy.ProxyFactory.toClass(ProxyFactory.java:975)
	at weld.core.impl@6.0.3.Final/org.jboss.weld.bean.proxy.ProxyFactory.createProxyClass(ProxyFactory.java:509)
	at weld.core.impl@6.0.3.Final/org.jboss.weld.bean.proxy.ProxyFactory.getProxyClass(ProxyFactory.java:416)
	... 37 more

With an additional --add-reads org.glassfish.jersey.core.server=weld.core.impl line the cause changes to:

(...)
Caused by: java.lang.IllegalAccessError: superinterface check failed: class org.glassfish.jersey.server.internal.process.RequestProcessingContextReference$Proxy$_$$_WeldClientProxy (in module org.glassfish.jersey.core.server) cannot access class org.jboss.weld.proxy.WeldClientProxy (in module weld.api) because module org.glassfish.jersey.core.server does not read module weld.api
	at java.base/java.lang.ClassLoader.defineClass0(Native Method)
	at java.base/java.lang.System$1.defineClass(System.java:2050)
	at java.base/java.lang.invoke.MethodHandles$Lookup$ClassDefiner.defineClass(MethodHandles.java:2354)
	at java.base/java.lang.invoke.MethodHandles$Lookup$ClassDefiner.defineClass(MethodHandles.java:2329)
	at java.base/java.lang.invoke.MethodHandles$Lookup.defineClass(MethodHandles.java:1753)
	at weld.core.impl@6.0.3.Final/org.jboss.weld.bean.proxy.util.WeldDefaultProxyServices.defineWithMethodLookup(WeldDefaultProxyServices.java:153)
	at weld.core.impl@6.0.3.Final/org.jboss.weld.bean.proxy.util.WeldDefaultProxyServices.defineClass(WeldDefaultProxyServices.java:62)
	at weld.core.impl@6.0.3.Final/org.jboss.weld.bean.proxy.ProxyFactory.toClass(ProxyFactory.java:975)
	at weld.core.impl@6.0.3.Final/org.jboss.weld.bean.proxy.ProxyFactory.createProxyClass(ProxyFactory.java:509)
	at weld.core.impl@6.0.3.Final/org.jboss.weld.bean.proxy.ProxyFactory.getProxyClass(ProxyFactory.java:416)
	... 37 more

(... does not read module weld.core.impl vs. ... does not read module weld.api)

[theit]

Here's a minimal reproducer; basically the same as in #6041:

jersey-6043.zip

Build the project (mvn clean verify) and start the ping service via mvn exec:exec. When you execute
curl --noproxy '*' http://localhost:8000/ping

you get:

Jan. 08, 2026 10:44:37 AM org.glassfish.jersey.server.ServerRuntime$Responder process
WARNUNG: An exception mapping did not successfully produce and processed a response. Logging the exception propagated to the default exception mapper.
org.jboss.weld.exceptions.WeldException: WELD-001524: Unable to load proxy class for bean org.glassfish.jersey.inject.cdi.se.bean.ClassBean@12d1fcea with class class org.glassfish.jersey.server.internal.process.RequestProcessingContextReference
        at weld.core.impl@6.0.3.Final/org.jboss.weld.bean.proxy.ProxyFactory.getProxyClass(ProxyFactory.java:424)
        at weld.core.impl@6.0.3.Final/org.jboss.weld.bean.proxy.ProxyFactory.instantiateProxy(ProxyFactory.java:375)
        at weld.core.impl@6.0.3.Final/org.jboss.weld.bean.proxy.ProxyFactory.create(ProxyFactory.java:368)
        at weld.core.impl@6.0.3.Final/org.jboss.weld.bean.proxy.ClientProxyFactory.create(ClientProxyFactory.java:84)
        at weld.core.impl@6.0.3.Final/org.jboss.weld.bean.proxy.ClientProxyProvider.createClientProxy(ClientProxyProvider.java:207)
        at weld.core.impl@6.0.3.Final/org.jboss.weld.bean.proxy.ClientProxyProvider.createClientProxy(ClientProxyProvider.java:197)
        at weld.core.impl@6.0.3.Final/org.jboss.weld.bean.proxy.ClientProxyProvider$CreateClientProxy.apply(ClientProxyProvider.java:52)
        at weld.core.impl@6.0.3.Final/org.jboss.weld.bean.proxy.ClientProxyProvider$CreateClientProxy.apply(ClientProxyProvider.java:48)
        at weld.core.impl@6.0.3.Final/org.jboss.weld.util.cache.ReentrantMapBackedComputingCache.lambda$new$0(ReentrantMapBackedComputingCache.java:57)
        at weld.core.impl@6.0.3.Final/org.jboss.weld.util.LazyValueHolder$1.computeValue(LazyValueHolder.java:32)
        at weld.core.impl@6.0.3.Final/org.jboss.weld.util.LazyValueHolder.get(LazyValueHolder.java:46)
        at weld.core.impl@6.0.3.Final/org.jboss.weld.util.cache.ReentrantMapBackedComputingCache.getValue(ReentrantMapBackedComputingCache.java:74)
        at weld.core.impl@6.0.3.Final/org.jboss.weld.util.cache.ReentrantMapBackedComputingCache.getCastValue(ReentrantMapBackedComputingCache.java:80)
        at weld.core.impl@6.0.3.Final/org.jboss.weld.bean.proxy.ClientProxyProvider.getClientProxy(ClientProxyProvider.java:232)
        at weld.core.impl@6.0.3.Final/org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:720)
        at weld.core.impl@6.0.3.Final/org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:746)
        at weld.core.impl@6.0.3.Final/org.jboss.weld.util.ForwardingBeanManager.getReference(ForwardingBeanManager.java:65)
        at weld.core.impl@6.0.3.Final/org.jboss.weld.bean.builtin.BeanManagerProxy.getReference(BeanManagerProxy.java:89)
        at org.glassfish.jersey.inject.cdi2.se@4.0.0/org.glassfish.jersey.inject.cdi.se.CdiSeInjectionManager.getInstanceInternal(CdiSeInjectionManager.java:178)
        at org.glassfish.jersey.inject.cdi2.se@4.0.0/org.glassfish.jersey.inject.cdi.se.CdiSeInjectionManager.getInstance(CdiSeInjectionManager.java:161)
        at org.glassfish.jersey.core.server@4.0.0/org.glassfish.jersey.server.ApplicationHandler.lambda$initialize$4(ApplicationHandler.java:430)
        at org.glassfish.jersey.core.server@4.0.0/org.glassfish.jersey.server.internal.process.ReferencesInitializer.apply(ReferencesInitializer.java:57)
        at org.glassfish.jersey.core.server@4.0.0/org.glassfish.jersey.server.internal.process.ReferencesInitializer.apply(ReferencesInitializer.java:31)
        at org.glassfish.jersey.core.common@4.0.0/org.glassfish.jersey.process.internal.Stages$LinkedStage.apply(Stages.java:284)
        at org.glassfish.jersey.core.common@4.0.0/org.glassfish.jersey.process.internal.Stages.process(Stages.java:173)
        at org.glassfish.jersey.core.server@4.0.0/org.glassfish.jersey.server.ServerRuntime$1.run(ServerRuntime.java:266)
        at org.glassfish.jersey.core.common@4.0.0/org.glassfish.jersey.internal.Errors$1.call(Errors.java:248)
        at org.glassfish.jersey.core.common@4.0.0/org.glassfish.jersey.internal.Errors$1.call(Errors.java:244)
        at org.glassfish.jersey.core.common@4.0.0/org.glassfish.jersey.internal.Errors.process(Errors.java:292)
        at org.glassfish.jersey.core.common@4.0.0/org.glassfish.jersey.internal.Errors.process(Errors.java:274)
        at org.glassfish.jersey.core.common@4.0.0/org.glassfish.jersey.internal.Errors.process(Errors.java:244)
        at org.glassfish.jersey.core.common@4.0.0/org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:266)
        at org.glassfish.jersey.core.server@4.0.0/org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:253)
        at org.glassfish.jersey.core.server@4.0.0/org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:703)
        at org.glassfish.jersey.container.grizzly2.http@4.0.0/org.glassfish.jersey.grizzly2.httpserver.GrizzlyHttpContainer.service(GrizzlyHttpContainer.java:374)
        at org.glassfish.grizzly.http.server@4.0.2/org.glassfish.grizzly.http.server.HttpHandler$1.run(HttpHandler.java:190)
        at org.glassfish.grizzly@4.0.2/org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:535)
        at org.glassfish.grizzly@4.0.2/org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.run(AbstractThreadPool.java:515)
        at java.base/java.lang.Thread.run(Thread.java:1474)
Caused by: java.lang.IllegalAccessError: superinterface check failed: class org.glassfish.jersey.server.internal.process.RequestProcessingContextReference$Proxy$_$$_WeldClientProxy (in module org.glassfish.jersey.core.server) cannot access class org.jboss.weld.interceptor.proxy.LifecycleMixin (in module weld.core.impl) because module org.glassfish.jersey.core.server does not read module weld.core.impl
        at java.base/java.lang.ClassLoader.defineClass0(Native Method)
        at java.base/java.lang.System$1.defineClass(System.java:2050)
        at java.base/java.lang.invoke.MethodHandles$Lookup$ClassDefiner.defineClass(MethodHandles.java:2354)
        at java.base/java.lang.invoke.MethodHandles$Lookup$ClassDefiner.defineClass(MethodHandles.java:2329)
        at java.base/java.lang.invoke.MethodHandles$Lookup.defineClass(MethodHandles.java:1753)
        at weld.core.impl@6.0.3.Final/org.jboss.weld.bean.proxy.util.WeldDefaultProxyServices.defineWithMethodLookup(WeldDefaultProxyServices.java:153)
        at weld.core.impl@6.0.3.Final/org.jboss.weld.bean.proxy.util.WeldDefaultProxyServices.defineClass(WeldDefaultProxyServices.java:62)
        at weld.core.impl@6.0.3.Final/org.jboss.weld.bean.proxy.ProxyFactory.toClass(ProxyFactory.java:975)
        at weld.core.impl@6.0.3.Final/org.jboss.weld.bean.proxy.ProxyFactory.createProxyClass(ProxyFactory.java:509)
        at weld.core.impl@6.0.3.Final/org.jboss.weld.bean.proxy.ProxyFactory.getProxyClass(ProxyFactory.java:416)
        ... 38 more

To get rid of that error uncomment the additional --add-reads arguments in the pom.xml

[arjantijms]

Why is this necessary? As far as I can see jersey-server doesn't make use of Weld and its libraries, only jersey-cdi2-se.

At some point Jersey needs a CDI managed instance of RequestProcessingContextReference:

final ReferencesInitializer referencesInitializer = new ReferencesInitializer(injectionManager,
                () -> injectionManager.getInstance(RequestProcessingContextReference.class));

RequestProcessingContextReference is normal scoped:

@org.glassfish.jersey.process.internal.RequestScoped // normal scope
public class RequestProcessingContextReference implements Ref<RequestProcessingContext> {

    private RequestProcessingContext processingContext;

    @Override
    public void set(RequestProcessingContext processingContext) {
        this.processingContext = processingContext;
    }

    @Override
    public RequestProcessingContext get() {
        return processingContext;
    }
}

So Weld needs to build a proxy for this. The new proxy class has to be added to the package the original class is in:

// these classes go into existing packages, we will use MethodHandles to define them
return defineWithMethodLookup(className, classBytes, originalClass, originalLoader);

[...]

 Module lookupClassModule = lookupBaseClass.getModule();
            if (!thisModule.canRead(lookupClassModule)) {
                // we need to read the other module in order to have privateLookup access
                // see javadoc for MethodHandles.privateLookupIn()
                thisModule.addReads(lookupClassModule);
            }

Weld checks that thisModule (module weld.core.impl) can read the module org.glassfish.jersey.server.internal.process.RequestProcessingContextReference is in. However, the reverse needs to be true too.

The generated proxy (org.glassfish.jersey.server.internal.process.RequestProcessingContextReference$Proxy$_$$_WeldClientProxy.class) has the following imports:

import java.io.ObjectStreamException;
import java.io.Serializable;
import java.lang.reflect.Method;
import org.glassfish.jersey.internal.util.collection.Ref;
import org.glassfish.jersey.server.internal.process.RequestProcessingContext;
import org.glassfish.jersey.server.internal.process.RequestProcessingContextReference;
import org.glassfish.jersey.server.internal.process.RequestProcessingContextReference$Proxy$_$;
import org.jboss.weld.bean.proxy.DefaultBytecodeMethodResolver;
import org.jboss.weld.bean.proxy.InterceptionDecorationContext;
import org.jboss.weld.bean.proxy.MethodHandler;
import org.jboss.weld.bean.proxy.ProxyMethodHandler;
import org.jboss.weld.bean.proxy.ProxyObject;
import org.jboss.weld.bean.proxy.util.SerializableClientProxy;
import org.jboss.weld.interceptor.proxy.LifecycleMixin;
import org.jboss.weld.interceptor.util.proxy.TargetInstanceProxy;
import org.jboss.weld.proxy.WeldClientProxy;
import org.jboss.weld.proxy.WeldConstruct;
import org.jboss.weld.serialization.spi.BeanIdentifier;

That's where the core exception comes from:

java.lang.IllegalAccessError: superinterface check failed: 
     class org.glassfish.jersey.server.internal.process.RequestProcessingContextReference$Proxy$_$$_WeldClientProxy 
            (in module org.glassfish.jersey.core.server) 
cannot access 
      class org.jboss.weld.bean.proxy.ProxyObject 
             (in module weld.core.impl) 
because module org.glassfish.jersey.core.server does not read module weld.core.impl

The generated proxy is in package "org.glassfish.jersey.server.internal.process" and in module "org.glassfish.jersey.core.server". The generated code of that proxy makes use of "org.jboss.weld.bean.proxy", which is in module "weld.core.impl".

Hence, every module for which weld proxies are generated needs to read module "weld.core.impl".

However, "lookupClassModule.addReads(thisModule);" would be illegal, as only code within lookupClassModule may do this.

@Ladicek @manovotn Did you encounter this issue before? Is there a cleaner workaround possible?

[Ladicek]

I'm not familiar with Weld, but seeing that the module names in the stack traces above are weld.api or weld.core.impl make it very clear that Weld JARs have neither a module descriptor nor an explicitly assigned automatic module name, which is a strong suggestion that they are not ready to be used on a module path. So, again, not an expert, but it feels like you're on an unsupported territory.

[arjantijms]

but seeing that the module names in the stack traces above are weld.api or weld.core.impl make it very clear that Weld JARs have neither a module descriptor nor an explicitly assigned automatic module name,

True, Weld itself does not define those. Would be absolutely great if they at some point did.

So, again, not an expert, but it feels like you're on an unsupported territory.

Weld does acknowledge Modules, and is not totally unaware of them as seen in e.g. this code fragment from Weld:

Module lookupClassModule = lookupBaseClass.getModule();
            if (!thisModule.canRead(lookupClassModule)) {
                // we need to read the other module in order to have privateLookup access
                // see javadoc for MethodHandles.privateLookupIn()
                thisModule.addReads(lookupClassModule);
            }

[manovotn]

Weld is pretty much module-unaware at the moment.
The bit you quoted is a default class declaring facility and IIRC this was just one of methods of determining where a proxy class should be placed.

Even if Weld had automatic module names, I am not sure this would help you much. We would need deep reflection access to essentially any library (any declaring a bean) so you'd end up declaring this ability everywhere 🤷
My knowledge of the JPMS is very limited as I have never really used it since delving into it back when it went live so I would need to do quite some homework. But you are right that Weld should add at least the automatic module names at some point.