Yea, that's basically what I figured you'd have to do to get Hibernate, GWT, and a database to work with spatial objects. I commend you for not running with your tail between your legs like I did when I saw the mountain of work I'd have to do to integrate all of those technologies. :)
If all your spatial calculations are done on the server side, then you shouldn't have any problems with the JTS API not being supported by GWT. I think the big thing will be to make converting from JTS to GWT and vice-versa again very efficient. I use the Maps implementation at http://code.google.com/p/gwt-google-apis/, so you may have to modify my code to work with the Mapitz library. If you get create an OverlayManagerChangedListener implement that uses Polygons for the past map bounds, I'd love to see the code and add it to the implementation for others. If you need help with it, I'd be willing, but at this point I'm not going to implement spatial functionality for my app. Good luck, Eric --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
