[keycloak-dev] public/private api module structure
Bill Burke
bburke at redhat.com
Wed Aug 12 08:50:49 EDT 2015
I was thinking we'd have a more course-grain module structure for public
apis. We have a crap load of SPIs and having a module for each of them
is a pain for the user and us in creating/maintaining poms as well as
creating maintaing JBoss modules. Something like:
keycloak-core-api
keycloak-server-api
keycloak-client-api
and
keycloak-saml-api
keycloak-oidc-api
protocol APIs would be for the case where users need to access the raw
SAML document or JWT.
These API modules would only contain public APIs and helper classes. we
can consolidate and/or separate internal implementation classes into any
structure we want with the thought process being that we would organize
these modules so that we have the option to remove features as needed to
make a smaller distro.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
More information about the keycloak-dev
mailing list