Hi,
this probably comes after the battle (sorry for that!) -
https://github.com/eclipse-ee4j/jaxb-api/issues/78 reminded me this
thread... - so for the record:
at this point of time (and in the past) we recommend using
com.sun.xml.bind:jaxb-osgi artifact for usage in OSGi environment. It
contains full JAXB-RI runtime + tooling (xjc/schemaGen). Should this,
for whatever reason, be too big jar, go ahead, file an issue @
https://github.com/eclipse-ee4j/jaxb-ri/issues and we can follow up there.
thanks,
--lukas
On 10/17/18 5:41 PM, Keith Chong wrote:
Are other teams affected by the removal of the javax.xml.bind package
from Java 11?
Web Tools Platform (WTP) Web services has 'unresolved' references when
running with Java 11. See
https://bugs.eclipse.org/bugs/show_bug.cgi?id=539771.
The solution would simply be to pull the javax.xml.bind package into WTP
(from orbit), but, it was originally pulled out of WTP because of
https://bugs.eclipse.org/bugs/show_bug.cgi?id=446080
due to OSGi wiring issues. If we proceed with this solution, we might
re-introduce the wiring issues when using a Java level (non-Java 11)
that contains the deprecated packages.
The info in the two bugzillas indicate that other teams might be
impacted by this. Dali (eg. eclipselink packages) and MyLyn. Thoughts?
Regards,
Keith Chong
WTP Web Services
_______________________________________________
cross-project-issues-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
