Thanks Benson, I located the source, I was momentarily confused because the
source trees in the source distribution do not follow the package names as
closely as I expected. I finally found the source under "frontend".
I wanted to look at the source to see about making some enhancements because I
noticed that the serialization strategy seems to ignore attributes defined in
the XML schema, and also seems to ignore elementFormDefault, i.e. there seems
to be no provision for qualifying element names with prefixes during
serialization.
All of the serialization routines seem to take the following general form:
if (elementName != null) {
xml = xml + '<';
xml = xml + elementName;
xml = xml + ' ';
xml = xml + 'xmlns:jns0=\'http://xyz.com\';
if (extraNamespaces) {
xml = xml + ' ' + extraNamespaces;
}
xml = xml + '>';
}
I don't see how attributes defined on the complex type for which "elementName"
is being emitted are ever emitted, or how the serialized XML would survive
validation if elementFormDefault="qualified" was specified in the XML schema.
Am I missing something?
Thanks,
Norris
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Benson Margulies
Sent: Saturday, August 23, 2008 2:23 PM
To: Merritt, Norris; CXF Users
Subject: wsdl2js
Norris,
wsdl2js was subsumed into CXF. Most of the code is inside
rt/javascript, but the command-line interfaces are in the tools area.
There is documentation at
http://cwiki.apache.org/CXF20DOC/javascript-clients.html.
--benson
