Issue: The JAXP+modules story is still a bit of a mess

mark.reinhold at mark.reinhold at
Thu Mar 31 15:48:58 UTC 2016

2016/3/11 9:50:51 -0800, mark.reinhold at
> 2016/3/4 15:06 -0800, david.lloyd at
>> I'm not sure if this is just something that has not yet been gotten 
>> 'round to, but the way JAXP loading works has become somewhat less 
>> convenient.
>> If you are a container author, and you need to supply your own global 
>> default JAXP implementation classes, your options are highly limited: 
>> you can rely on TCCL being set on every call to Xxxx.newFactory() (never 
>> going to happen 100% of the time in reality), or you can set the 
>> appropriate system properties and make your implementation visible from 
>> every class loader (something of the opposite of the kind of 
>> encapsulation that we have modules for).
>> ...
> This is an issue for Java SE 9, and its forthcoming Umbrella JSR, rather
> than for the module system itself.

Further discussion on the OpenJDK core-libs-dev list [1] made me
realize that this is, in fact, a problem that should be solved by a
module-system requirement we previously recorded but have not yet
addressed [2].  Since this is already an open requirement, there's
no need to create a specific open issue for it.

- Mark


More information about the jpms-spec-experts mailing list