Re: XmlSerializer and consistent use of exceptions
Stefan Haustein <[email protected]>
| Newsgroups | gmane.text.xml.xmlpull.devel |
|---|---|
| Organization | Univ. Dortmund FB 4 LS 8 |
| Message-ID | <[email protected]> |
> i like that exception takes instance of XmlPullParser as it allows to extract > any information it needs. but dependency is also not good. maybe we should > have a clean separate exception just for serializer XmlSerializerException? > changing constructor in XmlPullParserException is backward incompatible > change that i would like to avoid ... I think breaking compatibility here is not much of an issue since the XmlPullParserException is usually constructed in the XmlPullParser only. In my opinion, adding another exception would be too expensive. In my opion, the exception is not veryusefull since you usually cannot resume anyway. The functionality of the existing constructor can be replaced by a corresponding create method inside the parser implementation easily. Best, Stefan > > thanks, > > alek > > > > To unsubscribe from this group, send an email to: > [email protected] > > > > Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/ > > -- Stefan Haustein Univ. Dortmund, FB 4, LS 8 tel: +49 231 755 2499 Baroper Str. 301 fax: +49 231 755 5105 D-44221 Dortmund (Germany) www-ai.cs.uni-dortmund.de