Hi Val, I think you are right but when we tried your suggestion, it brought our hibernate code down.
Thus, we drilled down and found a confllict betweem cache-api-1.0.0.jar and javaee-16.jar they have a conflict on javax.cache.event.CacheEntryEvent. class with the constructor method( both have different signatures). javaee-16.jar resides in resin/lib folder while cache-api-1.0.0.jar resides in our application code. We use Maven for dependency management. The class is getting loaded from javaee-16.jar and not the cache JAR. Thanks & Regards, Jitesh Dundas Phone - 732-357-6292 On Sat, Feb 27, 2016 at 12:29 PM, jitesh dundas <[email protected]> wrote: > Hi Val, > > We tried the suggestion but we still get the same error. > > Any other ideas? > > > Thanks & Regards, > Jitesh Dundas > > Phone - 732-357-6292 > > > > > On Thu, Feb 25, 2016 at 9:28 PM, jitesh dundas <[email protected]> wrote: > >> Hi, >> >> Thanks for the advise. I will surely try that. >> >> Thanks & Regards, >> Jitesh Dundas >> >> Phone - 732-357-6292 >> >> >> >> >> On Thu, Feb 25, 2016 at 6:40 PM, vkulichenko < >> [email protected]> wrote: >> >>> Hi Jitesh, >>> >>> This issue looks similar to [1] - Resin includes javaee-16.jar which >>> contains some outdated JCache spec classes. These classes override ones >>> provided by the application. Can you try the solution provided on SO to >>> reverse the class loading order? >>> >>> [1] >>> >>> http://stackoverflow.com/questions/29382856/how-to-classload-java-ee-7-in-resin-4-0-42-and-not-use-the-default-javaee-16-jar >>> >>> -Val >>> >>> >>> >>> -- >>> View this message in context: >>> http://apache-ignite-users.70518.x6.nabble.com/NoSuchMethod-Error-tp3193p3194.html >>> Sent from the Apache Ignite Users mailing list archive at Nabble.com. >>> >> >> >
