For web applications, typically these files are usually stored un-jarred in the WEB-INF\classes folder, or in a jar in the WEB-INF\lib folder. End users generally don't have access to these directories.
If you are doing a rich client application, then an educated user could search through the JAR and find the XML. You could get around this with some encryption/decryption of the files manually before passing them to iBATIS. iBATIS does not have native support for this. In this case you might want to try an obfuscator too if you are concerned about reverse compilers. Jeff Butler On Nov 19, 2007 3:55 PM, Lindsay Oproman <[EMAIL PROTECTED]> wrote: > Hello, > > When I deploy my application, is there any way to protect the contents > of the XML > mappings holding the SQL? I don't want my end users having access > to my schema, or being able to change queries for that matter. > > Lindsay >
