On 15/07/2015 23:36, Christopher Schultz wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Ludovic,
On 7/15/15 3:29 AM, l.pe...@senat.fr wrote:
On 13/07/2015 15:13, Christopher Schultz wrote:
It looks like you or DeltaSpike are not cleaning-up as the
request transitions from one state to another.
Ok, thank you.
What kind of notification should we process to detect this
transition ?
I'm not sure, since it's DeltaSpike which is objecting to the current
state of the request.
I think you'll have better luck with asking the DeltaSpike folks. They
are welcome to come here to ask about why something may have changed.
Was there ever a reply to your initial question?
Yes, and a patch allowing this "double initialization".
But as I suspect that there is something "cleaner" to do, I try to
scratch the subject.
In your post to their list, you mentioned that "there are sometimes
Pretty much the same than in this case, if I sum it up.
A typical example : years ago, I wrote a web filter, had to perform some
locking in it (because of legacy libs) and was quite surprised to see
the request going through the filter twice when serving a
login page on FORM auth.
I am no JEE Guru, so "strange" does not mean "bad" but "surprising".
Thanks,
Ludovic
|
| AVANT D'IMPRIMER, PENSEZ A L'ENVIRONNEMENT.
|
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
