On October 28, 2019 1:11:46 PM UTC, Christopher Schultz <ch...@christopherschultz.net> wrote: >-----BEGIN PGP SIGNED MESSAGE----- >Hash: SHA256 > >Mark, > >On 10/28/19 08:15, Mark Thomas wrote: >> Hi all, >> >> A frequent topic of discussion at ApacheCon EU was Jakarta EE 9. >> For those of you who aren't familiar with Jakarta EE the key points >> are: >> >> - Oracle have donated Java EE to Eclipse - Eclipse have released >> Jakarta EE 8 which is essentially identical to Java EE 8 - Oracle >> have refused to allow changes to the APIs in the javax namespace - >> The Jakarta EE community seem to be reaching consensus on releasing >> Jakarta EE 9 which will rename all the Java packages from javax.* >> to jakarta.* - Jakarta EE 9 will not contain any other API changes >> - It will be a requirement to maintain backwards comparability >> (maybe not 100% compatibility) with Jakarta EE 8 - Jakarta EE 9 >> will be released in the next ~11 months - Jakarta EE 10 will then >> follow which is where new features will be introduced >> >> This raises various questions for the Tomcat community including: >> >> 1. Do we implement Jakarta EE 9? >> >> Assuming yes to q1. >> >> 2. As Tomcat 10 or some other version? >> >> 3. How do we manage development (in a branch, as master, ...)? >> >> 4. How do we implement backwards compatability? Runtime, deploy >> time, compilation time? >> >> 5. At what point do we EOL Tomcat 7? (since Jakarta EE 9 is just a >> package renaming?) >> >> 6. Do we commit to supporting Tomcat 9 for an extended period? (to >> provide a version that supports java.* directly) >> >> I'm posting this to users@ as how Tomcat users want to use and >> adopt Jakarta EE 9 is likely to be the biggest driving factor in >> choosing answers to these questions. >> >> We don't have to have all of the answers right now. I think we do >> need answers for 1 & 3 so we can start. A few options and 'wait and >> see' is likely good enough for the rest for now. >> >> I have my own views on the answers but I have tried not to express >> them here so we can get as wide a discussion as possible. > >How "simple" of a replacement are we talking about, here? For example, >can it be done simply with sed?
Probably not. JSPs are likely to be more complicated. The XSDs are probably not an issue. Request attributes and similar may need to support both javax.* and jakarta.* names for attributes. The detail is TBD. >$ find . -type f | xargs sed -e 's/javax.servlet/jakarta.servlet/g' > >? > >I'm asking because if it really is that easy, then we should be able >to trivially package each of the existing Tomcat 7, 8.5, 9 releases as >7.jakarta, 8.5.jakarta, and 9.jakarta alongside their legacy Java EE >versions. That only works if users can have separate Tomcat instances for javax.* based apps and jakarta.* based apps. My sense is that that will not be an acceptable option for all users. >Users wanting to move to the Jakarta EE namespace can do so with >existing, reliable versions of Tomcat instead of waiting for Tomcat 10 >or Tomcat having to implement some kind of hybrid version which >supports BOTH flavors of APIs (which seems kind of nightmarish to me). A runtime solution to compatibility would not be my first choice. I'm currently learning towards a BCEL based solution(or simikar) at deployment time. >Are there any restrictions against us supporting Jakarta EE in >existing Tomcat releases? Naming could be an issue. There might also be some very minor API changes as well as the package rename. That would make that tricky. Mark > I don't believe so. We merely advertise >support for various standards; Tomcat is no longer the "reference >implementation" of any APIs so we can do whatever we want, right? > >If we do a simply sed-style re-naming of packages to produce parallel >releases, will they actually work? My sense is that, yes, they will >indeed work. > >- -chris >-----BEGIN PGP SIGNATURE----- >Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/ > >iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAl226RIACgkQHPApP6U8 >pFjnfQ//bYExvm+BEhwroa/W+v3BGx+Bw0qtzz9MxjDIZ1zcGuxlITb1QdoYZ1sz >C9eQumSo/gK1sO8ImVhMCYdFOf1n2az/olcMdF2v9gYC3YMZ11+qQhppYRxvfRvG >pHzkV4PHbE6mgvfY9pli6LBs1Na1MSN0nRLluC4OBz3wMGCLQyByfBX3x+++8klB >HHM1wcJDLzziIBmM3NKcuEFQ1gVbjlV10rFYes29KiuG4z78FRPY87pQmP+Xj71o >l5NEtERYA+SjDGPZo6wrF6k3l23cZL/yrCp4PGwO1c0VB148DervvWG33+9OEOQL >1E8F0IZc2o2eiNYUxbUQcMxGXORnfbWpMyG8RVSVlwdhmzO4Ug1pxNVcpO2Y2qC2 >vHHz+deQiQ/dZIsNU5aWtC+MBL7tx3RWxBNxb3n2d5T9tJm6zHBSdGfcPyTN14cV >HTtPj9al4usxoT3XGSEhAP7FiI1RJXywq+o0sppaF6BrAh0UpRIYhLtU0vh80b+J >r5XClSUuQAzlWY6N6TOEHBWWDIxZ0Y2Jjx//Yz4x1XO6BVLs4Z0OhWsa0sZ+3cfg >e8jaTZHcTkX6rSZCXxExELJlsOke0KcA+IaPf/zQFJUiTEEteIck60GONKaPLtoC >mNaBAh7qJp7zzrl82OswiaJdksj+g76Xh4JdVFLlv1BDRbWiXVM= >=kSej >-----END PGP SIGNATURE----- > >--------------------------------------------------------------------- >To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >For additional commands, e-mail: users-h...@tomcat.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
