Hi Thomas, We should already support the Jakarta XSD. Those should be tested in the Jakarta EE 9.1 TCK which we pass. The namespaces have changed a few times over the years, so documents are adapted on the fly using SAX. Supporting old and new descriptors is a requirement for compliance.
Usually there are some new additions we have to account for on new EE versions. That's typically either a manual task for alternatively you can re-generate by hand and carefully copy just the new objects over. There are lot of threads from over the years on why we do this. In terms of deleting the WLS xml support, as they don't really cost anything to keep there what would be the advantage? -David > On Jan 23, 2024, at 1:11 AM, Thomas Andraschko <andraschko.tho...@gmail.com> > wrote: > > Hi, > > as you may know, i'm currently working on TomEE10. All our applications are > working fine now. > > i currently have some timeslots to refactor some parts and the whole XML > parsing in container/openejb-* is quite weird. There is still JAXB and SXC. > All mappings are very old (EE6). > > Should we migrate it to current Jakarta XSDs and remove support for older > XMLs? > IMO now is the right time to do it because users need to migrate to jakarta > namespace anyway. > > What about the WLS xmls? Can we remove support for this? > > Best regards, > Thomas
