[
https://issues.apache.org/jira/browse/NIFIREG-192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16575009#comment-16575009
]
ASF GitHub Bot commented on NIFIREG-192:
----------------------------------------
Github user kevdoran commented on a diff in the pull request:
https://github.com/apache/nifi-registry/pull/134#discussion_r208977230
--- Diff:
nifi-registry-web-api/src/main/java/org/apache/nifi/registry/web/NiFiRegistryResourceConfig.java
---
@@ -44,6 +48,14 @@
private static final Logger logger =
LoggerFactory.getLogger(NiFiRegistryResourceConfig.class);
+ @Autowired
+ private StandardProviderFactory standardProviderFactory;
+
+ @Bean
+ public EventService eventService() {
--- End diff --
I don't think this is required because `EventService` is already annotated
with `@Service`, so it will be created as a bean by component scanning.
> Create/Add REGISTRY_START event that fires when the NiFi Registry initially
> starts
> ----------------------------------------------------------------------------------
>
> Key: NIFIREG-192
> URL: https://issues.apache.org/jira/browse/NIFIREG-192
> Project: NiFi Registry
> Issue Type: New Feature
> Reporter: Jeremy Dyer
> Assignee: Jeremy Dyer
> Priority: Major
> Fix For: 0.3.0
>
>
> Having an event that fires when the NiFi Registry starts would provide a
> great place for bootstrapping the registry with any sort of setup, importing,
> repairing type tasks that need to occur before the registry starts serving
> clients.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
