o package any other
> libraries as the see fit.
>
> Mark
>
>
> 6 Apr 2022 01:23:01 Cherio :
>
> > This makes no sense.
> >
> > The application and the container need to be able to maintain an
> > independent life cycle of the libraries. I may want to upd
versions. An
application needs to be able to bring its own libraries.
Unless I misunderstood the meaning of what you said you sir are completely
wrong on this
On Tue, Apr 5, 2022 at 5:37 PM Mark Thomas wrote:
>
> 5 Apr 2022 20:58:26 Cherio :
>
> > I found what the issue is. This has
pplication supplied JAR.
What's the recommendation on this?
On Tue, Apr 5, 2022 at 11:17 AM Cherio wrote:
> I did ran the diffs between versions. With my naked eye I didn't spot
> anything obvious that in my mind would be directly related to this behavior
> change.
>
&
behave.
On Tue, Apr 5, 2022 at 10:42 AM Rémy Maucherat wrote:
> On Tue, Apr 5, 2022 at 4:02 PM Cherio wrote:
> >
> > Yes, I confirm. For this project I download Tomcat from here:
> >
> https://archive.apache.org/dist/tomcat/tomcat-$MAJOR_VER/v$VER/bin/apache-tomcat-$VER.ta
I forgot to mention that the Tomcat stack trace I posted earlier is from
Tomcat 9.0.62. The change in behavior was observed starting Tomcat 9.0.60
On Tue, Apr 5, 2022 at 10:01 AM Cherio wrote:
> Yes, I confirm. For this project I download Tomcat from here:
>
> https://archive.apache
> Handy: 0049 (0)176 / 87 521 576
> Handy: 0049 (0)176 / 47 876 303
>
>
>
> Gesendet: Freitag, 01. April 2022 um 23:02 Uhr
> Von: "Cherio"
> An: users@tomcat.apache.org
> Betreff: PostConstruct annotation in a filter since version 9.0.60
> I observed an ann
I observed an announced change in behavior in version 9.0.60 (and later).
My application has a Spring class loaded as a javax.servlet.Filter. It has
a method annotated with a PostConstruct annotation. Up until Tomcat 9.0.59
the annotation was handled by Spring. Starting with Tomcat 9.0.60 behavior
