Oh, hit 'send' too quickly,
All the code generation is done. You can invoke it currently with the
?js URL.
Is it wsdl2js?
That's a good thing, we can reuse the rt/js part in code generation
'All' I need to add is the command-line 'dump it to a file' in addition
to the live URL handling.
You can have your own Generator, it is OK not using the velocity
templates, you can dump them directly, not a big deal
I also have a yen to add some a new wsdl extension for the case where
someone explicitly controls the mapping from URI to javascript prefix.
Not quite understand this part, but we handle the wsdl extesions as a
plugin as well, like the wsdl:port is an extension plugin, so we can
handle the port:address equally
James
-----Original Message-----
From: Glen Mazza [mailto:[EMAIL PROTECTED]
Sent: Monday, December 03, 2007 3:35 PM
To: [email protected]
Subject: Re: tools for javascript
Ouch, that doesn't sound like fun. But I would start with
wsdl2js, look at the wsdl2java Java output velocity
templates, and just re-edit those to output JavaScript instead.
Next, during testing, I guess, see where that such a 1-to-1
mapping will
*not* work, and what workarounds you can create for that.
However, I don't know what you're going to do for the
JAXB-created classes (in the wsdl:types section). We don't
have templates for those.
Glen
Am Montag, den 03.12.2007, 14:18 -0500 schrieb Benson Margulies:
It is time to create wsdl2js and java2js. I confess that I
am daunted
by the task of starting this from zero. Is there any
possibilies that
the tool-experts would be willing to create some shells for me?
