why is config not passed to wamplet?

#1

Hello,

I have followed the votegame example to have a WAMPlet run within the crossbar router.

The wamplet is discovered successfully:

2015-09-25T10:34:45+0300 [Controller 27654] Detected 1 WAMPlets in environment:
2015-09-25T10:34:45+0300 [Controller 27654] WAMPlet twiliosms-wamplet.twiliosms

I’ve also confirmed that the WAMPlet factory (equivalent of the “make” function in the example) is called is when crossbar starts.

However, the factory is passed an empty config (None value), despite the following crossbar config:

components:
- dist: “twiliosms_wamplet”
type: “wamplet”
entry: “twiliosms”
extra:
twilio-account: “”
twilio-token: “”

Any clue as to why the config passed to the factory is None???

Thanks!

0 Likes

#2

Here’s the entry point:

  entry_points={

        'autobahn.twisted.wamplet': [

            'twiliosms = twiliosms_wamplet:app'

        ],

  },

perjantai 25. syyskuuta 2015 10.44.30 UTC+3 pe...@koodaamo.fi kirjoitti:

···

Hello,

I have followed the votegame example to have a WAMPlet run within the crossbar router.

The wamplet is discovered successfully:

2015-09-25T10:34:45+0300 [Controller 27654] Detected 1 WAMPlets in environment:
2015-09-25T10:34:45+0300 [Controller 27654] WAMPlet twiliosms-wamplet.twiliosms

I’ve also confirmed that the WAMPlet factory (equivalent of the “make” function in the example) is called is when crossbar starts.

However, the factory is passed an empty config (None value), despite the following crossbar config:

components:
- dist: “twiliosms_wamplet”
type: “wamplet”
entry: “twiliosms”
extra:
twilio-account: “”
twilio-token: “”

Any clue as to why the config passed to the factory is None???

Thanks!

0 Likes

#3

Hello!

The example you’re using is quite old, and anything in the “work” directory there is alpha/has some unresolved issues.

What version of Crossbar are you using? With current versions the validity check of the configuration should already fail. You can find the current (somewhat brief) documentation at http://crossbar.io/docs/Router-Components/

So: make sure that you’re using current Crossbar and have updated your config to work with this. Please let me know how this goes, and we can look into this in more detail.

Regards,

Alex

···

Am Freitag, 25. September 2015 09:46:47 UTC+2 schrieb pe...@koodaamo.fi:

Here’s the entry point:

  entry_points={
      'autobahn.twisted.wamplet': [
          'twiliosms = twiliosms_wamplet:app'
      ],
  },

perjantai 25. syyskuuta 2015 10.44.30 UTC+3 pe...@koodaamo.fi kirjoitti:

Hello,

I have followed the votegame example to have a WAMPlet run within the crossbar router.

The wamplet is discovered successfully:

2015-09-25T10:34:45+0300 [Controller 27654] Detected 1 WAMPlets in environment:
2015-09-25T10:34:45+0300 [Controller 27654] WAMPlet twiliosms-wamplet.twiliosms

I’ve also confirmed that the WAMPlet factory (equivalent of the “make” function in the example) is called is when crossbar starts.

However, the factory is passed an empty config (None value), despite the following crossbar config:

components:
- dist: “twiliosms_wamplet”
type: “wamplet”
entry: “twiliosms”
extra:
twilio-account: “”
twilio-token: “”

Any clue as to why the config passed to the factory is None???

Thanks!

0 Likes

#4

Using newest released crossbar. I think I must’ve been mixing old and new syntax in config.yaml because I now used my working config and switched it to wamplet config (using the “package” and “entrypoint” keys) and lo and behold it worked :slight_smile:

Thanks,

Petri

perjantai 25. syyskuuta 2015 14.12.38 UTC+3 Alexander Gödde kirjoitti:

···

Hello!

The example you’re using is quite old, and anything in the “work” directory there is alpha/has some unresolved issues.

What version of Crossbar are you using? With current versions the validity check of the configuration should already fail. You can find the current (somewhat brief) documentation at http://crossbar.io/docs/Router-Components/

So: make sure that you’re using current Crossbar and have updated your config to work with this. Please let me know how this goes, and we can look into this in more detail.

Regards,

Alex

Am Freitag, 25. September 2015 09:46:47 UTC+2 schrieb pe...@koodaamo.fi:

Here’s the entry point:

  entry_points={
      'autobahn.twisted.wamplet': [
          'twiliosms = twiliosms_wamplet:app'
      ],
  },

perjantai 25. syyskuuta 2015 10.44.30 UTC+3 pe...@koodaamo.fi kirjoitti:

Hello,

I have followed the votegame example to have a WAMPlet run within the crossbar router.

The wamplet is discovered successfully:

2015-09-25T10:34:45+0300 [Controller 27654] Detected 1 WAMPlets in environment:
2015-09-25T10:34:45+0300 [Controller 27654] WAMPlet twiliosms-wamplet.twiliosms

I’ve also confirmed that the WAMPlet factory (equivalent of the “make” function in the example) is called is when crossbar starts.

However, the factory is passed an empty config (None value), despite the following crossbar config:

components:
- dist: “twiliosms_wamplet”
type: “wamplet”
entry: “twiliosms”
extra:
twilio-account: “”
twilio-token: “”

Any clue as to why the config passed to the factory is None???

Thanks!

0 Likes