Prepare Java strings for JavaScript evaluation, similar to SQL prepared statements. Saves you from quote escape nightmares!
Browsing Posts tagged java
When you have more backslashes than words in the strings you are constructing, perhaps it’s time to look at another way of handling special characters like quotes.
Naming a framework is like naming a child – you need to be careful because people will find ways to make fun of the name, especially when it becomes surreal in truth. You’re a happy countenance and before you guano it, a tiny dipthong comes along and you’re excrement. That’s good advice, or my name [...]
Most of my ThoughtWorks colleagues love tests. We love writing tests and watching them fail, and we love writing the code that then makes them pass. We love tests so much that most of the time taken in building the software is in the running of the tests to make sure we haven’t done something [...]
TestCase.getName() was useful from time to time. I recently used it on a project where the name of the test was used as the “client application” name in the database connection properties. This was good for tracking what tests were doing in the database when they made use of stored procedures (by using SQLSleuth for [...]
Javaâ„¢ isn’t really the success we think it is, you know. Java programs written the way Gosling et al originally intended would clearly be using the object-oriented paradigm (sure, they’d be applets in a browser, but that’s another story). What happens when the COBOL crowd (of which I was one) gets their working-storage sections and [...]
Imagine, if you will, a core application’s code base that stretches back ten years, has around 3,500 classes, and 15,000 compiler warnings. In its germination, the Java industry had confused ideas about interoperability, no standard collections, no O/R mapping frameworks, application servers (lightweight or otherwise), and no sensible OO patterns of enterprise architecture to be [...]
Jim thought he’d wind me up this morning and told me to read his blog about SCA. This is another attempt at letting you expose an object-oriented business model to those who may wish to interoperate with your application. In summary, it’s a way of declaring an object interface in SOAP. Sounds great, doesn’t it? [...]
