[
https://issues.apache.org/jira/browse/TUSCANY-1063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kelvin Goodson resolved TUSCANY-1063.
-------------------------------------
Resolution: Fixed
Added print stack trace for any Exception (note one mod for this JIRA was
inadvertently committed under TUSCANY-1293)
Also added error report for case where input file results in no metadata (not
easy to catch case where some metadata is in error).
> Improve diagnostics running XSD2JavaGenerator against bad schema
> ----------------------------------------------------------------
>
> Key: TUSCANY-1063
> URL: https://issues.apache.org/jira/browse/TUSCANY-1063
> Project: Tuscany
> Issue Type: Improvement
> Components: Java SDO Tools
> Affects Versions: Java-SCA-M2
> Reporter: Scott Kurz
> Priority: Minor
> Fix For: Java-SDO-Next
>
>
> I gave an invalid XSD file to the XSD2JavaGenerator and had to use the
> debugger to figure out the problem.
> It might be nice to do a printStackTrace() on any exception before throwing
> out of main().
> Also it might be good to print out simple error messages in the cases that:
> a) the usage was correct but the specified file can't be read
> b) the file can be read but there is no valid schema found
> As a sample of the latter here is my invalid schema
> <xsd:schema xmlns:tns="http://helloworld";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"; elementFormDefault="qualified"
> targetNamespace="http://helloworld";>
> <complexType name="Person">
> <sequence>
> <element name="firstName" type="string"/>
> <element name="lastName" type="string"/>
> </sequence>
> </complexType>
> </xsd:schema>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
