You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by xa...@xml.apache.org on 2004/09/05 08:04:36 UTC

[jira] Updated: (XALANJ-1089) Message about additional sort data types could be better

The following issue has been updated:

    Updater: Brian Minchau (mailto:minchau@ca.ibm.com)
       Date: Sat, 4 Sep 2004 11:04 PM
    Changes:
             assignee changed from Xalan Developers Mailing List
             description changed from xsl:sort allows the data-type attribute to be either "text", "number", or a
QName qualified to some other namespace. If the latter were to be implemented
in Xalan, we would have to recognize the qualified name. Since we don't have
any additional types, sorterr08 covers the case where the value looks like a
QName (i.e., contains a colon) but is just a garbage string to us. Currently,
we put out a message that says this is a to-do item. While the message does
lead the user to the vicinity of the problem, it's not a real error message.
It should be a real error saying
No known sort routine for [QName]
or something similar. If we ever implement a recognized QName, this error will
still apply for the unrecognized ones.

See sorterr01 for the case of an unrecognized name without a colon. We emit a
good message in this case. to xsl:sort allows the data-type attribute to be either "text", "number", or a
QName qualified to some other namespace. If the latter were to be implemented
in Xalan, we would have to recognize the qualified name. Since we don't have
any additional types, sorterr08 covers the case where the value looks like a
QName (i.e., contains a colon) but is just a garbage string to us. Currently,
we put out a message that says this is a to-do item. While the message does
lead the user to the vicinity of the problem, it's not a real error message.
It should be a real error saying
No known sort routine for [QName]
or something similar. If we ever implement a recognized QName, this error will
still apply for the unrecognized ones.

See sorterr01 for the case of an unrecognized name without a colon. We emit a
good message in this case.
             environment changed from Operating System: Other
Platform: Other to Operating System: Other
Platform: Other
             priority changed to Blocker
             Component changed to Diagnostic messages/resources
             Component changed from Xalan
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://issues.apache.org/jira/browse/XALANJ-1089?page=history

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/XALANJ-1089

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: XALANJ-1089
    Summary: Message about additional sort data types could be better
       Type: Bug

     Status: Unassigned
   Priority: Blocker

    Project: XalanJ2
 Components: 
             Diagnostic messages/resources
   Versions:
             2.4Dx

   Assignee: 
   Reporter: david_marston

    Created: Thu, 11 Jul 2002 9:24 PM
    Updated: Sat, 4 Sep 2004 11:04 PM
Environment: Operating System: Other
Platform: Other

Description:
xsl:sort allows the data-type attribute to be either "text", "number", or a
QName qualified to some other namespace. If the latter were to be implemented
in Xalan, we would have to recognize the qualified name. Since we don't have
any additional types, sorterr08 covers the case where the value looks like a
QName (i.e., contains a colon) but is just a garbage string to us. Currently,
we put out a message that says this is a to-do item. While the message does
lead the user to the vicinity of the problem, it's not a real error message.
It should be a real error saying
No known sort routine for [QName]
or something similar. If we ever implement a recognized QName, this error will
still apply for the unrecognized ones.

See sorterr01 for the case of an unrecognized name without a colon. We emit a
good message in this case.


---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org