Hi, We are also in the process of migrating to Jakarta EE 9/10 and Shiro is one of the libraries missing native support. Transformers only work on an application built entirely against JEE8. You simply cannot build your application with mixed JEE versions. For example, when one method returns a javax.servlet.http.HttpServletRequest, you cannot pass it to a method expecting a jakarta.servlet.http.HttpServletRequest. This just won't compile. At the moment we use transformed dependencies deployed in our company repository, but this is only short term solution and requires a lot of work with every upgrade of such a transformed library. A Jakarta EE 9/10 release of Shiro would be really welcome.
Best regards, Emond On Fri, May 13, 2022 at 9:06 PM Thomas Heigl <[email protected]> wrote: > Hi, > > I'm in the process of upgrading my application to Spring 6, Spring Boot 3 > and Hibernate 6. That means moving to the Jakarta APIs. Shiro is my only > dependency that doesn't have a (pre)release based on Jakarta yet. > > While most containers will be able to support legacy javax APIs at runtime > or via transformer tools, this is far from optimal. Tomcat, for instance, > requires apps with legacy APIs to be deployed to a special context or > transformed via a a custom tool ( > https://tomcat.apache.org/migration-10.html). > > My question is: Are there plans to release a Jakarta based version of > Shiro in the foreseeable future? Spring 6, for instance, is planned for > release some time in September. > > Can we expect a Jakarta Shiro release by then? > > Best, > > Thomas > > On 2022/05/10 17:50:45 Lenny Primak wrote: > > All modern application servers and runtimes include javax.* packages > themselves. > > So, if you upgrade to Jakarta EE 8 compatible server or runtime you > should have no issues > > However, if you elect using Jakarta EE 9.1 or greater, it uses jakarta.* > packages. > > Most runtimes and servers have built-in transformer to run older javax.* > compatible packages including shiro-web > > at runtime so you should have no issues. > > > > > On May 10, 2022, at 7:36 AM, De Luise, Massimiliano < > [email protected] <mailto: > [email protected]>> wrote: > > > > > > Hi all! > > > I’m writing this email in order to check if shiro-web is compliant > with jdk 11+, specifically with jakarta library since javax library is > removed. > > > > > > It seems to me that shiro-web still uses the javax.servlet library. > > > In fact: looking at the pom.xml of the last available version in maven > central (available at > https://repo1.maven.org/maven2/org/apache/shiro/shiro-web/1.9.0/shiro-web-1.9.0.pom > < > https://repo1.maven.org/maven2/org/apache/shiro/shiro-web/1.9.0/shiro-web-1.9.0.pom>), > or taking a look at the pom.xml of the github repository ( > https://github.com/apache/shiro/blob/main/pom.xml < > https://github.com/apache/shiro/blob/main/pom.xml>), it can be seen the > javax.servlet dependency and not the jakarta.servlet. > > > > > > Can you please provide me some info about this? > > > Best regard, > > > Massimiliano De Luise > > > > >
