Oh Iiiii see, the Native context is basically transparent to Java (it's a,, don't worry your pretty little head about it
), just give CefMessageRouter.create() a CefMessageRouterConfig, I get it
I'm actually thinking if the Javascript itself can generate it's own CefMessageRouterHandlerAdapter(s) from its side by passing the Script to the CefMessageRouter (and using Apache/Mozilla Rhino) and so removing the 'complexed matters' from the (my) Browser wrapper class and making it all readily editable and refreshable from (on the next page load) in the HTML/JS... Hmm interesting...
Hokey