|
So clearly Java Persistence only addresses part of the problem. For a networked application (rather than a local storage app like iTunes or an AddressBook) you can't give the application direct access to the database. Even if you used a secure connection and obfuscated classfiles someone could eventually hack into your server. I discussed this issue with a friend of mine who's a server side developer and he recommends transferring my domain objects over the wire with SOAP and then using Persistence on the server side. The advantage here is that you can reuse your annotated data model objects on both sides and still have the security of server side validation. I plan to do another article in the future as I work out the details. |
java.net RSS Feeds
