Uploaded image for project: 'Weld'
  1. Weld
  2. WELD-2828

Ensure a proxy target JPMS module can read Weld JPMS modules

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 7.0.0.Alpha2, 6.0.5.Final
    • 7.0.0.Alpha1, 6.0.4.Final
    • None
    • None

      WeldDefaultProxyServices attempts to reads any module we end up putting proxies into.
      However, the opposite is required for Weld to work as well because those proxy classes reference Weld impl/api classes.

      ATM Weld lacks module names but even if there were some, users are expected to declare their dependency on CDI modules, not the impl-specific ones like Weld.
      We can workaround this by generating some bytecode into those packages and have it declare reads on Weld. It isn't the nicest thing to do, but it should do the trick.

      Note: Integrators can and often should provide their own implementations of the ProxyServices. The default one there mainly for SE where no integrator is presumed and also as a template.

              Unassigned Unassigned
              manovotn Matěj Novotný
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: