On Feb 21, 2024, at 5:17 PM, James Perkins via rest-dev <rest-dev@xxxxxxxxxxx> wrote:
Speaking just for myself, I need to say that I do have a problem with *removing* JAXB. I have to maintain a software that on one hand shall use latest features,
but on the other hand MUST stick with JAXB for backwards compatibility. It is OK for me that JAXB would become *optional* so I can simply drop it into the mix on my own. But *removing* instead of *optional* is a no-go for me and completely WAY off Java's long-term
backwards compatibility benefit. Having said that, it is not our charter to necessarily do exactly what the platform people dream of just because they would like so, in particular not *forcefully remove* things just because they want to spare maintenance costs
for their paid products or whatever benefit they like to have from *removing* it. Due to that I am -1 for *forcefully removing* JAXB, but I am +1 for having it *optional* in the sense of "application vendors can put it on the classpath if needed". As a side
effect, there is not justification for a 4.0.
-Markus
The removal of XML Binding was already done in the release-4.0 branch [1]. I wouldn't think we'd be doing anything beyond removing the module dependency and the Link.JaxbAdatper and Link.JaxbLink [2].
That’s the only compile-time dependency that I remember, so that is basically it AFAICT.
— Santiago
Is this what you mean or do you mean specifically with the specification document removing the optional XML Binding specification?
FWIW my understanding is we only want to remove the module dependency and the two deprecated types.
Von: rest-dev [mailto:rest-dev-bounces@xxxxxxxxxxx]
Im Auftrag von Jim Krueger via rest-dev
Gesendet: Dienstag, 20. Februar 2024 20:04
An: Jakarta Rest project developer discussions
Cc: Jim Krueger
Betreff: [rest-dev] EE11 Platform call update
In this morning's EE11 Platform call there was renewed concerns about the possibility that Jakarta Rest may need to remain on 3.1 for EE11. The primary point of concern centered
around the fact that XML binding would be moving to optional in EE11. This will cause a problem for Jakarta Rest since the deprecated dependency with JAXB is not slated for removal prior to JAkarta Rest 4.0. It was discussed that we might be asked to put out
Jakarta Rest 4.0 containing only the removal of the JAXB dependency. I'd also assume if our work with release-3.2 reaches a point where it could be included in EE11 that there would likely be a push to rename 3.2 to 4.0 in order to allow the JAXB dependency
removal to be included.
I was not in a position to advocate a course of action. I felt that the group should be made aware of this discussion.
_______________________________________________
rest-dev mailing list
rest-dev@xxxxxxxxxxx
To unsubscribe from this list, visit
https://accounts.eclipse.org
--
James R. Perkins
JBoss by Red Hat
_______________________________________________
rest-dev mailing list
rest-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://urldefense.com/v3/__https://accounts.eclipse.org__;!!ACWV5N9M2RV99hQ!J5foP08J_XQHAeZT9ZvqEExu45Gy-88FnuocyjoLkPlP78zpO--5ZTJ4ORylKyZm0OndpZc-UodBUKa7_iPsztIHw_0o$
|
