On 20/04/2017 13:57, David M. Lloyd wrote:

Let's say I want to create a module distribution with my own JSR 250 classes. Let's also assume that I or the spec team want the module to be named java.annotations.common.

How do I properly upgrade the JDK's java.xml.ws.annotation module such that java.xml.ws can see it, *and* I have my proper java.annotations.common module name? Am I forced to ship my annotations module as java.xml.ws.annotation? Or manually replace java.xml.ws with one that looks for my annotations (and where does that leave the original java.xml.ws.annotation module)?

java.xml.ws.annotation is upgradable so all you need to do is deploy the compiled form of the following on the upgrade module path:

module java.xml.ws.annotation {
    requires transitive java.annotations.common;
}

Separately, I don't know what name that JSR-250 will eventually choose. It could be indeed be "java.annotations.common", maybe "java.ee.annotation", maybe something else.

-Alan

Reply via email to