DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9717>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9717 wsdl2java doesn't seem to understand some of the basic schema types ------- Additional Comments From [EMAIL PROTECTED] 2002-06-26 23:25 ------- making the user specify fixed WSDL (option 1) was exactly what i wanted to do. i started from that point with some reasonable restrictions enforced by my custom schema types. then i was hoping to modify the deploy.wsdd file to specify my custom types' mappings explicitly. i was, it appears, a bit naive about what is currently possible :-) however, at this (admittedly quite limited) stage of my experience, i still think that is what i would prefer. i.e. a fancy, restrictive WSDL schema that the Web Services engine checks for me, but mapped to simple java types. (and i figured the constraint checking could just be handled directly by the XML parser/schema validator.) for example, i have a parameter that is a String representation of a 9-digit account number (type is a subtype of xsd:string). if the WSDL/schema/engine can restrict it to 9 numeric digits (obviously, advertising to callers that's what it has to be), my java code can just treat it as a String without any sort of sophisticated subclassing or range checking. re-reading the last comment, i see there are some fairly complicated issues here, so forgive me if i'm way over-trivializing the problem. i'm new to web services, but the potential of WSDL had me impressed, and the approach i described seemed the most powerful way to use it. thanks for the discussion/consideration.
