Hi,

Great, thanks for the reply.

We've been testing this for about a week now and haven't run into any
issues. In this setup, we export the Servlet API 6.0 packages with both
version 6.0 and 6.1, with the 6.1 export only being used to satisfy the
Bridge import. This has been working fine so far.

Would it be possible to release a Bridge version with a [6.0,7) import, so
that we can avoid exporting the Servlet API 6.0 as 6.1?

Kind regards,
Erwin

On Thu, Mar 12, 2026 at 9:37 AM Carsten wrote:

> Hi,
>
> yes, I think this is similar to http.base, the bridge should work with
> Servlet API 6.0. I think the best is if you could give it a try - if you
> are not running in class not found errors, it will work.
>
> Regards
> Carsten
>
> On 3/10/2026 11:06 AM, Erwin wrote:
> > Hi,
> >
> > In an existing project that uses Felix HTTP Proxy and Bridge, we are
> > migrating from Java EE to Jakarta EE 10 (Tomcat 10.1.x). It appears that
> > Felix Bridge (6.0 / 6.1) requires Jakarta Servlet API 6.1 (Jakarta EE
> 11),
> > and I have not been able to find a Felix Bridge release that works with
> > Jakarta Servlet API 6.0.
> >
> > Does Felix Bridge really require Servlet 6.1, or would it work correctly
> > with Servlet 6.0 as well? The Bridge bundles (version 6.0 and 6.1)
> > currently declare a dependency on jakarta.servlet;version="[6.1,7)", but
> > could [6.0,7) suffice?
> >
> > Unfortunately, we are not yet able to migrate to Jakarta EE 11 because we
> > also use WildFly, which does not currently support EE 11. So I'm hoping
> > that Felix can run on Servlet API 6.0.
> >
> > This seems related to the discussion in the thread 'Unexpected Jakarta
> > Servlet 6.1.0 dependency in org.apache.felix.http.base 5.1.14' [1].
> >
> > Thanks in advance for any clarification.
> >
> > Kind regards,
> > Erwin
> >
> > [1] https://lists.apache.org/thread/9ryfpv7lv5zq8j2bqk8788vp310v0y66
> >
>
> --
> Carsten Ziegeler
> Adobe
> [email protected]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to