During the #start() #stop() method of a legacy SAR the naming context is read only. The problem seems to be that org.jboss.as.service.AbstractService.invokeLifecycleMethod(Method) only sets the thread context class loader and does not do WritableServiceBasedNamingStore.pushOwner. - change AbstractService#invokeLifecycleMethod to take an additional LifecycleContext argument - update CreateDestroyService to pass the context - update StartStopService to pass the context https://issues.jboss.org/browse/AS7-5584
…ot handle rollback
hosts running versions that cannot notify the master of ignored resources at registration time.
…en the manifest is unconfigured
…anagement model of EJB3 subsystem
…nition configProperties to handle concurrent adds.
* fix PATH attribute definitions for the 4 messaging path subresources * add default value for each messaging path (+ fix typo in the LocalDescriptions) * use this PATH attribute to resolve the model and marshall it in XML * fix the removal of messaging path service when the HornetQ server resource is removed (the default value was used instead of the resource name)
* move RELATIVE_TO attribute to MessagingPathHandlers and fix its definition (default value + restart all services flag) * use the attribute to resolve its value and marshall it as an XML attribute