Go on the next e4 .9 review blogging.
One thing worried by me is that, in the JS framework diagram, one flow "e4 JS->Rhino->JVM" pass by the OSGI framework. It is a smell in the aspect of security. Because the OSGI is a thin modular layer on the JVM to some extent. I can not figure out why this design is a must.(Rhino problem?)
After quickly sources reviewing yesterday, I find that it is possible to uncover the tip of the iceberg. Maybe there are many potential contributors to take part in the evolvement of the e4 language support.
manifest.json, note the name "Activator" should match with the constructor function in test.js(test0.js here is a bug-like script I found accidently, it seem a rhino bug. However, more dependencies cause more security problem...)
add "-console" arguments, and set the "auto-start" into true if you want to get the same screenshots below(orz, you can do it by hand)
the content of test.js(not use the rhino "print", you should borrow the "println" from Java), and we get the "Hello..." when start osgi(yeah, all wanted-to-be-started bundles will be started)
we get the "Goodbye..." when stop osgi(yeah,all started bundles will be stopped)