| <!DOCTYPE doctype PUBLIC "-//w3c//dtd html 4.0 transitional//en"><html><head> |
| <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> |
| <meta name="Author" content="IBM"><title>Platform Text Breaking API changes</title></head><body text="#000000" bgcolor="#ffffff"> |
| |
| <table border="0" cellspacing="5" cellpadding="2" width="100%"> |
| <tbody> |
| <tr> |
| <td align="left" width="72%"> <font size="+3"><b>Platform Text - |
| Breaking API changes from R2.1 to R3.0</b></font> <font size="-2" color="#8080ff"><br> |
| </font></td> |
| </tr> |
| <tr> |
| <td> |
| <ul> |
| <li><span style="font-weight: bold; font-style: italic;">org.eclipse.jface.text.source.AnnotationModel.addAnnotation(Annotation, Position, boolean)</span>: |
| changed signature to throw <code>org.eclipse.jface.text.BadLocationException</code> |
| in order to add support for better handling of invalid document |
| positions. Only clients which extend (i.e. call super) this method will be |
| broken. To fix the problem either catch the exception from the super |
| call or change the signature in the extended method. The latter is |
| suggested since clients should decide how to handle invalid document |
| positions.<br> |
| </li> |
| </ul> |
| </td> |
| </tr> |
| <tr> |
| <td> <font size="-1"> This document lists the breaking API |
| changes that occurred between R2.1 and R3.0 and how to migrate from the |
| R2.1 API to the R3.0 API. </font> </td> |
| </tr> |
| </tbody> |
| </table> |
| <p> </p> |
| </body></html> |
