Am 2020-01-28 um 22:56 schrieb Mark Thomas:
On 28/01/2020 21:50, Christopher Schultz wrote:
Michael,
On 1/28/20 3:51 PM, Michael Osipov wrote:
Am 2020-01-25 um 12:13 schrieb Mark Thomas:
On 23/01/2020 10:29, Michael Osipov wrote:
Design questions: * Shall this remain a listener or do we
On Wed, Jan 29, 2020 at 5:26 PM Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Mark,
>
> On 1/28/20 4:56 PM, Mark Thomas wrote:
> > On 28/01/2020 21:50, Christopher Schultz wrote:
> >> Michael,
> >>
> >> On 1/28/20 3:51 PM,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mark,
On 1/28/20 4:56 PM, Mark Thomas wrote:
> On 28/01/2020 21:50, Christopher Schultz wrote:
>> Michael,
>>
>> On 1/28/20 3:51 PM, Michael Osipov wrote:
>>> Am 2020-01-25 um 12:13 schrieb Mark Thomas:
On 23/01/2020 10:29, Michael Osipov
On 28/01/2020 21:50, Christopher Schultz wrote:
> Michael,
>
> On 1/28/20 3:51 PM, Michael Osipov wrote:
>> Am 2020-01-25 um 12:13 schrieb Mark Thomas:
>>> On 23/01/2020 10:29, Michael Osipov wrote:
>>>
>>>
>>>
Design questions: * Shall this remain a listener or do we want
to introduce
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Michael,
On 1/28/20 3:51 PM, Michael Osipov wrote:
> Am 2020-01-25 um 12:13 schrieb Mark Thomas:
>> On 23/01/2020 10:29, Michael Osipov wrote:
>>
>>
>>
>>> Design questions: * Shall this remain a listener or do we want
>>> to introduce a new
Am 2020-01-25 um 12:13 schrieb Mark Thomas:
On 23/01/2020 10:29, Michael Osipov wrote:
Design questions:
* Shall this remain a listener or do we want to introduce a new
interface for that? If yes, how should it look like?
Given the use cases (could apply at various levels) a
On Sat, Jan 25, 2020 at 12:13 PM Mark Thomas wrote:
> On 23/01/2020 10:29, Michael Osipov wrote:
>
>
>
> > Design questions:
> > * Shall this remain a listener or do we want to introduce a new
> > interface for that? If yes, how should it look like?
>
> Given the use cases (could apply at
On 23/01/2020 10:29, Michael Osipov wrote:
> Design questions:
> * Shall this remain a listener or do we want to introduce a new
> interface for that? If yes, how should it look like?
Given the use cases (could apply at various levels) a LifecycleListener
looks like a reasonable design choice
Folks,
I'd like to discuss the architecture of BZ 55477 [0], this shall apply
to Tomcat 8.5+ only.
The feature has been requested several times over time years, being able
to map some technical role from a specific store to an application role.
E.g., A group SID from AD
