Custom Query (101 matches)
Results (16 - 18 of 101)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#108 | fixed | Error when reading zcfg without DataOutputs definition | djay | |
Description |
Return an informative message when no DataOutputs? was specified in a ZCFG. |
|||
#3 | fixed | Filling optional default values issue with GIS GRASS integration | soeren | |
Description |
By default the zoo kernel fills all optional literal data inputs with default values. Thats fine in case default literal values are provided. But here is the issue: optional literal data inputs are also attached in case no default values are available. This results in something like "distance=NULL", which will in case of gis grass modules, abort the processing with an error. There may be two solutions:
Both solutions are ok in case of literal data for me. The second one has the advantage, that the input map structure are fully available with literal data for service modules. So no new memory must be allocated/modified in case the developer decides to modify literal data in the input map. Optional complex data inputs should IMHO not be filled. GIS GRASS has many modules with optional complex data inputs. |
|||
#106 | fixed | Fix issue in displayStack function | djay | |
Description |
When you are not allowed to created the temporary file required to store the JVM call stack, it imply that the ZOO-Kernel will segfault. |