Re: Thanks for not deleting javaee.wildfly

2019-07-25 Thread ehsavoie
I have some stuff to finish first, sorry. I will have some hours next Wednesday to upgrade to WildFly 17. I can'(t just remove the DTDs which are from JBoss AS 4 time and whose schema hasn't been updated to ASL 2.0 Cheers Emmanuel -- Emmanuel Hugonnet http://www.ehsavoie.com http://twitter.

Re: Thanks for not deleting javaee.wildfly

2019-07-25 Thread ehsavoie
Which JDK version ? -- Emmanuel Hugonnet http://www.ehsavoie.com http://twitter.com/ehsavoie On Thu, Jul 25, 2019 at 12:37 PM Emilian Bold wrote: > ... and I think against wildfly-15.0.1.Final too. > > --emi > > On Thu, Jul 25, 2019 at 1:30 PM Emilian Bold > wrote: > > > > This happens

Re: Thanks for not deleting javaee.wildfly

2019-07-25 Thread Emilian Bold
... and I think against wildfly-15.0.1.Final too. --emi On Thu, Jul 25, 2019 at 1:30 PM Emilian Bold wrote: > > This happens against Wildfly-16.0.0.Final > > --emi > > > On Wed, Jul 24, 2019 at 12:26 PM ehsavoie wrote: > > > > I'll take a look once on my laptop. The plugin uses Wildfly jars dir

Re: Thanks for not deleting javaee.wildfly

2019-07-25 Thread Emilian Bold
This happens against Wildfly-16.0.0.Final --emi On Wed, Jul 24, 2019 at 12:26 PM ehsavoie wrote: > > I'll take a look once on my laptop. The plugin uses Wildfly jars directly. > Which version of Wildfly are you using ? > > > Le mer. 24 juil. 2019 à 08:46, Emilian Bold a > écrit : > > > @ Emman

Re: Thanks for not deleting javaee.wildfly

2019-07-24 Thread ehsavoie
I'll take a look once on my laptop. The plugin uses Wildfly jars directly. Which version of Wildfly are you using ? Le mer. 24 juil. 2019 à 08:46, Emilian Bold a écrit : > @ Emmanuel: are you working someplace on the Wildfly module? > > I'm seeing some error reports about WildFly: > > XNIO00100

Re: Thanks for not deleting javaee.wildfly

2019-07-23 Thread Emilian Bold
@ Emmanuel: are you working someplace on the Wildfly module? I'm seeing some error reports about WildFly: XNIO001003: Running IoFuture notifier org.jboss.remoting3.remote.HttpUpgradeConnectionProvider$1@45dcf24e failed java.util.concurrent.RejectedExecutionException: Endpoint is not open at org.j

Re: Thanks for not deleting javaee.wildfly

2019-07-15 Thread Emilian Bold
Are you doing this in the release111 branch or on master? Having on release111 would be convenient... --emi On Mon, Jul 15, 2019 at 11:43 AM ehsavoie wrote: > > Hello, > I'm working into updating the schemas in the contrib part. > Currently I'm trying to remove the old DTDs to have only ASL 2.0

Re: Thanks for not deleting javaee.wildfly

2019-07-15 Thread Geertjan Wielenga
Excellent, the WildFly support will be requested a lot as soon as we announce Payara -- I've seen questions about this already. Gj On Mon, Jul 15, 2019 at 10:43 AM ehsavoie wrote: > Hello, > I'm working into updating the schemas in the contrib part. > Currently I'm trying to remove the old DTDs

Re: Thanks for not deleting javaee.wildfly

2019-07-15 Thread ehsavoie
Hello, I'm working into updating the schemas in the contrib part. Currently I'm trying to remove the old DTDs to have only ASL 2.0 schemas. It should be useable in 11.1 as it builds currently but can't be included afaik directly. Cheers, Emmanuel -- Emmanuel Hugonnet http://www.ehsavoie.com

Thanks for not deleting javaee.wildfly

2019-07-13 Thread Emilian Bold
Hello, I see that initially javaee.wildfly was just removed from cluster.properties but it was still in place. It was easy to re-add. Now it has been moved to contrib. This is still OK as at least the code is in the repository. We should probably do the same for beansbinding and some other modul