Hi, The thing is the parsing logic doesn't identify that the interval element is at the correct position. Just to have an idea can you check following line to the attached c file (line 361) and see what is the expected element and what is actually met.
AXIS2_LOG_ERROR(env->log, AXIS2_LOG_SI, "element_qname = %s & qname = %s", axutil_qname_to_string(element_qname, env), axutil_qname_to_string(qname, env)); Thanks Dimuthu On Wed, Apr 2, 2008 at 12:00 AM, Sérgio Gomes <[EMAIL PROTECTED]> wrote: > Hello again, > > Sorry to bother with yet another issue, but it seems I keep running > into them :-/ > > I'm getting an error about a missing required element, but it's > actually present in the returned XML, as far as I can see. This is the > error: > > [Tue Apr 1 14:57:03 2008] [error] adb_SchedulingInterval.c(360) non > nillable or minOuccrs != 0 element endHour missing > > > Every "interval" structure in the XML has and endHour element. I'm > attaching the relevant part of the log and the .c file where the error > is taking place. > > Thanks, > Sérgio > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
