M
marian.edu
Guest
It looks like there is still an issue with array fields in resultset (temp-table), date and datetime now works but not datetime-tz 
Calling any procedure that returns a temp-table/dataset with one field being an datetime-tz array (extent) result in the following error. com.progress.open4gl.Open4GLException: Input result set error: com.progress.open4gl.Open4GLException: 0 (7176) at com.progress.open4gl.dynamicapi.ExceptionConverter.convertToOpen4GLException(ExceptionConverter.java:155) at com.progress.open4gl.dynamicapi.Session.handleOutputErrors(Session.java:1659) at com.progress.open4gl.dynamicapi.Session.runProcedure0(Session.java:1282) at com.progress.open4gl.dynamicapi.Session.runProcedure(Session.java:830) at com.progress.open4gl.dynamicapi.Session.runPersistentProcedure(Session.java:607) at com.progress.open4gl.javaproxy.Procedure.runPersistentProcedure(Procedure.java:458) at com.progress.open4gl.javaproxy.Procedure.runPersistentProcedure(Procedure.java:375) at com.progress.open4gl.javaproxy.OpenProcObjectImpl. (OpenProcObjectImpl.java:24) at com.progress.open4gl.javaproxy.OpenProcObject. (OpenProcObject.java:23) at com.progress.open4gl.javaproxy.OpenAppObject.createPO(OpenAppObject.java:353) Seems to be a sequel of this, Progress KB - Open4GLException is thrown by the Java Open Client when receiving a ProDataSet which contains DATE EXTENT fields ... I can confirm any other data type works just fine (including RAW). As a side note, is there any reason the entries in that list aren't native date objects for DATE/DATETIME fields? For all other data types the entries in the list are primitive Java data types (Integer, BigDecimal, bool, String, byte[])... for DATE/DATETIME those are GregorianCalendarHolder??? And, the ecore version there urge to be updated to a more recent one 
Thanks, Marian
Continue reading...
Calling any procedure that returns a temp-table/dataset with one field being an datetime-tz array (extent) result in the following error. com.progress.open4gl.Open4GLException: Input result set error: com.progress.open4gl.Open4GLException: 0 (7176) at com.progress.open4gl.dynamicapi.ExceptionConverter.convertToOpen4GLException(ExceptionConverter.java:155) at com.progress.open4gl.dynamicapi.Session.handleOutputErrors(Session.java:1659) at com.progress.open4gl.dynamicapi.Session.runProcedure0(Session.java:1282) at com.progress.open4gl.dynamicapi.Session.runProcedure(Session.java:830) at com.progress.open4gl.dynamicapi.Session.runPersistentProcedure(Session.java:607) at com.progress.open4gl.javaproxy.Procedure.runPersistentProcedure(Procedure.java:458) at com.progress.open4gl.javaproxy.Procedure.runPersistentProcedure(Procedure.java:375) at com.progress.open4gl.javaproxy.OpenProcObjectImpl. (OpenProcObjectImpl.java:24) at com.progress.open4gl.javaproxy.OpenProcObject. (OpenProcObject.java:23) at com.progress.open4gl.javaproxy.OpenAppObject.createPO(OpenAppObject.java:353) Seems to be a sequel of this, Progress KB - Open4GLException is thrown by the Java Open Client when receiving a ProDataSet which contains DATE EXTENT fields ... I can confirm any other data type works just fine (including RAW). As a side note, is there any reason the entries in that list aren't native date objects for DATE/DATETIME fields? For all other data types the entries in the list are primitive Java data types (Integer, BigDecimal, bool, String, byte[])... for DATE/DATETIME those are GregorianCalendarHolder??? And, the ecore version there urge to be updated to a more recent one Thanks, MarianContinue reading...