Details
-
Bug
-
Status: Open
-
Resolution: Unresolved
-
beta-3
-
None
-
None
-
Operating System: All
Platform: All
-
10872
Description
i need to be able to specify a custom WSDL for a deployed service. Axis should
both validate incoming requests against that WSDL and return that WSDL when
queried with "?wsdl".
the latter is less important, but probably much easier 
the former is, i
believe, vital to properly supporting WSDL.
particularly, it seems to me that the XML parser should be validating request
data against the internal type schema while it's parsing. (i made some related
comments in <a href="http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9717">bug
9717</a>)
i've read some discussion about wsdl2java generating sophisticated setters to
handle the validation, (and enough meta-data to convert that java back to the
original WSDL) but it seems inefficient for the engine to parse the XML, then
call setters to validate the data, when the parser could have validated it
itself. plus, that requires use of wsdl2java in my server-side coding 
also, it seems like a lot of Axis code to write to handle all those restriction
types in the java code generation. it seems like a quicker path to
(server-side) validation is to implement just enough code to let Xerces do the
work. (i realize there are "internal" and client-side reasons to also make
the wsdl2java enhancements.)
when i first started reading about Web Services, it was this automatic
validation of sophisticated schemas that got me excited about the interface
potential. i am new to Web Services, so i could be misunderstanding something
here, but this seems like a very powerful piece of the puzzle that is,
currently, missing. (and at least a couple of other co-workers here had the
similar expectations.)
i didn't find any other bug reports that addressed this broad issue, and i
didn't see any documentation that suggested such a capability was already
implemented or intended for a future release, so if something is out there and i
missed it, i apologize for the duplication.
(btw, i wasn't sure how to categorize this "bug". if i understand the intent of
WSDL correctly, this could be a "major" bug. on the other hand, i don't know
the current state of specs well enough to really say that, so i've submitted it
as an "enhancement".)