> On Mar 29, 2018, at 3:03 PM, Matthew Broadhead > <matthew.broadh...@nbmlaw.co.uk> wrote: > > i would like JWT support but it has to be done right. is the plan to place > it as a sub project under the TomEE umbrella? is the project going to have a > future as an independent module which can be reused in G etc?
Current status is there's a PR with 19 new classes in it that aren't already in TomEE. They could potentially be reusable outside of TomEE. The code could potentially be less classes if refined. The discussion is where should that exploration be done. I think it'd also be pragmatic to evaluate how much overhead 19 classes are worth; it's own jar, it's own git repo. Those are open questions. The statement being made is that this code shouldn't live in TomEE as a library or module or separate git repo where it could be mistaken as being a component that doesn't work outside of an app server and instead should be in Geronimo and called geronimo-mp-jwt to avoid that misunderstanding. In terms of being reused in Geronimo, there's no server there anymore to reuse the code and the project is a bit of an abandoned building. Of the 66 people that have commit, only 3 are active. The statement being made that Geronimo as a project, not as a server, could hold all reusable app server components for all of the ASF and code from TomEE should be moved to Geronimo to help achieve that vision. One could argue that moving the code from an alive app server to a dead app server doesn't achieve the main objective of avoiding perception that code is not reusable. -David
