We recently upgraded Weblogic Workshop to version 10.2. When I went to regenerate an existing Service Control from a new WSDL file, I was greeted with a not so nice error popup...

Here's how to get rid of the log message-- INFO: The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path when you startup Tomcat on OSX. On Windows, all one needs to do is drop in a precompiled dll, on OSX there are a few more steps...

Previously, I wrote an article on how to achieve dynamic list binding in Spring MVC. Since I wrote that article, I have received emails and comments that ask (in a roundabout way) Why would I need to do this? When I wrote the other article I didn't explain the why; I just wrote the how. Here's why you need dynamic binding and the problems it is trying to solve.

This book was just ok for me. I had already worked with Spring (a little) before picking up this book. I have been using Spring for two years since and have only needed to use the book one time. The website documentation is pretty thorough and maybe a little challenging for the newbie; this book might be good for a novice. I really like the way Chapter 4 (on database abstractions) is written but found Chapter 8 (on Spring MVC) to be really anemic.

Prior to reading this book my security awareness level was average at best. I knew that sensitive information should probably be encrypted in the database, used one-way hashes for passwords, and used SSL for any network communications not protected by a firewall. I had enough information to speak intelligently about the subject but not precisely about it.

After reading the book, I know a lot more about...

I recently created an application that started with the appfuse stack. Everything performed admirably, until I created a page with numerous form elements (~30K)that was large (~38M when saved to disk). The page would either cause an OutOfMemory (OOM) error or would take 3+ minutes for the first byte download. Here's what I did to bring full page load times to < 15s.

I hadn't used WSAD in debug mode in quite some time. I always found that the debugger was a memory hog and quite slow. On a whim, I clicked the enable hot method replace option in my test server and lo and behold the debugger was running as fast and as lean (*cough*) as the normal runtime! Then it broke...

Heinz writes The Java Specialists' Newsletter. In his latest issue he offers up a little program that will test CPU efficiency...

Recently I encountered a nasty little runtime bug in java. I call it a bug even though the java.sql.Timestamp javadoc has a Note explaining why.

How can I easily dump http POST parameters using JSTL? It is super easy...