On 11/20/2013 1:58 PM, Stian Thorgersen wrote:
----- Original Message -----
> From: "Bill Burke" <bburke(a)redhat.com>
> To: "Stian Thorgersen" <stian(a)redhat.com>
> Cc: keycloak-dev(a)lists.jboss.org
> Sent: Wednesday, 20 November, 2013 6:52:06 PM
> Subject: Re: [keycloak-dev] is UserManager really unused?
>
> LiveOak is what?
The shiny new name for mbaas (or restafari which was the previous code-name)
>
> I've been thinking about removing Resteasy from at least the adapters.
> Patching AS7/EAP to use Resteasy 3.0.x might be a non-starter for some.
> But I'd have to use the JDK's client API java.net.URL, or Apache
> client. The latter also may have versioning problems between AS7/EAP6
> and Wildfly :(
>
> For server-side, I'd consider replacing JAX-RS if it can run under
> AS7/EAP6/Wildfly without any dependency conflicts and could run under a
> servlet container(for AS7/EAP6) or non-servlet Undertow(Wildfly).
> Otherwise, it doesn't make much sense to switch it out. For me, it all
> boils down to not requiring users to patch JAX-RS.
I wasn't talking about switching it out, but separating it into an optional module. I
need to run Keycloak in LiveOak, which doesn't have support for servlets or jax-rs.
This is why I'd like to be able to use the logic from Keycloak, but wire-up the
endpoints with LiveOak. This with the minimum amount of code specific to the
keycloak-liveoak integration.
I know you weren't talking about switching it out...But I am :)
Specifically because of dependency issues. Can REST processing for
LiveOak live in a Servlet 3.0 container?
Bill
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com