I deploy the adapter by overlaying/copying the adapter modules into my
Wildfly.
I understand that you support older Wildfly versions too, but I guess
you have to create a separate adapter for Wildfly 10 then.
You can easily see that there are incompatibilities between Undertow
1.2.x and 1.3.x which will result in a failed compilation if you change
the Undertow version in the parent pom for testing purposes.
Regards,
Christian
Am 21.01.2016 um 14:44 schrieb Stian Thorgersen:
BTW we support older versions of WildFly as well as 10, so it's
not as
simple as upgrading the undertow version
On 21 January 2016 at 14:43, Stian Thorgersen <sthorger(a)redhat.com
<mailto:sthorger@redhat.com>> wrote:
How are you deploying the adapter and what adapter are you using?
We have tested the adapter with WildFly 10 (Keycloak 1.8.0.CR1 was
tested on 10.0.0.CR5) and it worked fine.
On 21 January 2016 at 14:30, Christian Beikov
<christian.beikov(a)gmail.com <mailto:christian.beikov@gmail.com>>
wrote:
Hello,
I am trying to deploy Keycloak 1.8.0.CR1 to Wildfly 10.0.0.CR4
but there
are some problems with that.
You are compiling against Undertow 1.1.1.Final but Wildfly
10.0.0.CR4
comes with 1.3.3.Final and there are some binary
incompatibilities in
io.undertow.server.Connectors of which
org.keycloak.adapters.undertow.SavedRequest is affected.
You are using io.undertow.util.ImmediatePooled instead of the
expected
type io.undertow.connector.PooledByteBuffer which leads to
method not
found exceptions.
I suggest you update the undertow version in the parent
pom.xml to make
sure everything is binary compatible if you are going to
support Wildfly
10 as you announced.
Regards,
Christian
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org <mailto:keycloak-dev@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/keycloak-dev