Projects tagged ‘jmx’ and ‘spring’

Scriptella is an ETL (Extract-Transform-Load) and script execution tool. Its primary focus is simplicity. It doesn't require the user to learn another complex XML-based language to use it, but allows ... [More] the use of SQL or another scripting language suitable for the data source to perform required transformations. Main features: * Simple and minimalistic XML syntax for ETL scripts. * Built-in providers for JDBC, CSV, Text, XML, LDAP, Lucene and Velocity. * Support for many useful JDBC features, e.g. parameters in SQL including file blobs and JDBC escaping. * Easy-to-Use as a standalone tool or Ant task. No deployment/installation required. Easy-To-Run ETL files directly from Java code. * Seamless integration with Java/Java EE and Spring [Less]

This project cames from Xuefeng's book "Spring 2.0 Core Technology and Best Practice" which is a completely ready-to-run example of JavaEE web application based on Spring framework. This online ... [More] bookstore web application based on light-weight Spring framework, integration of Acegi, Hibernate, XFire, Velocity, OSCache, Compass and Lucene. Snapshot: [Less]

Java Simon - Simple Monitoring API Java Simon is a simple monitoring API that allows you to follow and better understand your application. Monitors (familiarly called Simons) are placed directly ... [More] into your code and you can choose whether you want to count something or measure time/duration. Current version 2 provides basic monitor functionality, extensibility via Callbacks, JMX and Spring integration tools and also easy to use JDBC proxy driver that measures JDBC performance and can log all statements too. Version 2.1 was released on July 23rd, 2009. [Less]

Project BroadwayProject Broadway is an extensible and customizable monitoring API. Broadway lets developers easily create monitor components to observe pre-defined conditions and specify how to react ... [More] when these conditions are encountered. At its core, Broadway lets developers separate the monitoring concerns from the observed resources. It has a flexible design, which allows it to work in any context where JavaBean-style getter property values can be read either directly through in-VM method invocation or through some detached mechanism (i.e. proxy, reflection, rmi, jmx, web service, etc). Broadway's simplified design offers two major high level components: a Monitor and an Action components. The Monitor lets you specify the resources to monitor and an expression (default expression language is Groovy) used to monitor these resources . The Action component specifies the action to execute when a specified monitored states are realized at a given time. Broadway OffersEasy to learn non-invasive API. Maintains clean separation between monitors and monitored resources. Simplified design to allow maximum flexibility by API user. High level components such as monitors and actions use sensible defaults. Ability to monitor both in-VM and distributed resources. API with rich level of programmability through a monitor DSL. Support for programmability through dependency injection (i.e. Spring Framework, etc) Support for native JMX integration using Monitor and Action MBeans. Leverages existing frameworks including JavaBean, JMX, Java scripting, Apache BSF, etc. Support expressive monitoring rules using scripting language (default is Groovy) Create compound monitoring expressions to observe multiple resources which can be in different contexts. Architecture allows plug-in of different scripting engines supported Apache BSF (default is Groovy). Scripted action components to execute script files to handle monitoring action when monitored conditions are realized. Ready to Get Started ?Here are few links to get you Started with Broadway Download Broadway and Broadway-Tutorial (see Featured Download links) BroadwayJavaTutorial - Introductory tutorial to Broadway. BroadwayMonitorDSL - Explores how to use Broadway DSL to create monitors. BroadwayAndSpring - See how to use Broadway and Spring. BroadwayAndJavaManagement - Use Broadway to monitor Java platform management beans. BroadwayAndJMX - Use JMX to build distributed monitoring agents. Contact For all feedbacks, reach me at vmatters at gmail. [Less]

Java Simon - Simple Monitoring APIJava Simon is a simple monitoring API that allows you to follow and better understand your application. Monitors (familiarly called Simons) are placed directly into ... [More] your code and you can choose whether you want to count something or measure time/duration. NewsJuly 23rd, 2009 - Version 2.1This is a minor update of version 2 based on some user's input: added methods reset and two versions of sampleAndReset to SimonMXBean; you can now use [, ], and _ in Simon names; timestamps for 0 are formated as undef in toString methods. Download on the right side of the page, we also updated Javadoc for a few JMX classes - see JavaDoc for v2.1. We thank our users for their support and feedback! June 19th, 2009 - Version 2 out!After few more fixes, some simplifications (ever used StatProcessor? it's gone!), more Javadocs and some Wiki updates (with some more ahead) we have finally released version 2 of Java Simon library. You can choose the big package with precompiled JARs, Javadocs (here online) and working Ant build - or if you're Maven user, you can go for smaller sources-only ZIP with Maven build (Maven 2.1 is required). Check the right side of the page for both downloads. Enjoy - and tell us what you think! May 20th, 2009 - Version 2, Beta 2Yup, we're slower than we anticipated - especially because we really wanted to wrap it up faster for our own sake as well. This time the whole source structure is Maven 2 compliant and you should be able to compile the project and install all Java Simon artifacts into your repository. We still have to finish deployment to online repository and besides that there are some documentation tasks pending as well. May 6th, 2009 - Fighting with Maven 2 ;-)We are finishing second beta (check trunk if you're adventurous) with Maven 2 build. As the core developers are not familiar with Maven we have a problem to build the project properly with all dependencies (especially half of the JARs need JDK 5, the other JDK 6 ;-)). If you don't need Maven, simply download the first beta - final version is going to be very similar except for the project structure. API, JARs, features... we will not change this unless some vis major occasion. Older news: All news can be found here. News on this page (Google code) might be rephrased or shortened. ;-) DocumentationCheck out the list of our Wiki pages where you may also find: Introduction - where Java Simon API is positioned and the motivation for it GettingStarted - how to start with Java Simon along with some examples Callbacks - new important feature of v2 to extend Java Simon functions with your own code MavenSupport - for Maven 2 users Other resources: Javadocs for v2 About Java Simon - on javasimon.org Visit and join our mailing list on Google Groups: http://groups.google.com/group/javasimon Some part of the documentation relates to v1 which is not officially supported anymore (sounds strange but there are reasons for that). MotivationWe wanted to use something like JAMon for our products originally, but we lacked two important features: better way (or any way for that matter) to organize all those monitors; nanosecond resolution. Monitor hierarchySimon API gives you a better control over all those monitors in your big - possibly Java EE - application. Simons are organized in a hierarchy similar to what you can see in java.util.logging API. Simons can be disabled which minimizes their overhead influencing your application. These operations can be performed on the whole subtrees of Simons which makes partial application monitoring easier. See SimonHierarchy for more. The time for nanos is hereSimon measures times in nanos - and believe it or not it can make the difference on current very fast machines. Although not all platforms provide timers precise enough this design decision is future proof. Of course this decision comes with a price - you can use Java Simon only with JDK 1.5 or higher (platform Java SE 5). See SystemTimersGranularity page for more. Future plansOur future goals include (the later goals are in a more distant future): Sampling, collecting, agregating with persistence backend (file/DB). VisualVM plugin. Dynamic profiling integration. Currently the project is rather on hold - but this depends on other free-time activities of the authors and also on public demand and feedback. We're not preparing v3 right now, we're ready to tweak version 2 though. Do you have something to tell us?So tell us! Visit our Google Group (preferably) or file an issue, whatever. We can't promise to fulfill all your dreams but we want to produce the library YOU like (and so do we - of course ;-)). So if you know how to make Simon better, without making it something it is not, let us know! We want to know. [Less]

ZenTrackerTroubleshooting and development tool allowing to transparently monitor Hibernate activity, in order to gather sufficient information to start an optimization process : Entity statistics ... [More] (select, insert, update, delete) sorted by type Collection modifications, logging the add and removal of entities Logging the dirty properties (entity, property, previous and new values) Tracking execution times of SQL queries (max, min and average) without any third-party JDBC tool Version 1.xThe version 1.x of ZenTracker has the following new features : Spring integration : Making ZenTracker work is as simple as adding a bean definition in the applicationContext.xml JMX Integration out of the box for gathering the statistics No need to modify an existing Hibernate interceptor On web environm [Less]

java-commons-1.2.0 released!!!Changes in version 1.2.0 (2009-10) This is the list of the issues fixed in this version: - Update maven2-parent dependency - Refactoring of NamingManager - Create ... [More] the JMXManager class - Add methods to ReflectionHelper class - Create AbstractPK class (commons-persistence) - Create AbstractEntity class (commons-persistence) - Adds getMidnight to DateHelper (commons-core) - Create AbstractDAO class for JPA based applications (commons-persistence) What is java-commons?"java-commons" is a bunch of tools that allow developers to build java applications. The project is divided into several modules: 1. commons-core This is the main module of the project. It provides classes to work with Dates, Calendars, Emails, Localization... A flexible objects registry can also be found in this module. For more informations (documentation, samples, ...) about the commons-core module, please refer to this wiki page. 2. commons-security This module provides classes to work with Java cryptography API. For more informations (documentation, samples, ...) about the commons-security module, please refer to this wiki page. 3. commons-server This module provides classes to use in your service layer. You will find classes to help you to work with several JEE technologies like: EJB, JMS, JMX, Naming... In the future release, you will find an exceptions framework built around ApplicationException and SystemException concept. For more informations (documentation, samples, ...) about the commons-core module, please refer to this wiki page. 4. commons-persistence For this moment, this module provides only classes to work with JPA (Java Persistence API). For more informations (documentation, samples, ...) about the commons-persistence module, please refer to this wiki page. 5. commons-w3c This module provides classes to work with W3C related API. In this module, you can find, for example, classes to make XSL transformations. TODO --> For more informations (documentation, samples, ...) about the commons-w3c module, please refer to this wiki page. 6. commons-web This module provides classes to work with Web technologies. Several classes to work with JSF (Java Server Faces) can be found in this module. TODO --> For more informations (documentation, samples, ...) about the commons-web module, please refer to this wiki page. Getting Started1. Without maven2 Download the java-commons distribution (java-commons-{project.version}.zip) and add the wanted jars in your classpath. These jars can be found in the 'dist' directory of the distribution. 2. With maven2 In order to add java-commons dependencies in your project, you have to add the following lines in your pom.xml file. Theses lines are very important because they allow maven to locate the java-commons repository. sempere-plugin-repository http://www.sempere.org/maven2-repository/ sempere-repository http://www.sempere.org/maven2-repository/ Finally, add the wanted java-commons dependencies in your pom.xml file: org.sempere.commons commons-core ${commons.version} ...Have fun!! [Less]