[keycloak-dev] Release next Monday or Tuesday

[Stian Thorgersen]

----- Original Message -----
> From: "Stian Thorgersen" <stian at redhat.com>
> To: "Bill Burke" <bburke at redhat.com>
> Cc: keycloak-dev at lists.jboss.org
> Sent: Friday, 10 January, 2014 4:52:50 PM
> Subject: Re: [keycloak-dev] Release next Monday or Tuesday
> 
> 
> 
> ----- Original Message -----
> > From: "Bill Burke" <bburke at redhat.com>
> > To: "Stian Thorgersen" <stian at redhat.com>
> > Cc: keycloak-dev at lists.jboss.org
> > Sent: Friday, 10 January, 2014 4:34:01 PM
> > Subject: Re: [keycloak-dev] Release next Monday or Tuesday
> > 
> > 
> > 
> > On 1/10/2014 9:43 AM, Stian Thorgersen wrote:
> > >
> > >
> > > ----- Original Message -----
> > >> From: "Bill Burke" <bburke at redhat.com>
> > >> To: "Stian Thorgersen" <stian at redhat.com>
> > >> Cc: keycloak-dev at lists.jboss.org
> > >> Sent: Friday, 10 January, 2014 2:30:47 PM
> > >> Subject: Re: [keycloak-dev] Release next Monday or Tuesday
> > >>
> > >> I'm fine with this as long as no further things pop up.  This is an
> > >> alpha release and so long as it is functional, we're good.
> > >
> > > Sure, I can sort out the issues I listed, except it would be good if you
> > > could have a look at https://issues.jboss.org/browse/KEYCLOAK-256.
> > >
> > >>
> > >> I'm not sure about the JSF example addition.  I want all the examples to
> > >> work off of the appliance (and pre-configured as marek suggested), and
> > >> the appliance will be trimmed down to remove CDI/JSF in the future.
> > >> People don't use JSP anymore, but so what?  The examples are very
> > >> minimal on purpose because they focus on keycloak.  But, I've always
> > >> wanted nice example applications in addition to these simple examples
> > >> (like event juggler) so users can also see other technologies
> > >> interacting with keycloak.
> > >
> > > Makes sense. Just one question though, once the WildFly subsystem is
> > > ready,
> > > wouldn't the trimmed down appliance also not have support for
> > > JavaEE/deployments altogether? I think it makes sense to have two options
> > > for Keycloak (embedded in a fully functional WildFly/EAP, and a
> > > standalone
> > > that doesn't allow deployments of any sort).
> > >
> > 
> > We need support for:
> > 
> > jca/jta - jdbc connection pool
> > JPA
> > Servlet
> > 
> > JAX-RS/Jackson comes bundled with keycloak war.
> > 
> > Not sure yet how we'll deal with clustering yet,no there may be some
> > other pieces we need.  I'm pretty sure there's something interesting
> > things we can do with the Wildfly Domain Controller to make clustering
> > really nice.
> > 
> > IMO, if users want something different than the appliance, then they
> > have to download and install the war distribution themselves.  So, only
> > one appliance download IMO.  Two many options is confusing.
> > 
> 
> Sure - my point was that I don't think a trimmed down standalone appliance
> shouldn't support JavaEE deployments (i.e. standalone/deployments and
> hot-deployment stuff is ripped out) so wouldn't matter if examples are JSP
> or JSF.

Hmm... let me rewrite that! A slimmed down standalone Keycloak appliance should not support JavaEE deployments. It should be a pure auth server, not a JavaEE application server as well (if you want that deploy auth-server.war to a standard wildfly server).

> 
> > Bill
> > 
> > --
> > 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
>