6:57 a.m.
Currently Keycloak runs on Undertow and relies heavily on Resteasy. This doesn't work
for the LiveOak project in the long run.
After M1 I would like to create a Keycloak core that doesn't depend on Undertow or
Resteasy. This should provide most of the logic except for wiring-up endpoints. For
WildFly/EAP I would assume we'd provide endpoints using Undertow/Resteasy. Those would
live in the Keycloak project. Then me and Marek will provide endpoints using Liveoak,
these would live in the Liveoak project.
Further, for some dependencies I'd also like to make these pluggable. For example http
client and json processing. Not sure what libraries would be required, but I basically
don't want to bring in yet-another-library if one exists in Liveoak that can do the
job.
In summary what I want to do is to make sure Keycloak can be run on both WildFly/EAP and
LiveOak and at the same time:
* Share as much as possible of the code
* Implement REST endpoints in Liveoak with the minimum amount of code
* Reduce the amount of dependencies Keycloak introduces in Liveoak
7:52 a.m.
Do what you want, but I think its silly to not just adapt LiveOak to use
Resteasy/JAX-RS. If LiveOak supports BIO/Streams, it would be easy to
adapt Resteasy to run in that environment. Its already been done for
Netty 3 and 4, JDK HTTP, and even Grizzly.
On 12/14/2013 7:57 AM, Stian Thorgersen wrote:
Currently Keycloak runs on Undertow and relies heavily on Resteasy.
This doesn't work for the LiveOak project in the long run.
After M1 I would like to create a Keycloak core that doesn't depend on Undertow or
Resteasy. This should provide most of the logic except for wiring-up endpoints. For
WildFly/EAP I would assume we'd provide endpoints using Undertow/Resteasy. Those would
live in the Keycloak project. Then me and Marek will provide endpoints using Liveoak,
these would live in the Liveoak project.
Further, for some dependencies I'd also like to make these pluggable. For example
http client and json processing. Not sure what libraries would be required, but I
basically don't want to bring in yet-another-library if one exists in Liveoak that can
do the job.
In summary what I want to do is to make sure Keycloak can be run on both WildFly/EAP and
LiveOak and at the same time:
* Share as much as possible of the code
* Implement REST endpoints in Liveoak with the minimum amount of code
* Reduce the amount of dependencies Keycloak introduces in Liveoak
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
8:09 a.m.
On 12/16/2013 8:52 AM, Bill Burke wrote:
Do what you want, but I think its silly to not just adapt LiveOak to
use
Resteasy/JAX-RS. If LiveOak supports BIO/Streams, it would be easy to
adapt Resteasy to run in that environment. Its already been done for
Netty 3 and 4, JDK HTTP, and even Grizzly.
That being said, the code does need refactoring to get the bits that
aren't JAX-RS specific into a Java API that could be used.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
11:41 a.m.
Resteasy/JAX-RS on LiveOak makes as much sense as margarine on butter. LiveOak is a
container for REST resources and doesn't provide direct access to BIO/Streams.
----- Original Message -----
From: "Bill Burke" <bburke(a)redhat.com>
To: keycloak-dev(a)lists.jboss.org
Sent: Monday, 16 December, 2013 2:09:53 PM
Subject: Re: [keycloak-dev] Keycloak server environments
On 12/16/2013 8:52 AM, Bill Burke wrote:
> Do what you want, but I think its silly to not just adapt LiveOak to use
> Resteasy/JAX-RS. If LiveOak supports BIO/Streams, it would be easy to
> adapt Resteasy to run in that environment. Its already been done for
> Netty 3 and 4, JDK HTTP, and even Grizzly.
>
That being said, the code does need refactoring to get the bits that
aren't JAX-RS specific into a Java API that could be used.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev
11:57 a.m.
Again, create extra work for yourself if you want to...But if LiveOak is
using Netty or Undertow, no reason JAX-RS can't be plugged in. Its
funny how Vert.x can place so much importance on polyglot, yet can't
support a simple REST framework.
On 12/18/2013 12:41 PM, Stian Thorgersen wrote:
Resteasy/JAX-RS on LiveOak makes as much sense as margarine on
butter. LiveOak is a container for REST resources and doesn't provide direct access to
BIO/Streams.
----- Original Message -----
> From: "Bill Burke" <bburke(a)redhat.com>
> To: keycloak-dev(a)lists.jboss.org
> Sent: Monday, 16 December, 2013 2:09:53 PM
> Subject: Re: [keycloak-dev] Keycloak server environments
>
>
>
> On 12/16/2013 8:52 AM, Bill Burke wrote:
>> Do what you want, but I think its silly to not just adapt LiveOak to use
>> Resteasy/JAX-RS. If LiveOak supports BIO/Streams, it would be easy to
>> adapt Resteasy to run in that environment. Its already been done for
>> Netty 3 and 4, JDK HTTP, and even Grizzly.
>>
>
> That being said, the code does need refactoring to get the bits that
> aren't JAX-RS specific into a Java API that could be used.
>
>
> --
> Bill Burke
> JBoss, a division of Red Hat
> http://bill.burkecentral.com
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/keycloak-dev
>
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
4026
days inactive
4030
days old
4 comments
2 participants
participants (2)
-
Bill Burke -
Stian Thorgersen