This shows the version was 1.2.1, so we're safe, i.e., no issue with EAP. Thanks.
I am still having the same exception when I have a SOAPProcessor action in my service tag within my jboss-esb.xmlKindly suggest on a workaround.