Benson Margulies wrote:
Here is the XML for the java2js command.
The basic idea is this: the code has to process a service. That means it
needs an SEI, a front-end, and a data binding, just like java2ws. This
is going to require some refactoring of code into some common place from
java2ws. It can't be tools-common, without producing a circular
build-path problem. The whole idea of the implementation of
rt/javascript is that this tool is very nearly identical to java2ws. We
want to cause the very same kind of ServiceInfo model to get built, but
then run a Javascript generator instead of a WSDL generator.
Agreed !
I can split java2ws into two modules : java2common and java2ws then
you can reuse
the java2common to build this new tool .
