search

fabric8io / fabric8-forge

Supports JBoss Forge plugins for the Fabric8 iPaaS along with using Forge as a REST service inside Fabric8 DevOps
Apache License 2.0
11 stars 21 forks source link

ipaas-search-connectors seems to cache results #690

Closed gashcrumb closed 7 years ago

gashcrumb commented 8 years ago

Could be maven causing this. But basically:

1) Call ipaas-search-connectors 2) upload a new connector jar to nexus 3) Call ipaas-search-connectors again

only the connectors you got back for step 1 are returned. I can only get my newly uploaded connector to show up if I kill the fabric8-forge pod and let it get restarted.

davsclaus commented 8 years ago

There is a background thread the re-index the nexus repo and runs every 60 second. https://github.com/fabric8io/django/blob/master/addons/ipaas/src/main/java/io/fabric8/forge/ipaas/repository/NexusConnectionRepository.java#L52

davsclaus commented 7 years ago

Yeah let me see if forge don't detect that CDI bean and starts it (CDI is lovely)

davsclaus commented 7 years ago

So you need to run one of the django commands first to have that background thread start up. I guess forge dont scan CDI beans or something. Will try with some EjbStartup annotations

davsclaus commented 7 years ago

Okay the new forge release starts the indexer on startup.

You need to name the artifactId of the connector with -connector as suffix. The wizard do not enforce that as its a wizard OOTB from jboss forge (project-new) which we cannot control.