This version (2017/05/27 13:44) is a draft.
Approvals: 0/1

[09:16:51] * ChanServ sets mode: +o temporalfox [10:18:16] * ChanServ sets mode: +o temporalfox

[12:30:38] <temporalfox> pmlopes hi

[12:30:48] <pmlopes> hi

[12:30:55] <temporalfox> I have done some javascript in vertx shell

[12:31:01] <temporalfox> would you mind to throw an eye at it :-) ?

[12:31:10] <pmlopes> sure

[12:31:17] <pmlopes> do you have a pr id?

[12:31:21] <temporalfox> not yet a PR

[12:31:24] <temporalfox> rather a branch

[12:31:32] <temporalfox> it is web-shell branch of vertx shell

[12:31:37] <temporalfox> there is a vertxshell.js

[12:31:46] <temporalfox> also you can have a look at everything if you like

[12:31:55] <temporalfox> it uses Router and SockJS

[12:31:56] <temporalfox> so perhaps I'm doing wrong things

[12:32:10] <temporalfox> that's the branch

[12:32:10] <temporalfox>

[12:33:40] <temporalfox> in particular I don't really do the “module” thing for client

[12:33:41] <temporalfox> and I prefer to ask you to do whatever is the thing to do to provide the best client side support

[12:33:41] <temporalfox> the main script is

[12:33:42] <temporalfox>

[12:33:42] <temporalfox> and the default html page for serving it is

[12:33:42] <temporalfox>

[12:33:43] <temporalfox> there is not really much

[12:33:55] <temporalfox> I mean it's failrly straightforward and simple javascript

[12:37:54] <pmlopes> ok, i'll check

[12:38:40] <temporalfox> thanks very much

[13:09:10] <pmlopes> i'm looking at the Js code and i think you should follow the same loader code as in the eventbus-client if you do that than it is known to work with browser, node, webpack, amd and commonjs

[13:11:01] <pmlopes> in the html file you can replace “location.hostname + (location.port ? ':' + location.port : '')” with just “” will include the port if not the standard, so if you're using something else than 80 then it will be properly appended for you

[13:48:44] <aesteve> hi guys :) am I missing something, or do message headers are not readable from javascript vertxbus client ?

[13:53:05] <aesteve>

[13:53:37] <aesteve> json doesn't seem to contain an 'headers' node

[14:36:27] <temporalfox> pmlopes the term.js dependency how is that supposed to be consumed with modules ?

[14:37:47] <pmlopes> @aesteve a fix from server → client has been merged a few days ago, can you test with latest git?

[14:38:49] <pmlopes> if you're using a module loader then you should load it according to the module loader way if you're just doing simple stuff, by adding a <script> tag to your html will make the term available in the global scope (the defaul for javascript)

[14:39:09] <pmlopes> sorry, last message was for @temporalfox

[14:39:45] <temporalfox> ah so you mean the SockJS dependency ?

[14:39:55] <temporalfox> sockjs-client is from NPM ?

[14:43:45] <aesteve> thx pmlopes ! I'll try it later

[14:44:25] <aesteve> it's not a big deal actually, I marshalled headers within the payload as a workaround

[17:17:53] * ChanServ sets mode: +o temporalfox [20:50:56] * ChanServ sets mode: +o temporalfox

[21:10:50] <kibibyte> hi

[21:10:52] <kibibyte> need help

[21:11:24] <kibibyte> how to share lock localmap in verticle method

[21:11:30] <kibibyte> errr

[21:11:37] <kibibyte> how to lock localmap in verticle method

[21:12:38] <kibibyte> what i mean i want to do some operation like : check if item quantity is ok, if yes update it etc. and i have severall verticles which operate on localmap

[23:58:55] <junster> Hi all, does anyone here have much experience with using Vert.x embedded in an OSGi application? I'm having some issues on shutdown with java.lang.NoClassDefFoundError errors. It seems like even after vertx.close's handler is called netty is still doing some work.

[23:59:04] <junster> I know that vertx.close is async so I tried to make it a blocking call with a CountDownLatch, before I made that change the application would hang instead of shutting down on top of throwing the exception now it shuts down but still throws a the same exception just for a different class.