Problem with JAXBContext.newInstance

[Oliver Z.]

I found the solution. Pretty trivial, but probably unexpected when 
migrating. It is required to have 2 require entries in the 
module-info.java. I guess one for the API, and one for the implementation:

requires java.xml.bind;
requires com.sun.xml.bind;

Then it works. Thanks for your effort!

Am 13.02.19 um 12:30 schrieb Alan Bateman:
> On 13/02/2019 11:14, Oliver Z. wrote:
>> Can you tell me where i can download the JAXB 2.4 final module? I 
>> only found 2.4.0-b... which does not seem to be a final to me.
>>
>> I also tried to write to that list but i am waiting for approval, 
>> which seems pretty long now (maybe the owner is on vacation or so..). 
>> Do you know any other mailing list/resource i could contact to get 
>> that information? Otherwise i guess i have to go with xstream to not 
>> to be blocked for days now.
> I think you need to follow up on the Eclipse or Jakarta EE mailing 
> lists about this as JAXB is not maintained here. From what I can tell 
> from the release notes [1],  the Java EE JAXB project released 2.4.0 
> with changes to fix the issues they had deploying the JAXB runtime on 
> the module path. It was a bit awkward before those changes in that you 
> had to leave the runtime on the class path when running with 
> java.xml.bind on the module path. I have no insight into why the 
> download on the Eclipse site is 2.3.2 rather than the latest.
>
> -Alan
>
> [1] https://javaee.github.io/jaxb-v2/doc/user-guide/ch02.html#a-2-4-0