New candidate JEP: 335: Deprecate the Nashorn JavaScript Engine (original) (raw)
Luigi Dell'Aquila luigi.dellaquila at gmail.com
Thu Jun 7 07:48:03 UTC 2018
- Previous message: New candidate JEP: 335: Deprecate the Nashorn JavaScript Engine
- Next message: New candidate JEP: 335: Deprecate the Nashorn JavaScript Engine
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi,
Same here, OrientDB stored procedures (we refer to them as functions) are executed using Nashorn. We also supported Rhino in the past, so as long as we have an alternative it should not be a big issue. Anyway, having more precise information about the replacement will help a lot
Thanks
Luigi
2018-06-07 9:20 GMT+02:00 Michael Vitz <vitz.michael at googlemail.com>:
Hi,
some of my colleagues and I also rely on Nashorn for server side JSX rendering. Removing Nashorn without any replacement would really hurt us. We would therefore like to see a precise statement about replacement in the JEP, too. Thanks! — Michael Vitz
- Previous message: New candidate JEP: 335: Deprecate the Nashorn JavaScript Engine
- Next message: New candidate JEP: 335: Deprecate the Nashorn JavaScript Engine
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]