Jakub,
On 5/30/24 08:08, Jakub Królikowski wrote:
Hi Christopher,
On Thu, May 30, 2024 at 1:40 PM Christopher Schultz <
[email protected]> wrote:
Jakub,
On 5/30/24 05:25, Jakub Królikowski wrote:
Where is your <Manager> configuration located? It *should* be inside
your <Context> located in META-INF/context.xml in your web application.
If it's in there, then everything it does should be in the context (and
ClassLoader) of your web application -- where your classes should be
locatable.
If you have it anywhere else, it probably won't work the way you expect
it to work.
Yes, you are right! Thank you for this hint!
I have configured <Manager> in <tomcat-dir>/conf/server.xml.
And indeed - interestingly, StandardManager, works correctly even there!
PersistentManager, however, does not.
After moving the configuration to <app-dir>/META-INF/context.xml, both
managers work fine.
It may be worth mentioning this in the documentation:
https://tomcat.apache.org/tomcat-10.1-doc/config/manager.html#Persistence_Across_Restarts
Would you like to provide a documentation patch/PR that works for you?
-chris
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
I can write a paragraph about how to properly prepare the web service for
serialisation and deserialisation, but I need some more time for that,
because I see that the PersistentManager behaves differently from the
StandardManager and I think it tries to serialise also session attributes,
which are not instances of classes that implement java.io.Serializable. I
need more time to experiment.
The objects will always need to be from classes that implement
Serializable. Both PersistentManager and StandardManager use standard
Java serialization to store sessions, though they store the bytes
differently.
-chris
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
