|
Stefan, POJO is a Plain Old Java Object so when you see that it means the property value can be any Java object, we don't have to know how to handle it but some models may require the data to be persevered. A feature without a schema is basically just a Map of property names to values, rather than the JUMP features where you have an array and it's the schema which maps from the array index to the property name. In some cases this is too rigid a model, consider the case where you want to rename from one schema to another or create additional properties e.g. a geometry from a lat/lon property values. This may need to be done in several steps, which you couldn't do easily with the fixed feature model in JUMP. Paul Stefan Steiniger wrote: hei.. i did not read all the stuff before until now... but.. your suggestions are nice.. but if i think what all need to be changed (especially in terms of avoiding errors).. i don't know?but maybe it is more simple than i thought if one can simply add some feature properties such as AttribtuteType.Collection or Feature.hasSchema()? Although i don't understand how a feature can not have a schema. Otherwise it is a geoemtry? BTW. what is a POJO? sorry guys stefan Paul Austin schrieb: https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel |
------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/
_______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
