As I dig into a new technology I realize how ridiculous your average techie must sound saying JAVA-TLA this and JAVA-YABA that. I feel ridiculous right now as try and do more and more with the JAVA-SOAP API and begin to file away yet another set of acronyms in my little head.

First one is the JWS file. JWS files are the "quick and dirty" approach to SOAP applications with the emphasis on "dirty". It deploys like an HTML or JSP file in the web application directory and, like a JSP, is compiled on the fly. Unlike JSP, it has no redeeming features and probably shouldn't ever be used.

Once I realized that JWS sucked, I specified my service in a the site-wide WSDD file, which goes into WEB-INF/server-config.wsdd. The overall implementation I'm working on allows you to submit remote jobs on a server much the way that a queueing system works. So here is the WSDD code that I wrote to do that.