MoonBlog, le blog qui te regarde!

BuildProcess, a complete J2EE deployment toolbox:

BuildProcess is a set of tools designed to automatic perform J2EE tasks : * AutoDeploy is the main J2EE deployment tool. The J2EE administrator describes the list of network environments (application server, applications, database, etc) in a main XML file. This XML file can be modified by hand or using WebAutoDeploy, the web admin console. Periodically, AutoDeploy read this description file and update the environment. More informations. * BuildEraser is an automatic file deletion tool. The disk space saturation is a classical problem for J2EE administrators. In fact, application server and J2EE applications generate a lot of files (log file, temporary files, etc). On the other hand, automatic build tools such as CruiseControl or AntHill, generate log files too. BuidEraser provides a multi-OS, automatic and networked way to delete files. WebBuildEraser is the web admin console of BuildEraser. More informations. * AsMon is a web application which store description of all J2EE environments that the administrator need to manage. It store a lot of data such as the application server description (type, host, network port in use, etc), database description, application description (URI, version, etc), etc. AsMon can import data from the AutoDeploy XML file but has a discover system included : the administrator defines a network mask and AsMon sniff all IP address/network ports in the netmask to discover application server. AsMon includes monitoring tools to know if the environment is available or not and what is the status. More informations. * BugzillaPublisher is a publisher for CruiseControl automatic build tool. It takes modifications set comments and add the build number in the bug description. More informations. * MVeloce is a technical framework used in all web based application of BuildProcess suite. MVeloce is a MVC2 framework which use Apache Jakarta Velocity for the view part. More informations.

Damien Katz: Error codes or Exceptions? Why is Reliable Software so Hard?:

Error codes or exceptions? Like static vs. dynamic programming languages or how great David Hasselhoff is (most people say great, I say super-great), it tends to turn into a pointless argument (”Hasselhoff is super-great ASSHOLE!”). Very little software really gets error handling right. Even many critical, backend server systems tend to break under heavy loads. And the vast majority of end-user applications handle errors gracefully only for the most well understood, commonly encountered conditions (e.g. HTTP timeout), but very poorly for most other conditions (failed allocations, bad data, I/O errors, missing files, etc). When these sorts of errors occur, bad things happen. Bad bad things. Like when my web browser crashes, taking one half-composed email and 8 open web pages with it. Why did a single flaw cause so much damage? I use Firefox and it’s pretty reliable compared to most applications. It’s engineered impressively, with logical program layers well separated and a great deal of the application logic is written in JavaScript, a high-level “safe” programming language. But occasionally it still just crashes or locks up.

AccessPDF – A PDF Forum for Users and Programmers:

If PDF is electronic paper, then pdftk is an electronic staple-remover, hole-punch, binder, secret-decoder-ring, and X-Ray-glasses. Pdftk is a command-line tool for doing everyday things with PDF documents. Keep one in the top drawer of your desktop and use it to: * Merge PDF Documents * Split PDF Pages into a New Document * Decrypt Input as Necessary (Password Required) * Encrypt Output as Desired * Fill PDF Forms with FDF Data and/or Flatten Forms * Apply a Background Watermark * Report on PDF Metrics such as Metadata, Bookmarks, and Page Labels * Update PDF Metadata * Attach Files to PDF Pages or the PDF Document * Unpack PDF Attachments * Burst a PDF Document into Single Pages * Uncompress and Re-Compress Page Streams * Repair Corrupted PDF (Where Possible) Pdftk allows you to manipulate PDF easily and freely. It does not require Acrobat, and it runs on Windows, Linux, Mac OS X, FreeBSD and Solaris. Pdftk is free software (GPL).

Cool Solutions Wiki Main Page – CoolSolutionsWiki:

Welcome to the Cool Solutions Wiki. Please feel free to join in. You can read anything in here without logging in, but if you feel like commenting on something, or starting a new thread, you’ll need to use a Novell Login account (which you’ll be prompted to create if you don’t already have one). If you’ve used a wiki before, you’ll have no trouble getting used to this format. If not, you should take a minute to learn more about it. We think this is going to be a great new addition to our Cool Solutions offerings, providing an easier way for the community to collaborate on solutions, correct mistakes, add sample code, etc. We look forward to seeing what you have to say in here.

eGroupWare: Home:

The eGroupWare project is pleased to announce the next major release of its collaboration suite, eGroupWare. After 20 months of active development, it comes with blazing new features and many improvements for usability and performance. The user interface for the major applications has been extensively harmonized, giving the user a more intuitive way to do their daily work. Through the use of new programming techniques and technologies, this new release has become notably faster. The newly-integrated SyncML Server makes eGroupWare now compatible with MS Outlook, Evolution, Palm and many mobile phones. The concept of “links” was extended to a broader range of applications. This allows users to create information pools with linked information from different sources. Version 1.2 now is more flexible and customizable to fit small and mid-sized companies needs without changing code. For a more detailed description of new applications and features, see the release notes.

TechWeb | News | Top 10 Windows XP Tips Of All Time:

Despite all the hoopla about the introduction of Windows Vista, the truth of the matter is that the new OS isn’t due for at least another seven to nine months — and it will probably be even longer before most of us start adopting it. Meanwhile, we’ve still got to deal with Win XP. In order to make the waiting easier, we’ve decided to assemble the greatest tips in the history of Windows XP. Here you’ll find the tips that give you the most bang for your buck; that are most useful in terms of security, functionality, and PC performance; and that are just plain cool.

java.net: Exception-Handling Antipatterns:

E-mail Print Discuss Blog Exception-Handling Antipatterns Exception-Handling Antipatterns by Tim McCune 04/06/2006 * Contents * Basic Exception Concepts * Creating Your Own Exceptions * Exceptions and Transactions o EJB 2 o EJB 3 o Message-Driven Beans * Logging * Antipatterns o Log and Throw o Throwing Exception o Throwing the Kitchen Sink o Catching Exception o Destructive Wrapping o Log and Return Null o Catch and Ignore o Throw from Within Finally o Multi-Line Log Messages o Unsupported Operation Returning Null o Ignoring InterruptedException o Relying on getCause() * Conclusion * Resources Should you throw an exception, or return null? Should you use checked or unchecked exceptions? For many novice to mid-level developers, exception handling tends to be an afterthought. Their typical pattern is usually a simple try/catch/printStackTrace(). When they try to get more creative, they usually stumble into one or more common exception handling antipatterns. The antipattern concept became popular in the software development community with the release of AntiPatterns: Refactoring Software, Architectures, and Projects in Crisis in 1998. An antipattern draws on real-world experience to identify a commonly occurring programming mistake. It describes the general form of the bad pattern, identifies its negative consequences, prescribes a remedy, and helps define a common vocabulary by giving each pattern a name. In this article, we’ll discuss some fundamental concepts about the different types of Java exceptions and their intended uses. We’ll also cover basic logging concepts, especially as they relate to exception handling. Finally, instead of prescribing what to do, we’ll focus on what not to do, and take a look at a dozen common exception-handling antipatterns that you are almost certain to find somewhere in your code base.