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