Skip to content

Conversation

@shishir-lab
Copy link

As discussed on #196 , the issue #141 is resolved by sending deployment options with isolated classes in the app config.
With this approach, the modules/services should pass additional appConfig as shown below if the module/service has issue related with class not found.

{
          "metadata": {
            "group_id": "com.nubeiot.edge.module",
            "artifact_id": "jdbc",
            "version": "1.0.0-SNAPSHOT",
            "service_name": "edge-jdbc-demo"
          },
          "appConfig": {
            "__deploy__": {
              "isolatedClasses": [
                "io.vertx.ext.jdbc.*"
              ]
            },
.... // other app configs
          }
 }

…h and isolated classpath and used deployment options to resolve such cases.
@zero88
Copy link
Contributor

zero88 commented Jul 16, 2019

I have not yet had time to do review, but it is quite correct direction.
I will do review later next week.
So sorry for delay.

@zero88 zero88 force-pushed the master branch 2 times, most recently from f2047b4 to 68d3fa8 Compare February 6, 2021 21:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

C: bios Issue related to BIOS C: edge T: Bug Issue Type: Bug

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants