Poster at Kinetium dot Com wrote: > Could you'll please reconsider your position on scripting support in XXE? > > Take your pick of any ONE of the scripting languages - Beanshell, Jruby, > Jython, ... Please pick one that can run on a JVM, so it can use your Java > interfaces and be seen by XXE as a Java add-on. > > It could make it _much_ easier for people to customize and extend your > product.
XXE used to have scripting support (through scripting plug-ins) and we gave up this feature mainly for the following reasons: [1] This didn't make it easier to *customize* the product. Customization is better performed using directives specified in (declarative) XML. [2] Because we don't have a *very-high level* API for use by scripts, extensions written in BeanShell, or to a lesser extend Rhino, were slow to the point of being unusable. [3] Because we don't have a *very-high level* API for use by scripts, debugging scripts was hell. Scripting support means in fact providing an alternate *very-high level* API (really, really mandatory: the Java native API is too low-level for scripts), documenting it, giving a lot of useful examples, supporting people when they write scripts using their favorite scripting language. We are a very small company and we simply cannot afford doing that. However we clearly understand the problem and therefore XXE V3 (or V3.1) will have many features which will make customizing XXE much easier.
