Wednesday, March 09, 2005
Tuesday, March 08, 2005
The Grinder, a Java Load Testing Framework
The Grinder, a Java Load Testing Framework
What is The Grinder?
The Grinder is a JavaTM load-testing framework. It is freely available under a BSD-style open-source license.
The Grinder makes it easy to orchestrate the activities of a test script in many processes across many machines, using a graphical console application. Test scripts make use of client code embodied in Java plug-ins. Most users of The Grinder do not write plug-ins themselves, instead they use one of the supplied plug-ins. The Grinder comes with a mature plug-in for testing HTTP services, as well as a tool which allows HTTP scripts to be automatically recorded.
The Grinder was originally developed for the book Professional Java 2 Enterprise Edition with BEA WebLogic Server by Paco Gómez and Peter Zadrozny. Philip Aston took ownership of the code and reworked it to create The Grinder 2. Philip continues to enhance and maintain The Grinder, and welcomes all contributions. Recently Peter, Philip and Ted Osborne have published the book J2EE Performance Testing which makes extensive use of The Grinder.
The next major version of The Grinder, The Grinder 3 is currently available as a beta quality release. The Grinder 3 uses the powerful scripting language Jython, and allows any Java code to be tested without the need to write a plug-in.
The latest news, downloads, and mailing list archives can be found on SourceForge.net.
What is The Grinder?
The Grinder is a JavaTM load-testing framework. It is freely available under a BSD-style open-source license.
The Grinder makes it easy to orchestrate the activities of a test script in many processes across many machines, using a graphical console application. Test scripts make use of client code embodied in Java plug-ins. Most users of The Grinder do not write plug-ins themselves, instead they use one of the supplied plug-ins. The Grinder comes with a mature plug-in for testing HTTP services, as well as a tool which allows HTTP scripts to be automatically recorded.
The Grinder was originally developed for the book Professional Java 2 Enterprise Edition with BEA WebLogic Server by Paco Gómez and Peter Zadrozny. Philip Aston took ownership of the code and reworked it to create The Grinder 2. Philip continues to enhance and maintain The Grinder, and welcomes all contributions. Recently Peter, Philip and Ted Osborne have published the book J2EE Performance Testing which makes extensive use of The Grinder.
The next major version of The Grinder, The Grinder 3 is currently available as a beta quality release. The Grinder 3 uses the powerful scripting language Jython, and allows any Java code to be tested without the need to write a plug-in.
The latest news, downloads, and mailing list archives can be found on SourceForge.net.
Monday, March 07, 2005
PMD - Problem finder in Java Source Code
PMD - PMD
PMD scans Java source code and looks for potential problems like:
* Empty try/catch/finally/switch blocks
* Unused local variables, parameters and private methods
* Empty if/while statements
* Overcomplicated expressions - unnecessary if statements, for loops that could be while loops
* Classes with high Cyclomatic Complexity measurements
PMD has plugins for JDeveloper, Eclipse, JEdit, JBuilder, Omnicore's CodeGuide, NetBeans/Sun ONE Studio, IntelliJ IDEA, TextPad, Maven, Ant, Gel, JCreator, and Emacs.
PMD scans Java source code and looks for potential problems like:
* Empty try/catch/finally/switch blocks
* Unused local variables, parameters and private methods
* Empty if/while statements
* Overcomplicated expressions - unnecessary if statements, for loops that could be while loops
* Classes with high Cyclomatic Complexity measurements
PMD has plugins for JDeveloper, Eclipse, JEdit, JBuilder, Omnicore's CodeGuide, NetBeans/Sun ONE Studio, IntelliJ IDEA, TextPad, Maven, Ant, Gel, JCreator, and Emacs.
Sunday, March 06, 2005
Saturday, March 05, 2005
Friday, March 04, 2005
Thursday, March 03, 2005
JDBC URL for direct Connection to an Access database
If you want to connect to an Access Database File (*.mdb file) without creating an DSN entry in the system, you can enter all needed informations directly in the JDBC URL. Here is an example for the German Access driver
jdbc:odbc:Driver={Microsoft Access-Treiber (*.mdb)};dbq=D:\temp\example.mdb;uid=Admin
Replace the driver name you usually use in the DSN configuration and the concrete path to the mdb file and you should be able to access to the access file via JDBC.
Hope this hint helps.
Comments are welcome.
jdbc:odbc:Driver={Microsoft Access-Treiber (*.mdb)};dbq=D:\temp\example.mdb;uid=Admin
Replace the driver name you usually use in the DSN configuration and the concrete path to the mdb file and you should be able to access to the access file via JDBC.
Hope this hint helps.
Comments are welcome.
Wednesday, March 02, 2005
Saturday, February 26, 2005
NekoHTML
NekoHTML
NekoHTML is a simple HTML scanner and tag balancer that enables application programmers to parse HTML documents and access the information using standard XML interfaces. The parser can scan HTML files and "fix up" many common mistakes that human (and computer) authors make in writing HTML documents. NekoHTML adds missing parent elements; automatically closes elements with optional end tags; and can handle mismatched inline element tags.
NekoHTML is written using the Xerces Native Interface (XNI) that is the foundation of the Xerces2 implementation. This enables you to use the NekoHTML parser with existing XNI tools without modification or rewriting code.
NekoHTML is a simple HTML scanner and tag balancer that enables application programmers to parse HTML documents and access the information using standard XML interfaces. The parser can scan HTML files and "fix up" many common mistakes that human (and computer) authors make in writing HTML documents. NekoHTML adds missing parent elements; automatically closes elements with optional end tags; and can handle mismatched inline element tags.
NekoHTML is written using the Xerces Native Interface (XNI) that is the foundation of the Xerces2 implementation. This enables you to use the NekoHTML parser with existing XNI tools without modification or rewriting code.
Tuesday, February 22, 2005
Sunday, February 20, 2005
Monday, February 14, 2005
ProGuard
ProGuard
ProGuard is a free Java class file shrinker, optimizer, and obfuscator. It can detect and remove unused classes, fields, methods, and attributes. It can then optimize bytecode and remove unused instructions. Finally, it can rename the remaining classes, fields, and methods using short meaningless names. The resulting jars are smaller and harder to reverse-engineer.
ProGuard is a free Java class file shrinker, optimizer, and obfuscator. It can detect and remove unused classes, fields, methods, and attributes. It can then optimize bytecode and remove unused instructions. Finally, it can rename the remaining classes, fields, and methods using short meaningless names. The resulting jars are smaller and harder to reverse-engineer.
Saturday, February 12, 2005
Welcome to Muse!
Welcome to Muse!: "Overview
Muse is a robust Java implementation of the Management using Web Services (MuWS) 0.5 specification and the underlying WS-* specifications it is based upon. The next major release of Muse, targeted for March 2005, will be an implementation of the soon-to-be-released MuWS 1.0 specification."
Muse is a robust Java implementation of the Management using Web Services (MuWS) 0.5 specification and the underlying WS-* specifications it is based upon. The next major release of Muse, targeted for March 2005, will be an implementation of the soon-to-be-released MuWS 1.0 specification."
TestNG
TestNG
TestNG is a testing framework inspired from JUnit and NUnit but introducing some new functionalities that make it more powerful and easier to use, such as:
* JSR 175 Annotations (JDK 1.4 is also supported with JavaDoc annotations).
* Flexible test configuration.
* Default JDK functions for runtime and logging (no dependencies).
* Powerful execution model (no more TestSuite).
* Supports dependent methods.
I started TestNG out of frustration for some JUnit deficiencies which I have documented on my weblog here, here and in particular, here. Reading these entries might give you a better idea of the goal I am trying to achieve with TestNG. You can also check out a quick overview of the main features and an article describing a very concrete example where the combined use of several TestNG's features provides for a very intuitive and maintainable testing design.
TestNG is a testing framework inspired from JUnit and NUnit but introducing some new functionalities that make it more powerful and easier to use, such as:
* JSR 175 Annotations (JDK 1.4 is also supported with JavaDoc annotations).
* Flexible test configuration.
* Default JDK functions for runtime and logging (no dependencies).
* Powerful execution model (no more TestSuite).
* Supports dependent methods.
I started TestNG out of frustration for some JUnit deficiencies which I have documented on my weblog here, here and in particular, here. Reading these entries might give you a better idea of the goal I am trying to achieve with TestNG. You can also check out a quick overview of the main features and an article describing a very concrete example where the combined use of several TestNG's features provides for a very intuitive and maintainable testing design.
Thursday, February 10, 2005
Tribe - Home Page
Tribe - Home Page
Tribe is a Java-based group communication library. It is based on reliable point-to-point FIFO communication channels (basically TCP) and targets high performance cluster environments. Unlike JGroups, Tribe only targets reliable multicast (no probabilistic delivery) and is optimized for cluster communications.
Tribe is a Java-based group communication library. It is based on reliable point-to-point FIFO communication channels (basically TCP) and targets high performance cluster environments. Unlike JGroups, Tribe only targets reliable multicast (no probabilistic delivery) and is optimized for cluster communications.
Wednesday, February 09, 2005
Sunday, February 06, 2005
Saturday, February 05, 2005
Wednesday, February 02, 2005
Tuesday, February 01, 2005
Sunday, January 30, 2005
Friday, January 28, 2005
Tuesday, January 25, 2005
Monday, January 24, 2005
Sunday, January 23, 2005
LogWeb - LogWeb
LogWeb - LogWeb: "LogWeb is a web interface for configuring Log4J at runtime within a servlet container.
In response to numerous requests, LogWeb has been restructured to make it easier to incorporate LogWeb as a 3rd party component within your web-apps. The installation document outlines the different ways to install logweb."
In response to numerous requests, LogWeb has been restructured to make it easier to incorporate LogWeb as a 3rd party component within your web-apps. The installation document outlines the different ways to install logweb."
Friday, January 21, 2005
Thursday, January 20, 2005
Verwendung von "SQLConfigDataSource" zur Erstellung eines Access-System-DSN
Verwendung von "SQLConfigDataSource" zur Erstellung eines Access-System-DSN
These parameters can also be used directly in the JDBC URL!
See also
SUN Java Forum Message
These parameters can also be used directly in the JDBC URL!
See also
SUN Java Forum Message
Wednesday, January 19, 2005
Monday, January 17, 2005
Friday, January 14, 2005
Lift-Off Java-Installer
Lift-Off Java-Installer
Vergleiche dazu auch den bereits am Friday, August 27, 2004 im Blog erwähnten IZPack Installer
IZ Pack Blog Eintrag
Vergleiche dazu auch den bereits am Friday, August 27, 2004 im Blog erwähnten IZPack Installer
IZ Pack Blog Eintrag
Drools - Home
Drools - Home
Drools is an augmented implementation of Forgy's Rete algorithm tailored for the Java language. Adapting Rete to an object-oriented interface allows for more natural expression of business rules with regards to business objects.
More importantly, Drools provides for Declarative Programming and is flexible enough to match the semantics of your problem domain. The various parts that compose a rule may be extended to lend domain-specific sense to the rule.
Drools is an augmented implementation of Forgy's Rete algorithm tailored for the Java language. Adapting Rete to an object-oriented interface allows for more natural expression of business rules with regards to business objects.
More importantly, Drools provides for Declarative Programming and is flexible enough to match the semantics of your problem domain. The various parts that compose a rule may be extended to lend domain-specific sense to the rule.
Thursday, January 13, 2005
CementJ
CementJ
CementJ alpha will be released soon…………...
CementJ is a Java™ API that provides functionality needed by most Java™/J2EE™ applications that isn't yet provided by the JDK specification directly. In other words, this API is a foundation that fills the gaps between the JDK and applications you code. Functionality includes:
*
Base abstracts for Data Transfer Objects, Data Access Objects, Bean/RMI clients, Application exceptions, and others that can be easily extended and used.
*
Many static utilities that turn many common tasks into coding one-liners (JDBC, Date routines, EJB routines, etc.)
*
A JDBC layer that provides enhanced exception information for easy problem diagnostics and performance tuning information.
*
Collection augmentations and enhancements.
*
Many other generic/useful common utilities.
All utilities in CementJ adhere to the following principles:
*
All utilities strive to be one-liners to save you coding time.
*
No complex or lengthy set-up procedures that cost you time.
*
All exceptions originating from CementJ are Runtime exceptions -- we don't force you into numerous try/catch blocks unless you want them.
*
All arguments are validated with meaningful error messages to reduce the number of derivative exceptions and save you time.
CementJ is featured in the forthcoming book The J2EE Architect's Handbook : How to Be a Successful Architect for J2EE Applications to be released by DVT Press in June, 2004.
CementJ alpha will be released soon…………...
CementJ is a Java™ API that provides functionality needed by most Java™/J2EE™ applications that isn't yet provided by the JDK specification directly. In other words, this API is a foundation that fills the gaps between the JDK and applications you code. Functionality includes:
*
Base abstracts for Data Transfer Objects, Data Access Objects, Bean/RMI clients, Application exceptions, and others that can be easily extended and used.
*
Many static utilities that turn many common tasks into coding one-liners (JDBC, Date routines, EJB routines, etc.)
*
A JDBC layer that provides enhanced exception information for easy problem diagnostics and performance tuning information.
*
Collection augmentations and enhancements.
*
Many other generic/useful common utilities.
All utilities in CementJ adhere to the following principles:
*
All utilities strive to be one-liners to save you coding time.
*
No complex or lengthy set-up procedures that cost you time.
*
All exceptions originating from CementJ are Runtime exceptions -- we don't force you into numerous try/catch blocks unless you want them.
*
All arguments are validated with meaningful error messages to reduce the number of derivative exceptions and save you time.
CementJ is featured in the forthcoming book The J2EE Architect's Handbook : How to Be a Successful Architect for J2EE Applications to be released by DVT Press in June, 2004.
Wednesday, January 12, 2005
JSP dynamischer Inhalt in Custum Tag Attribute : Error
Ich habe beim Einfuegen eines dynamischen Inhalts (Request Time Expressions a la <%= variable %> in einen Custum Tag die Fehlermeldung:
etc erhalten. Hier ein paar andere Links die im Netz zu diesem Thema zu finden waren:
Re: einfache jsp Problem: "c_rt.tld"
Scheinbar hat folgender Eintrag in der web.xml etwas damit zu tun:
#
#
#http://java.sun.com/jstl/core_rt
#/WEB_INF/c_rt.tld
#
#
Mail Reader Servlet / c_rt.tld
=> Lösung:
Entscheident war wohl das einfügen eines speziellen Tags innerhalb der TAG Definition:
(Ich hatte leider Probleme den ganzen XML Code hier in Blogger schoener zu posten, das mit der Textarea hat auch nicht richtig geklappt - leider)
etc erhalten. Hier ein paar andere Links die im Netz zu diesem Thema zu finden waren:
Re: einfache jsp Problem: "c_rt.tld"
Scheinbar hat folgender Eintrag in der web.xml etwas damit zu tun:
#
#
#
#
#
#
Mail Reader Servlet / c_rt.tld
=> Lösung:
Entscheident war wohl das einfügen eines speziellen Tags innerhalb der TAG Definition:
(Ich hatte leider Probleme den ganzen XML Code hier in Blogger schoener zu posten, das mit der Textarea hat auch nicht richtig geklappt - leider)
Sunday, January 09, 2005
jSyncManager for Palm PDA's
jSyncManager
The jSyncManager is a open source, Java implementation of a HotSync compatible protocol stack, set of data abstraction objects, development tools, and applications allowing developers and end-users to synchronize Palm devices with any Java based system. HotSync your Palm with jSyncManager and Java.
The jSyncManager is a open source, Java implementation of a HotSync compatible protocol stack, set of data abstraction objects, development tools, and applications allowing developers and end-users to synchronize Palm devices with any Java based system. HotSync your Palm with jSyncManager and Java.
Saturday, January 08, 2005
Thursday, January 06, 2005
User/PW Protection for MS ACCESS and Java JDBC connections
1) First get a new MS ACCESS database
2) make the database password protected by using the Tools/Security/User-Level Security Wizard.
By doing this a file secured.mdw for example is created
3) Create a User Data Source which points to the mdb file and choose the system database option and select the mdw file there. Enter no user and password in the user data source definition (under advanced options)
4) Connect to the database via JDBCODBC Bridge as usual and enter user and password during getConnection
The important hint for this doing was found at
dBforums - JDBC Microsoft Access
2) make the database password protected by using the Tools/Security/User-Level Security Wizard.
By doing this a file secured.mdw for example is created
3) Create a User Data Source which points to the mdb file and choose the system database option and select the mdw file there. Enter no user and password in the user data source definition (under advanced options)
4) Connect to the database via JDBCODBC Bridge as usual and enter user and password during getConnection
The important hint for this doing was found at
dBforums - JDBC Microsoft Access
Wednesday, January 05, 2005
Tuesday, January 04, 2005
Resin(tm) Core
Resin(tm) Core
Resin is a fast servlet and JSP engine supporting load balancing for increased reliability. Resin encourages separation of content from style with its XSL support. Servlets can generate simple XML and use an XSL filter to format results for each client's capability, from palm pilots to Mozilla.
Resin is a fast servlet and JSP engine supporting load balancing for increased reliability. Resin encourages separation of content from style with its XSL support. Servlets can generate simple XML and use an XSL filter to format results for each client's capability, from palm pilots to Mozilla.
Sunday, January 02, 2005
Friday, December 31, 2004
Wednesday, December 29, 2004
Wednesday, December 22, 2004
Monday, December 20, 2004
Sunday, December 12, 2004
Saturday, December 11, 2004
Subscribe to:
Posts (Atom)