[keycloak-dev] next release: refactoring

[Stian Thorgersen]

As part of creating a non JavaEE dependent core I think we should extract code into reusable modules. All modules should have an SPI and be replaceable if needed. Without to much consideration I could imagine modules such as:

* OAuth2
* Model
* Forms (login, registration)
* Account Management
* URLs (URLs to everything)
* Admin?

For the main distribution there would also be:

* JAX-RS services
* WildFly sub-system

I think re-working things into reusable modules will solve a lot of the pain points in the code, as well as allow us to integrate Keycloak properly with LiveOak.

----- Original Message -----
> From: "Bill Burke" <bburke at redhat.com>
> To: keycloak-dev at lists.jboss.org
> Sent: Tuesday, 14 January, 2014 9:06:48 PM
> Subject: [keycloak-dev] next release: refactoring
> 
> After Alpha 1, I'd like to focus on refactoring and improving the
> overall code quality.  For example, it has been brutally painful to
> change URI schemes from /auth-server to /auth and also using Realm name
> instead of id to generate URLs.  This is a problem in both the admin
> console and services.  I'm sure there's other areas too.
> 
> --
> Bill Burke
> JBoss, a division of Red Hat
> http://bill.burkecentral.com
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/keycloak-dev
>