|
I'm currently involved in a free time project which will work with hibernate and HSQL (maybe later on switching to H2, depending on performance tests to be made once evrything works). I've done quite some online investigation, creating little test applications, printing out the handbook and some tutorials. Right now I'm pretty much at the beginning, trying to define my data objects (domain layer), getting them hooked up with hibernate and keeping my fingers crossed that I won't have to refactor too much as I don't know yet how easy or hard it will be to rewrite the mappings and get the test data changed.. it'll remain a white spot on my map
At work I currently have to deal with another situation. I'm developing client applications hooked up to our web apps via XML-RPC. By now I only had to read data out of our web app's database but currently I'm working on a client which will act as most db client apps, only with the difference that I can't access it via JDBC but will have to use XML-RPC. There are so many persistence frameworks / ORMs out there, but I just can't seem to find something that is not focussed on working with JDBC or (XML) flat files. I'm now at a point where I feel forced to do my own persistence framework. Armed with a printout of Scott Ambler's "The Design of a Robust Persistence Layer For Relational Databases" I'll see what I can do and hope I'll achieve something right before the my boss ripps off my head because of the delay.
I just wanted to remind you and other readers, that there may be more to 'persistence' than what's currently coverred in magazines and blogs. Hibernate, all those JDO implementations and others come from the server side and only work with direct JDBC access, which you may not get everywhere as security policies may forbid the related database ports to be opened in firewalls.
I'd be thankful for every tip someone can give me on how to do persistence with XML-RPC / webservices. |
java.net RSS Feeds
