ppkarwasz edited a comment on pull request #16:
URL: 
https://github.com/apache/tomcat-jakartaee-migration/pull/16#issuecomment-806549378


   @rmaucher: I fail to understand how changing the `TOMCAT` profile will cause 
problems for others, because I don't understand the purpose of this profile. 
When one would want to use the `TOMCAT` profile instead of the `EE` profile?
   
   The way I imagine it should work is:
   
   1. You want to migrate your application to Jakarta EE 9, use the `EE` 
profile and **replace** all spec jars shipped with the application,
   2. If you don't use any Java EE technology, besides those implemented by 
Tomcat, but you are using annotations: transform the application **before** 
deployment (IIRC the annotation scanner does not interact with the class 
loader) with the `TOMCAT` profile,
   3. If you are not using annotations nor `ServletContainerInitializer`s (the 
latter limitation can be relaxed), just configure the application context with 
`jakartaConverter="TOMCAT"` and deploy the application **as is**.
   
   Of course I would settle for an alternative profile, which works for case 3. 
I am bad with names, so a proposition is welcome.
   
   Packaging both versions of the spec jars is also a solution, but our clients 
tend to upgrade our applications very rarely: some applications run a couple of 
years before they upgrade. We even found recently several Tomcat 8.0.5 and 
9.0.0-M10 installations (probably they fought `M` stands for _max_). Therefore 
we are looking for a solution that requires the minimal amount of configuration 
to accommodate clients which run Tomcat 7.0 and Tomcat 10.0, possibly without 
modifying `CATALINA_HOME` (due to the widespread practice of _"upgrading"_ 
Tomcat by installing a new version and moving the `webapps` folder, all 
upgrades would require our intervention).


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Reply via email to