Yes, the intention is that LiveOak doesn't require JEE container. We
started with pure netty container. Currently we deploy on WildFly for
several reasons, also because of KeyCloak. However we want to start
stripping it down as soon as WildFly Core is available.
Btw. LiveOak has a mailing list:
http://liveoak.io/community/
On 05/16/2014 09:41 AM, Stian Thorgersen wrote:
That's an open question at the moment, but I would be surprised
if
LiveOak itself starts using any JavaEE libraries. Currently, Keycloak
and AeroGear UPS are deployed separately (as WARs) on the same
WildFly instance.
In the future I would like to see both of those deployed as WildFly
extensions. I've in the past done WildFly extensions with JAX-RS and
Servlets, which worked quite well, but I don't think CDI would.
----- Original Message -----
> From: "Anil Saldhana" <Anil.Saldhana(a)redhat.com> To:
> keycloak-dev(a)lists.jboss.org Sent: Thursday, 15 May, 2014 11:21:29
> PM Subject: [keycloak-dev] LiveOak and JavaEE libraries
>
> Hi Stian, do you know what parts of JavaEE Web libraries, LiveOak
> does not want to use?
>
> Right now, I know LiveOak uses Jax-RS and WebSockets.
>
> Does it use CDI, Servlets?
>
> Regards, Anil _______________________________________________
> keycloak-dev mailing list keycloak-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/keycloak-dev
>
_______________________________________________ keycloak-dev mailing
list keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev
--
Bolesław Dawidowicz
JBoss Portal Platform Architect | GateIn Portal Project Lead