The console log contains several POTENTIAL ERRORs for the Infinity WSDL

[GoogleCodeExporter]

When running the program against the Infinity wsdl, the program detects
several potential problems: 

POTENTIAL ERROR -- Schema http://microsoft.com/wsdl/mime/textMatching/ does
not contain any types!
POTENTIAL ERROR -- Schema http://schemas.xmlsoap.org/wsdl/mime/ does not
contain any types!
POTENTIAL ERROR -- Schema http://schemas.xmlsoap.org/wsdl/ does not contain
any types!
POTENTIAL ERROR -- Schema http://schemas.xmlsoap.org/soap/encoding/ does
not contain any types!
POTENTIAL ERROR -- Schema http://schemas.xmlsoap.org/wsdl/soap12/ does not
contain any types!
POTENTIAL ERROR -- Schema http://schemas.xmlsoap.org/wsdl/http/ does not
contain any types!
POTENTIAL ERROR -- Schema http://schemas.xmlsoap.org/wsdl/soap/ does not
contain any types!

These should be examined to see what's going on and if this is okay.
They're all built-in so it's probably fine; it might be worthwhile to add
the necessary types to USParser's -(NSArray*)builtInSchemas.

Original issue reported on code.google.com by will...@gmail.com on 14 Jun 2008 at 3:42

[GoogleCodeExporter]

Original comment by will...@gmail.com on 16 Jun 2008 at 1:08

• Added labels: Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Fixed in revision 9. Decided that these errors are okay for now, so removed the 
code
that outputs them to the console (that's one way of getting rid of errors...). 

As stated in the description, "it might be worthwhile to add the necessary 
types to
USParser's -(NSArray*)builtInSchemas". So consider revisiting this one day.

Original comment by will...@gmail.com on 9 Jul 2008 at 11:37

• Changed state: Fixed
• Added labels: Consider-Revisitng