RE: scomp Errors, Unuseful

I may be wrong, but isn't this caused by the fact that the default parser in V1 
didn't support line numbers?

-----Original Message-----
From: Roland Pereira [mailto:PereiraR@xxxxxxxxxxx]
Sent: Thursday, January 06, 2005 6:57 AM
To: user@xxxxxxxxxxxxxxxxxxx
Subject: RE: scomp Errors, Unuseful


 
Hello,
         I resolved a similar issue last time. But I had to use JAXB and the
ant script within it to find the line numbers. I then went on to rectify the
.xsd file using jaxb. The corrected .xsd file was then used by XMLBeans
(scomp) to generate the jar file which I used to code.

Thanks

-----Original Message-----
From: P. Michael Hutchins [mailto:pmh0232@xxxxxxxxxx] 
Sent: Wednesday, January 05, 2005 1:36 PM
To: user@xxxxxxxxxxxxxxxxxxx
Cc: Alex Kahn
Subject: scomp Errors, Unuseful

When I run scomp against an XSD file, I get any number of lines like:

>    [].xsd:0: error: Must be less than or equal to previous maxInclusive
>    [].xsd:0: error: Must be greater than or equal to previous 
> minInclusive

That's not all that helpful, since there's 79 m{ax, in}Inclusive-s in the
xsd.

Is there a way to get actual line numbers of the offenders reported?
(the ":0:"s suggest so to me)

...and/or the offending text


Thanks,

   -- M. 


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@xxxxxxxxxxxxxxxxxxx
For additional commands, e-mail: user-help@xxxxxxxxxxxxxxxxxxx


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@xxxxxxxxxxxxxxxxxxx
For additional commands, e-mail: user-help@xxxxxxxxxxxxxxxxxxx