[prev in list] [next in list] [prev in thread] [next in thread]
List: geronimo-dev
Subject: Re: MP-JWT progress
From: Romain Manni-Bucau <rmannibucau () gmail ! com>
Date: 2018-03-19 18:01:06
Message-ID: CACLE=7PV2ZMhEG8NXRiogNK1F2tkW1T2+5GA9iVk_MjRZyU8bg () mail ! gmail ! com
[Download RAW message or body]
Jwt-auth impl doesnt depend on tomee and is reusable so must not be put in
tomee codebase.
Hope it is clearer this time.
Le 19 mars 2018 18:54, "John D. Ament" <johndament@apache.org> a =C3=A9crit=
:
> On Mon, Mar 19, 2018 at 3:20 AM Romain Manni-Bucau <rmannibucau@gmail.com=
>
> wrote:
>
> > 2018-03-19 0:07 GMT+01:00 John D. Ament <johndament@apache.org>:
> >
> >>
> >>
> >> On Sun, Mar 18, 2018 at 5:38 PM Romain Manni-Bucau <
> rmannibucau@gmail.com>
> >> wrote:
> >>
> >>>
> >>>
> >>> Le 18 mars 2018 21:29, "David Blevins" <david.blevins@gmail.com> a
> >>> =C3=A9crit :
> >>>
> >>>
> >>> > On Mar 18, 2018, at 12:43 PM, Romain Manni-Bucau <
> >>> rmannibucau@gmail.com> wrote:
> >>> >
> >>> > 1. code will be at geronimo - whatever happens at tomee
> >>>
> >>> As far as I understand the topic is still open and no git repos have
> >>> been created anywhere yet, is that right?
> >>>
> >>>
> >>> Yes
> >>>
> >>>
> >>> Is there anyone on the Geronimo side who would be open to collaborati=
ng
> >>> on a reusable JWT library under the TomEE project for a change?
> Something
> >>> not branded tomee or geronimo.
> >>>
> >>>
> >>> This is what was proposed to be created @g which is just an umbrella,
> no
> >>> more a project delivery by itself.
> >>>
> >>> Are you against/-1ing g-jwt-auth?
> >>>
> >>
> >> As mentioned elsewhere in the thread, I am against bringing something =
in
> >> geronimo that is TomEE specific. I haven't looked at the code (as far
> as I
> >> can tell, nothing is linked in this thread so I have no idea if code
> even
> >> exists) but based on what I've seen with implementing JWT it's closely
> tied
> >> to your container. So I don't believe its a good fit.
> >>
> >> Why is your preference to bring this into geronimo?
> >>
> >
> > As mentionned there is no link to TomEE in the jwt-auth codebase so no
> > reason to hold that code in something not reusable at tomee.
> >
>
>
> Too many negatives in that sentence to make sense of what you're trying t=
o
> say.
>
>
> >
> >
> >>
> >>
> >>>
> >>>
> >>>
> >>> -David
> >>>
> >>>
> >>>
> >
>
[Attachment #3 (text/html)]
<div dir="auto">Jwt-auth impl doesnt depend on tomee and is reusable so must not be \
put in tomee codebase.<div dir="auto"><br></div><div dir="auto">Hope it is clearer \
this time.</div></div><div class="gmail_extra"><br><div class="gmail_quote">Le 19 \
mars 2018 18:54, "John D. Ament" <<a \
href="mailto:johndament@apache.org">johndament@apache.org</a>> a écrit :<br \
type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex">On Mon, Mar 19, 2018 at 3:20 AM \
Romain Manni-Bucau <<a \
href="mailto:rmannibucau@gmail.com">rmannibucau@gmail.com</a>><br> wrote:<br>
<br>
> 2018-03-19 0:07 GMT+01:00 John D. Ament <<a \
href="mailto:johndament@apache.org">johndament@apache.org</a>>:<br> ><br>
>><br>
>><br>
>> On Sun, Mar 18, 2018 at 5:38 PM Romain Manni-Bucau <<a \
href="mailto:rmannibucau@gmail.com">rmannibucau@gmail.com</a>><br> >> \
wrote:<br> >><br>
>>><br>
>>><br>
>>> Le 18 mars 2018 21:29, "David Blevins" <<a \
href="mailto:david.blevins@gmail.com">david.blevins@gmail.com</a>> a<br> \
>>> écrit :<br> >>><br>
>>><br>
>>> > On Mar 18, 2018, at 12:43 PM, Romain Manni-Bucau <<br>
>>> <a href="mailto:rmannibucau@gmail.com">rmannibucau@gmail.com</a>> \
wrote:<br> >>> ><br>
>>> > 1. code will be at geronimo - whatever happens at tomee<br>
>>><br>
>>> As far as I understand the topic is still open and no git repos have<br>
>>> been created anywhere yet, is that right?<br>
>>><br>
>>><br>
>>> Yes<br>
>>><br>
>>><br>
>>> Is there anyone on the Geronimo side who would be open to \
collaborating<br> >>> on a reusable JWT library under the TomEE project for \
a change? Something<br> >>> not branded tomee or geronimo.<br>
>>><br>
>>><br>
>>> This is what was proposed to be created @g which is just an umbrella, \
no<br> >>> more a project delivery by itself.<br>
>>><br>
>>> Are you against/-1ing g-jwt-auth?<br>
>>><br>
>><br>
>> As mentioned elsewhere in the thread, I am against bringing something in<br>
>> geronimo that is TomEE specific. I haven't looked at the code (as far \
as I<br> >> can tell, nothing is linked in this thread so I have no idea if \
code even<br> >> exists) but based on what I've seen with implementing JWT \
it's closely tied<br> >> to your container. So I don't believe its a \
good fit.<br> >><br>
>> Why is your preference to bring this into geronimo?<br>
>><br>
><br>
> As mentionned there is no link to TomEE in the jwt-auth codebase so no<br>
> reason to hold that code in something not reusable at tomee.<br>
><br>
<br>
<br>
Too many negatives in that sentence to make sense of what you're trying to<br>
say.<br>
<br>
<br>
><br>
><br>
>><br>
>><br>
>>><br>
>>><br>
>>><br>
>>> -David<br>
>>><br>
>>><br>
>>><br>
><br>
</blockquote></div></div>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic