Project:
| View Revisions: Issue #40614 | [ Back to Issue ] | ||
| Summary | 0040614: API change: support method chaining in OBQuery and OBCriteria | ||
| Revision | 2019-04-17 12:52 by caristu | ||
| Description | As part of the changes introduced with 0040552, the methods that helps to build an OBQuery/OBCriteria will return the instance instead of void. This will allow to use method chaining with these classes in the same way that Hibernate's Query class. This is an ABI change[1]: it does not affect source code compatibility (it will not break any compilation) but it breaks binary compatibility (i.e. OBQuery/OBCriteria related bytecodes that were previously compiled against the old API will no longer run). In case of having a jar compiled against the old OBQuery/OCriteria API it should be recompiled with the new API in order to make it compatible with 3.0PR19Q3. [1] https://en.wikipedia.org/wiki/Application_binary_interface [^] |
||
| Revision | 2019-04-17 12:45 by caristu | ||
| Description | As part of the changes introduced with 0040552, the methods that helps to build an OBQuery/OBCriteria will return the instance instead of void. This will allow to use method chaining with these classes in the same way that Hibernate's Query class. This is an ABI change: it does not affect source code compatibility (it will not break any compilation) but it breaks binary compatibility (i.e. OBQuery/OBCriteria related bytecodes that were previously compiled against the old API will no longer run). In case of having a jar compiled against the old OBQuery/OCriteria API it should be recompiled with the new API in order to make it compatible with 3.0PR19Q3. |
||
| Revision | 2019-04-17 12:37 by caristu | ||
| Description | As part of the changes introduced with 0040552, the methods that helps to build an OBQuery/OBCriteria will return the instance instead of void. This will allow to use method chaining with these classes in the same way that Hibernate's Query class. This API change does not affect source code compatibility (it will not break any compilation) but it breaks binary compatibility (i.e. OBQuery/OBCriteria related bytecodes that were previously compiled against the old API will no longer run). In case of having a jar compiled against the old OBQuery/OCriteria API it should be recompiled with the new API in order to make it compatible with 3.0PR19Q3. |
||
| Revision | 2019-04-17 12:36 by caristu | ||
| Description | As part of the changes introduced with 0040552, the methods that helps to build an OBQuery/OBCriteria will return the instance instead of void. This will allow to use method chaining with these classes in the same way that Hibernate's Query class. This API change does not affect source code compatibility (it will not break any compilation) but it breaks binary compatibility (i.e. OBQuery/OBCriteria related bytecodes that were previously compiled against the old API will no longer run). In case of having a jar compiled against the old OBQuery/OCriteria API it should be recompiled with the new changes in these classes to make it compatible with 3.0PR19Q3. |
||
| Revision | 2019-04-15 09:34 by caristu | ||
| Description | As part of the changes introduced with 0040552, the methods that helps to build an OBQuery/OBCriteria will return the instance instead of void. This will allow to use method chaining with these classes in the same way that Hibernate's Query class. This API change does not affect source code compatibility (it will not break any compilation) but it breaks binary compatibility (i.e. OBQuery/OBCriteria related bytecodes that were previously compiled against the old API will no longer run). |
||
| Revision | 2019-04-15 09:25 by caristu | ||
| Description | As part of the changes introduced with 0040552, the methods that helps to build an OBQuery/OBCriteria will return the instance instead of void. This will allow to use method chaining with these classes in the same way that Hibernate's Query class. Although these changes are not breaking any compilation, this is an api change because the byte code generated is different. Thus, it is possible to have runtime errors in case old versions of OBQuery/OBCriteria were compiled within a jar file, and that jar is used in an environment with these changes in OBQuery/OBCriteria. |
||
| Revision | 2019-04-15 09:24 by caristu | ||
| Description | As part of the changes introduced with 0040552, the methods that helps to build an OBQuery/OBCriteria will return the instance instead of void. This will allow to use method chaining with these classes in the same way that Hibernate's Query class. Although these changes are not breaking any compilation, this is an api change because the byte code generated is different. Thus, it is possible to have runtime errors in case old versions of OBQuery/OBCriteria were compiled within a jar file, and if that jar is used in an environment with these changes in OBQuery/OBCriteria. |
||
| Revision | 2019-04-15 09:17 by caristu | ||
| Description | As part of the changes introduced with 0040552, the methods that helps to build an OBQuery/OBCriteria will return the instance instead of void. This will allow to use method chaining with these classes in the same way that Hibernate's Query class. | ||
| Copyright © 2000 - 2009 MantisBT Group |
 |