[ 
https://issues.apache.org/jira/browse/TOMEE-2839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Richard Zowalla resolved TOMEE-2839.
------------------------------------
    Resolution: Fixed

> Investigate uses of "javax"
> ---------------------------
>
>                 Key: TOMEE-2839
>                 URL: https://issues.apache.org/jira/browse/TOMEE-2839
>             Project: TomEE
>          Issue Type: Task
>            Reporter: David Blevins
>            Priority: Major
>
> *Short version:*
>  #  Locate the source code in github and see if you can find the file and 
> line number of the indicated "javax" references.
>  # Post the github links to file & line number to jira ticket
>  # *Bonus*, see if you can figure out what the code is doing (at least a 
> little) and update the ticket
>  
> *Longer version:*
> In Jakarta EE 9 all the APIs have been repackaged from javax to jakarta.  For 
> example `javax.servlet.http.HttpServlet` becomes 
> `jakarta.servlet.http.HttpServlet`
>  
> We're using tooling to perform bytecode transformation on all the jars and 
> classes in TomEE 8 so that we can create a distribution of TomEE that can be 
> made both Jakarta EE 8 and Jakarta EE 9 compliant.  When the references are 
> classes, it's very easy.  When the references are strings, it's harder as you 
> have to look at the code and see what it is doing with the string and if its 
> logic will still work or if it needs to be adjusted.
>  
> We need a community effort to divide and conquer on these to see if we can 
> figure out if the uses are safe or some change needs to happen.
>  
> Full list of packages being renamed from javax to jakarta
>  * [https://gist.github.com/dblevins/9a6d4b1c90986a4116dd738c9e5ef212]
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to