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/CAKdsXoEojjJwhaBqvGOTErptw10%2BN8TX0fhenUam%2Bq1U9859cw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
