Weblog: Morgan DelagrangeIt seemed like a good idea at the time...Continuous integration- May 2, 2003 Rod has started a series on our Continuous Integration environment 1 2. I've also jotted down notes on our CI process for my weblog, but Rod is doing a superlative job, so I'll leave it to the master. Just one comment on the series so far. When putting together a Continuous Integration environment, you want build failures to evoke one of two feelings: 1. guilt ... 3 : a feeling of culpability for offenses 2. shame ... 2 : a condition of humiliating disgrace or disrepute : IGNOMINY Source:.http://radio.weblogs.com/0116794/2003/05/02.html#a13 JDK 1.4, now including the kitchen sink- May 2, 2003 James: Be careful of JDK 1.4 No doubt. However, James left out my favorite JDK 1.4 "feature", the built-in XML parser. How convenient! Unless of course, you want to upgrade or modify it in any way. Then you have to resort to the incredibly awkward Endorsed Standards Override Mechanism, which is the least hosting-friendly addition to Java in recent memory. While the Servlet APIs have in recent years made substantial improvements to the organization of their...http://radio.weblogs.com/0116794/2003/05/02.html#a12 Encoding, schmencoding- May 2, 2003 I was writing a character encoding FAQ for our company's Wiki when I came across something in the JAXP javadocs that has always puzzled me: StreamResult Javadocs: Normally, a stream should be used rather than a reader, so that the transformer may use instructions contained in the transformation instructions to control the encoding. JAXP has a similar warning for StreamSource as well. Why is using character streams so ill-advised The character encoding behaviour that XSL parsers should.http://radio.weblogs.com/0116794/2003/05/02.html#a11 |