ASM is a PITA, it is not backward compatible. IIRC Wildfly 8.1 uses ASM 3 for hibernate and in CXF for some JAXB annotations so as long as you do not use this in your web app classpath it seems doable from within Wildfly, but you get the deployment errors.
As said, my preference would be to drop MVEL from ES. Just use an ES TransportClient from within Widlfly. In that case there is no longer the need for a script language. I suggest not to create a full ES node in a web app container, this has other downsides (think of heap memory). Then you can exclude MVEL and ASM from ES jars safely, and most other dependencies too, just keep the ES jar and Lucene core jar with the query builders, this is enough for TransportClient. Jörg On Sat, Jul 26, 2014 at 3:44 AM, John D. Ament <[email protected]> wrote: > I can try upgrading ASM locally to see if it works. I'm assuming it's > backwards compatible? > > > On Friday, July 25, 2014 3:06:13 AM UTC-4, Jörg Prante wrote: > >> As a side note, I run Wildfly 8.1 on Java 8. ASM 3 does not work with >> Java 8, so I wonder how things can work out at all, even without ES. If >> possible, ASM 3 should be replaced by ASM 5.0 >> >> Jörg >> >> >> On Fri, Jul 25, 2014 at 9:02 AM, [email protected] <[email protected]> >> wrote: >> >>> You have two choices: >>> >>> - drop ASM and MVEL, switch to Groovy for scripting >>> >>> - use TransportClient to avoid ES-cluster-side services like scripting >>> in Wildfly deployment (this is how I do it currently) >>> >>> Jörg >>> >>> >>> On Fri, Jul 25, 2014 at 3:30 AM, John D. Ament <[email protected]> >>> wrote: >>> >>>> Hi all >>>> >>>> I was tinkering a bit with ElasticSearch. I think my target runtime >>>> may end up being embedded, just based on our deployment model. Probably >>>> not a big deal to get multiple nodes talking to each other and no >>>> additional hardware to deploy. >>>> >>>> I was trying to start the application in WildFly 8.1. When I go to >>>> deploy, I get errors related to ASM. It turns out that ES 1.3 ships w/ ASM >>>> 4.1. WildFly uses ASM 3.3.1. Is it possible to run ES against this >>>> version of ASM? It would seem that the two versions not compatible. >>>> >>>> If there's an alternative to running it on WF 8.1, I would love to hear >>>> it. >>>> >>>> Thanks, >>>> >>>> John >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "elasticsearch" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected]. >>>> >>>> To view this discussion on the web visit https://groups.google.com/d/ >>>> msgid/elasticsearch/4908b733-babc-41bf-a87f-39ebfaea1f94% >>>> 40googlegroups.com >>>> <https://groups.google.com/d/msgid/elasticsearch/4908b733-babc-41bf-a87f-39ebfaea1f94%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> >> -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/6856b6aa-bfa5-42de-8922-8be6d57a3221%40googlegroups.com > <https://groups.google.com/d/msgid/elasticsearch/6856b6aa-bfa5-42de-8922-8be6d57a3221%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAKdsXoET2XhnoQkt4s%3DsTp%3DG8UjQnBHgFwZpFcxoj1wQK%3DUm_w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
