Hi, Thank you for the feedback.
We actually had to remove MP from Plus and Plume because we found some other issues. See here: https://jira.apache.org/jira/browse/TOMEE-2407 <https://jira.apache.org/jira/browse/TOMEE-2407> It is possible to disable it, but I don’t think it is possible to enable it per application. Is this is something that you would like to add, please add a sub-task issue in https://jira.apache.org/jira/browse/TOMEE-2407 <https://jira.apache.org/jira/browse/TOMEE-2407> Cheers, Roberto > On 31 Dec 2018, at 11:19, j4fm <james.m...@my-managed.net> wrote: > > Hi, I tested with the last TomEE Plus snapshot which had MP in it and #304 > below. Apart from having to add a line to exclusions.list for one item, it > seems to work fine. Without the exclusions.list entry, I get the following > because @Provider is being used in our class (think this could be removed > though): > > “at java.base/java.lang.Class.newInstance(Class.java:571) > at > org.apache.openejb.server.cxf.rs.CxfRsHttpListener.newProvider(CxfRsHttpListener.java:528) > at > org.apache.openejb.server.cxf.rs.CxfRsHttpListener.providers(CxfRsHttpListener.java:463) > at > org.apache.openejb.server.cxf.rs.CxfRsHttpListener.configureFactory(CxfRsHttpListener.java:1012) > at > org.apache.openejb.server.cxf.rs.CxfRsHttpListener.deployApplication(CxfRsHttpListener.java:579)” > > > Is having MP scanning disabled by default and enabling it on a > per-application basis possible? > > Thank you > > > > > -- > Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
