This content has been marked as final. Show 2 replies
MapViewer internal libraries have the support for annotation texts and could be used, but they are not public with supported documentation. If you have done any implementation using some of MapViewer internal libraries, then you may be able to use the annotation text part. You can write to me joao dot paiva at oracle dot com and we can talk more about this.
Yes, I found the classes in sdoviz (but only after I'd written my half baked versions). I was able to successfully create a JPA Converter and have that plus a JUnit test package that runs through both JDBC and JPA CRUD tasks. So if anyone wants these just send me an email and I'll happily send them back to you.
But, having done that and explored the functionality of ST_ANNOTATION_TEXT I'm almost certain that we won't use it unless we run across a client with a legacy implementation of it. The structure is awkward and complex and I half-suspect that it is only there to satisfy OGC compliance requirements. No blame to Oracle though, it is clearly the OGC standard, but like much OGC standards I struggle to believe that the designers ever actually had to deliver a functioning system. Before I get flamed, I express that opinion having been programming and creating spatial database and GIS systems for 34 years now and I'm a very 'practical' programmer. ST_ANNOTATION_TEXT just doesn't seem to be the model I'd want to use to implement a powerful annotation subsystem with.
Thanks for you help though and if anyone wants the Eclipselink JPA Converter for ST_ANNOTATION_TEXT I'm happy to email them the source code.
Edited by: mmillman on Feb 17, 2012 12:42 PM