DO NOT REPLY [Bug 45240] New: Deprecated SAX API Used by SAXCatalogReader and SAXCatalogParser

https://issues.apache.org/bugzilla/show_bug.cgi?id=45240

           Summary: Deprecated SAX API Used by SAXCatalogReader and
                    SAXCatalogParser
           Product: XmlCommons
           Version: 1.x
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: minor
          Priority: P3
         Component: Resolver
        AssignedTo: commons-dev@...
        ReportedBy: dshearer@...


Created an attachment (id=22147)
 --> (https://issues.apache.org/bugzilla/attachment.cgi?id=22147)
Patches for both SAXCatalogReader and SAXCatalogParser in one file.

SAXCatalogReader and SAXCatalogParser use these deprecated SAX classes:
org.xml.sax.DocumentHandler, org.xml.sax.Parser, and org.xml.sax.AttributeList.


--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

https://issues.apache.org/bugzilla/show_bug.cgi?id=45240





--- Comment #1 from David Crossley <crossley@...>  2008-06-19 18:58:41 PST ---
Thanks. However could you please provide a new patch. Whatever text editor you
are using has made many text-formatting changes. Please only change the
necessary lines.


--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

https://issues.apache.org/bugzilla/show_bug.cgi?id=45240


Dylan Shearer <dshearer@...> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #22147|0                           |1
        is obsolete|                            |




--- Comment #2 from Dylan Shearer <dshearer@...>  2008-06-19 19:52:22 PST ---
Created an attachment (id=22148)
 --> (https://issues.apache.org/bugzilla/attachment.cgi?id=22148)
Patch without formatting changes.


--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

https://issues.apache.org/bugzilla/show_bug.cgi?id=45240


Dylan Shearer <dshearer@...> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #22148|0                           |1
        is obsolete|                            |




--- Comment #3 from Dylan Shearer <dshearer@...>  2008-06-19 19:57:36 PST ---
Created an attachment (id=22149)
 --> (https://issues.apache.org/bugzilla/attachment.cgi?id=22149)
Patch without formatting changes (fixed).


--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

https://issues.apache.org/bugzilla/show_bug.cgi?id=45240





--- Comment #4 from Michael Glavassevich <mrglavas@...>  2008-06-19 20:21:48 PST ---
Yes SAX1 is deprecated, but the proposed patch makes backwards incompatible
changes to the API. Deleting methods and interfaces from an API which has
shipped is generally a bad thing to do. There are lots of methods, classes and
interfaces in the Java platform that are deprecated and none of them can be
deleted because it might break some existing application. Not in favour of
changes which might break the existing user base.


--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

https://issues.apache.org/bugzilla/show_bug.cgi?id=45240





--- Comment #5 from Dylan Shearer <dshearer@...>  2008-06-19 20:41:32 PST ---
(In reply to comment #4)
> Yes SAX1 is deprecated, but the proposed patch makes backwards incompatible
> changes to the API. Deleting methods and interfaces from an API which has
> shipped is generally a bad thing to do. There are lots of methods, classes and
> interfaces in the Java platform that are deprecated and none of them can be
> deleted because it might break some existing application. Not in favour of
> changes which might break the existing user base.
>

Aren't SAXCatalogReader and SAXCatalogParser internal classes?


--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

https://issues.apache.org/bugzilla/show_bug.cgi?id=45240





--- Comment #6 from Michael Glavassevich <mrglavas@...>  2008-06-19 20:51:08 PST ---
They're a documented part of the API:
http://xml.apache.org/commons/components/apidocs/resolver/index.html. Users of
the resolver might be using these classes. In fact Xerces uses
SAXCatalogReader directly.


--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

https://issues.apache.org/bugzilla/show_bug.cgi?id=45240


Dylan Shearer <dshearer@...> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID




--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.