[ANN] Pax Web 8.0.10 and 9.0.1 released

[Grzegorz Grzybek]

Hello

I'd like to announce new minor releases of Pax Web: 8.0.10 and 9.0.1.

There were quite a few actual bug fixes related to how TCCL is configured
and how default context can be overriden.

Jetty and Tomcat runtimes are upgraded and the current versions are:

   - Jetty 9.4.49.v20220914
   - Tomcat 9.0.67
   - Undertow 2.2.19.Final

There's a new PID configuration option called "org.ops4j.pax.web.tccl.type"
introduced with this issue
[1]. It accepts two
options:

   - "servlet" (which is the default) - TCCL inside service methods (like
   servlet.doGet()) is set to an OsgiServletContextClassLoader which delegates
   to all the bundles that are reachable for the context - this is perfect
   setting for a WAB scenario, however in Whiteboard scenario, TCCL doesn't
   delegate to bundles of the dynamically registered servlets! The problem is
   that each time a servlet is whiteboard-registered into a context, servlet's
   bundle would have to be added to the underlying list of bundles, but it
   causes classloader leaks due to the very JVM specification
   - "whiteboard" - TCCL is set for each service method (separately for
   each filter and target servlet in invocation chain) to a bundle classloader
   of the actual filter/servlet

The problem with TCCL is that no OSGi CMPN specification mentions TCCL at
all and I simply followed the "principle of least surprise
"[2].

For completeness, the changelogs is available for 8.0.10[3] and 9.0.1[4].

kind regards
Grzegorz Grzybek
===
[1]: https://github.com/ops4j/org.ops4j.pax.web/issues/1760
[2]: https://en.wikipedia.org/wiki/Principle_of_least_astonishment
[3]: https://github.com/ops4j/org.ops4j.pax.web/milestone/224?closed=1
[4]: https://github.com/ops4j/org.ops4j.pax.web/milestone/225?closed=1

Re: Latest karaf 4.4.1 issue with java.base package import issue(OpenJDK11)

[Jean-Baptiste Onofré]

Hi,

I guess you have the issue at deployment time while running Karaf right ?
The JDK11 args (add exports, open, etc) are defined in the bin/karaf (or
wrapper conf if you are using the wrapper).

Regards
JB

On Fri, Sep 23, 2022 at 8:13 PM Vamsikrishna Koka
 wrote:

> Hi Team,
>
>
>
> We are tried to upgrade latest KARAF from KARAF  *4.2.15* to KARAF *4.4.1*
> version with *OpenJDK 11*. And tried osgi.annotation/7.0.0 or 8.1.0 both
> version .
>
> Release Note KARAF 4.4.1
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12351548
>
>
>
> While doing maven build our product, the build was failed due to package
> sun.security.krb5.internal is not visible
> [ERROR]   (package sun.security.krb5.internal is declared in module
> java.security.jgss, which does not export it to the unnamed module).
>
>
>
> The above issue for fixing, I have added given below compilerArgs tag then
> only maven build working. We do have any best solution the above issue?
> without adding the given below  compilerArgs tags.
>
>
>
>  
>
>  ${java.version}
>
>  ${java.version}
>
> 
>
>   
>
>   --add-exportsjava.base/sun.nio.ch
> =ALL-UNNAMED
>
>
> --add-exportsjava.base/jdk.internal.ref=ALL-UNNAMED
>
>   
>
>  
>
>
>
> Thanks,
> * VamsiKrishna*
> Senior Software Engineer
>
> Mob: +91 9381078936
>
>
> [image: Motivitylabs - Enabling Mobile Enterprises]
>
> *US: *222 W. Las Colinas Blvd.
> Suite 755 East
> Irving, TX 75039
> Ph:+1-214-730-0798
>
> *INDIA:* 9th & 10th floor, Water Mark Building, Kondapur, Hitech City,
> Hyderabad 500 084, Telangana.
> Ph:+91-40-4651-5454
>
> *Confidentiality Note:* This message is confidential. It may also be
> privileged or otherwise protected by work product immunity or other legal
> rules. This email and any files transmitted with it are confidential and
> intended solely for the use of the individual or entity to whom they ar
>
>
>
>
>