Several people have already used the tool to "jump start" a WSDL, but
it's not quite mature enough to be the primary way of maintaining a
WSDL. I'm wondering if the current method is the most ideal way to
go? Or maybe try a language-based DSL, such as Ruby or Groovy. I
think the key for me would be a type library supporting XSD data
types / declarations.
It is important that the tool be usable for Java or .Net development.
At work we've been using it for .Net work, so I know it's compatible
(with a few warts) with wsdl.exe. A ruby-based DSL might make it
easier to use either Java or .Net (using IronRuby?). Or maybe the
implementation doesn't matter, the use of Java is just an internal
detail of a command-line tool.
I just wanted to throw these thoughts out there ... if anyone has any
preference, or experience with XSD type libraries, or more DSL
experience than I ... I'd appreciate some feedback.
Regards,
Jason