Custom Query (101 matches)
Results (100 - 101 of 101)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#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. |
|||
#1 | fixed | Maintaining, security and debugging enhancement request for zoo kernel | soeren | |
Description |
I know that the current release is a proof of concept, so this request is related to the next release, but attached to the current. While working on GIS GRASS ZOO integration, i faced several issues and obstacles using the zoo-kernel.
Hence i have modified several files in zoo-kernel because of security and stability reasons and added additionally debug output. The modification are made in the kernel and the python loader part.
I may have implemented new bugs while trying to reduce them. :/ So intensive testing is needed. Patch is attached.
|