I guess my problem is that the error message isn't really clear, I'm in a situation of putting an API out there to third parties, and so I've gone with a pretty strict API to make message validation easier, but I'm finding ADB error messages to be rather terse and uninformative. So I'm kind of curious if there is a hooking point where I can extend the ADB layer to return a more meaningful message, something akin to what you would get out of validating the request against the schema. In my example the absence, or misplacement of that categoryId field returns an error indicating that it is categoryId that is broken, but it is possible for there to many instances of category id so with out a reference to which one, or a line number, or even a more clear error message a user is sort of left with an uneasy feeling on exactly what went wrong.
Has anyone else tackled complex validation scenario's? ________________________________ From: Amila Suriarachchi [mailto:[EMAIL PROTECTED] Sent: Friday, August 31, 2007 12:27 AM To: axis-user@ws.apache.org Subject: Re: wsdl2java question in the template it says /** * <xsl:value-of select="@name"/>.java * * This file was auto-generated from WSDL * by the Apache Axis2 version: #axisVersion# #today# */ I think it has pick a wrong version some where. Amila. On 8/31/07, Lindsey Hess <[EMAIL PROTECTED]> wrote: Hi, I'm running Axis 1.2.1's wsdl2java against a WSDL, and when I look at the generated code it says: "This file was auto-generated from WSDL by the Apache Axis 1.4 Apr 22, 2006" Shouldn't this say Apache Axis 1.2.1? I'm a bit confused... Thank you. Lindsey ________________________________ Shape Yahoo! in your own image. Join our Network Research Panel today! <http://us.rd.yahoo.com/evt=48517/*http:/surveylink.yahoo.com/gmrs/yahoo _panel_invite.asp?a=7> -- Amila Suriarachchi, WSO2 Inc.
