I got rid of it by adding in the metatype bundle. I'll go have a look and see if the level could be turned down to 'info'.
On Sat, Oct 8, 2016 at 11:58 PM, David Jencks <[email protected]> wrote: > It shouldn’t be error for sure. It just says the metatype spec classes > aren’t available so it can’t register the ManagedService that also implements > MetatypeProvider, so it’s just registering a ManagedService that doesn’t > implement MetatypeProvider. Does info level seem appropriate? > > thanks > david jencks > >> On Oct 7, 2016, at 7:30 AM, Benson Margulies <[email protected]> wrote: >> >> What is this about? I have DS and CM in my container. >> >> [java] ERROR: Cannot create MetaType providing ManagedService; >> not providing Metatype information but just accepting configuration >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
