[ http://issues.apache.org/jira/browse/DERBY-1772?page=comments#action_12431279 ] A B commented on DERBY-1772: ----------------------------
> This is a run-time error but it has the SQL state '42' for compile error, I guess that depends on what you mean by "run-time" error. In order to compile the query expression the Xalan classes have to be present. Derby checks to see if they are present when it first encounters the XML operator--i.e. at compile time--and then when the syntax of the SQL/XML operator has been successfully parsed, the XML query expression is itself compiled. All of this occurs as part of Derby compilation, hence the error code "42". But if that's too much of a technicality, I won't complain if the error message is changed... > Error 42Z78 "Failed to locate 'Xalan' API classes" should not have sqlstate > class '42' > --------------------------------------------------------------------------------------- > > Key: DERBY-1772 > URL: http://issues.apache.org/jira/browse/DERBY-1772 > Project: Derby > Issue Type: Bug > Components: SQL > Affects Versions: 10.2.1.0 > Reporter: Daniel John Debrunner > Priority: Minor > > This is a run-time error but it has the SQL state '42' for compile error, > and thus in Java SE 6 will have a SQLException of type > SQLSyntaxErrorException. > ERROR 38000: The exception 'java.sql.SQLSyntaxErrorException: Failed to > locate ' > Xalan' API or implementation classes. XML operations are not permitted > unless t > hese classes are in your classpath.' was thrown while evaluating an > expression. > ERROR 42Z78: Failed to locate 'Xalan' API or implementation classes. XML > operat > ions are not permitted unless these classes are in your classpath. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
