(Some) Triggers are created without context.resourcePath

It may happen that some JVM/GC/Deployment/Datasources triggers are created without context.resourcePath property, which is necessary for the UI (and possibly something else).

It happens because at the time of trigger creation the var being used (this.$rootScope.resourcePath) might not have been initialized yet (it is a result of a REST call) and thus not being passed.