2017-01-03 10:20 GMT+01:00 Dignesh <[email protected]>: > Okay. I will remove the custom loader. > > A last question. > As per the description in https://issues.apache.org/jira/browse/TOMEE-1851 > , > I should not see the issue of I add the below content in context.xml file > > Not really. This only control the parent-first/last behavior for not filtered classes. With jersey you likely need to force the loading of a set of filtered classes. This is controllable with forceSkip property but I think you can't set it from the configuration.
What I'd do: 1. test it in a plain webapp (no ear) and make it work with previously mentionned configurations 1. bis. if you have issues with 1. please share a maven project as mentionned with a tomee setup 2. move this configuration to ear, normally if you used global configuration it should work too, if not try adding back the WebAppFirstEarClassLoader Note that 1. will let you identify which classes need a particular loading (org.glassfish is likely just a part of the iceberg but actual classes are - as mentionned - probably com.sun.x. Until you do this work I fear you will just be in a try and fail process. Once these classes are identified you can configure tomee to make it working. > <Context> > <Loader className="org.apache.tomee.catalina.TomEEWebappLoader" > loaderClass="org.apache.tomee.catalina.WebAppFirstEarClassLoader" > forceSkip="com.company.fromparent.,org.apache.deltaspike" /> > </Context> > > But looks like it is not working. Is it something which is expected ? > > > > > -- > View this message in context: http://tomee-openejb.979440. > n4.nabble.com/Classloading-issues-integrating-Jersey-2- > 16-and-apache-tomee-plus-7-0-0-tp4678794p4680850.html > Sent from the TomEE Dev mailing list archive at Nabble.com. >
