> On Oct 1, 2025, at 11:03 PM, Markus Jung <[email protected]> wrote: > > Hey all, > > > I've began some first steps towards TomEE 11 and updated our API shade. > Whilst doing so I found that the EE 11 platform spec has these _removals_ > [1]: SOAP Attachements, XML Binding, XML Web Services. Essentially turning > them into standalone specs that aren't tied to EE platform anymore from my > understanding. > > > That poses the question: What do we do with JAXB and JAXWS? The easiest > option would probably be to just remove them and hand over the task of > bringing implementations to the user. But I fear this will cause users a > pretty big disruption when migrating from TomEE 10 to TomEE 11. Also I don't > know TomEE internals too well but I do know we use JAXB quite a bit > internally as well (e.g. with SXC), so might not be too easy to remove.
We use CXF for both the JAX-WS and JAX-RS support. At most we could remove a CXF jar or two. All the standard XML deployment descriptors are still part of the platform, so in practice it will be in all Platform implementations and the removal is at best symbolic. Even CDI has XML deployment descriptors via the beans.xml, so even Core Profile implementations will still have JAXB in it in practice. > Right now my opinion would be to remove these from the jakartaee-api shade as > they're not in EE platform anymore and depending on the application server to > implement them is non-portable behavior but to still regularly support these > APIs in TomEE besides jakartaee-api (like e.g. MP right now) and ship > implementations. It's definitely good to keep the jakartaee-api as close to the platform as we can. We'd still need to include those other api jars in TomEE and in the tomee-foo-api artifact. -David
