Uncategorized

External configuration for SelfDiagnose

Initialization of the SelfDiagnose component is done by reading the resource selfdiagnose.xml which must be located on the classpath of the Web application. This configuration declares the diagnostic tasks that are executed in the context of the Web application. The upcoming release (1.1) will have a new feature that allows you to override the local configuration and dynamically load the configuration from a provided URL: http://your-app/selfdiagnose?config=http://some-other-server/selfdiagnose.xml or even a local file can be passed: http://your-app/selfdiagnose?

Foreign compile-time dependencies in SelfDiagnose

In the upcoming release 1.1 of the SelfDiagnose task library, a new task has been added called CheckEndecaService. Endeca is commercial software that provides excellent Search services to e.g. e-commerce web applications. This particular task checks the availability of that service and can perform a simple query. To implement this, the following snippet has been used: HttpENEConnection connection = new HttpENEConnection(); connection.setHostname(host); connection.setPort(port); UrlENEQuery eneQuery = new UrlENEQuery(“N=0”, “UTF-8”); ENEQueryResults eneResults = connection.

QuickSilver and Current Application

On a Mac, accessing the current application from QuickSilver provides interesting new possibilities as can been on an episode of the Merlin Show. If you agree that this is something you wanted all along, then follow these instructions to set it up. (Thanks to BOONE). In QS prefs, make sure “Enable advanced features” is checked In QS Plug-ins, enable the User Interface plugin In MacOSX System Preferences–>Universal Access, check “Enable access for assitive devices” In QS prefs–>Catalog–>Quicksilver, check and reload “Proxy Objects”

s3browse.com

For some time now, Amazon S3 Web Services are available to the developer community. Since its inception, several client solutions made their way to the public. S3Browse.com provides both a simple Web Interface and a Java Web Start based client to your S3 accounts. The web client is typically used to create and browse your bucket contents. The Java client is used to upload large files or a large amount of files.