Re: [keycloak-dev] is UserManager really unused?

From: "Bill Burke" <bburke(a)redhat.com&gt; To: "Stian Thorgersen" <stian(a)redhat.com&gt; 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?

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.

On 11/20/2013 12:38 PM, Stian Thorgersen wrote: > I would really like it if we could use Keycloak in LiveOak without > requiring dependencies on Resteasy/JAX-RS. So if we could separate out all > business logic from JAX-RS code, including OAuth logic, that would be > great. > > The sooner we could have this the better. At the moment we're starting an > embedded Undertow server on LiveOak for Keycloak, which is far from ideal. > Using Netty would be less than elegant as well, as LiveOak provides it's > own layer to create restful services. > > We don't have to do it before M1, but if we could do it after M1 that would > be great. I'd be more than happy to do the legwork if you want. > > ----- Original Message ----- >> From: "Bill Burke" <bburke(a)redhat.com&gt; >> To: keycloak-dev(a)lists.jboss.org >> Sent: Wednesday, 20 November, 2013 2:13:12 PM >> Subject: Re: [keycloak-dev] is UserManager really unused? >> >> I forget what I was going to use it for, but I guess we can ditch it for >> now. I don't know if you've noticed but, I've been trying to separate >> JAX-RS code from Business Logic from Storage logic. Thus the >> Resource/Manager/Model splits. Hopefully the end result can be an API >> that can be used programmatically. There's still a lot of thought and >> refactoring to do here. >> >> On 11/19/2013 11:53 AM, Viliam Rockai wrote: >>> Hey, >>> >>> Could the class org.keycloak.services.managers.UserManager be safely >>> deleted? >>> >>> It doesn't seem to be used anymore and if I delete it, tests are >>> passing. Just wanted to be sure if someone doesn't have any intentions >>> with it anymore. >>> >>> Thanks, >>> >>> Viliam >>> _______________________________________________ >>> 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 >> _______________________________________________ >> 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