PojoCache is an in-memory, transactional, and replicated POJO (plain old Java object) cache system that allows users to operate on a POJO transparently without active user management of either replication or persistency aspects. This tutorial focuses on the usage of the PojoCache API.
JBoss Tattletale is a tool that can help you get an overview of the project you are working on or a product that you depend on.
The tool will provide you with reports that can help you
* Identify dependencies between JAR files
* Find missing classes from the classpath
* Spot if a class is located in multiple JAR files
* Spot if the same JAR file is located in multiple locations
* With a list of what each JAR file requires and provides
* Verify the SerialVersionUID of a class
* Find similar JAR files that have different version numbers
* Find JAR files without a version number
* Locate a class in a JAR file
* Get the OSGi status of your project
* Remove black listed API usage
JBoss Tattletale will recursive scan the directory pass as the argument for JAR files and then build the reports as HTML files.
The main HTML file is: index.html
JBoss Tattletale is licensed under GNU Lesser General Public License (LGPL) version 2.1 or later.
We hope that JBoss Tattletale will help you in your development tasks !
Reports
* Dependants
* Depends On
* Graphical Dependencies
* Transitive Dependants
* Transitive Depends On
* Class Location
* OSGi
* Eliminate Jar files with different versions
* Invalid version
* Multiple Jar files
* Multiple Locations
* No version
* Black listed API
* JAR archive
Jopr is an enterprise management solution for JBoss middleware projects and other application technologies. This pluggable project provides administration, monitoring, alerting, operational control and configuration in an enterprise setting with fine-grained security and an advanced extension model. This system is based on and plugin-compatible with the multi-vendor RHQ management project. It provides support for monitoring base operating system information on six operating systems as well as mangement of Apache, JBoss Application Server and other related projects.
If you use NetBeans and JBoss, you've probably noticed that you can't register JBoss 5.0 as a server in NetBeans 6.5
This issue is logged at NetBeans as issue number 154800 and is scheduled to be released into Patch 2 for NetBeans 6.5 to be issued towards the end of January.
JBoss old timer, Red Hatter, and successful open source entrepreneur. Co-wrote two books as well as a few other in print and online publications. Husband, father of two, and New England Patriots season ticket holder since 1993.
Runa WFE is an environment for JBoss jBPM workflow engine. It is a cross-platform end user solution for business process development and execution. Together Runa WFE and JBoss jBPM provide an easy to use business process management system.
Runa WFE is an open source project.
What is this project
Runa WFE provides:
* an end user GUI to define business processes without any coding: draw flowcharts, define roles and variables, lay out forms
* an end user GUI to load and execute processes
* an administrative interface to create and remove users/groups and grant rights
* a possibility of writing automatic "bots" that can participate in business processes
* a possibility to code new GUI elements, variable types, organizational structure functions etc. that extend existing Runa WFE components and will be available to end users through the GUI
Runa WFE makes it possible to integrate your diverse enterprise applications in a unified system, by using "bots" that run inside "bot stations".
Elastica is a highly efficient and extensible, rules-based load-balancer for JBoss that adds dynamic behavior to EJB load balancing. Rules can be defined to redirect EJB requests according to request data, server performance data, or even the time of day
Business process management (BPM) – while also its own independent practice / school of thought – is an application of technology that is served by many products, not the least of which is jBPM. The best definition of BPM that I've found is: "Business Process Management (BPM) is the concept of shepherding work items through a multi-step process. The items are identified and tracked as they move through each step, with either specified people or applications processing the information. The process flow is determined by process logic and the applications (or processes) play virtually no role in determining where the messages are sent.".
The Envers project aims to enable easy versioning of persistent JPA classes. All that you have to do is annotate your persistent class or some of its properties, that you want to version, with @Versioned. For each versioned entity, a table will be created, which will hold the history of changes made to the entity. You can then retrieve and query historical data without much effort.
Similarly to Subversion, the library has a concept of revisions. Basically, one transaction commit is one revision (unless the transaction didn't modify any versioned entities). As the revisions are global, having a revision number, you can query for various entities at that revision, retrieving a (partial) view of the database at that revision.
In spite of the example working, transaction management is not working appropriately when it comes to both Hibernate and JBossCache participating of the same transaction. The reason is because at the time of writing this wiki, Hibernate did not allow to inject a JTA Transaction Manager which is not bound to JNDI. In the example, Hibernate creates a JDBC transaction and JBossCache a JTA transaction which are not linked together. To be able to make a Hibernate and JBossCache participant of the same JTA transaction in a standalone environment, customer code needs to be added to Hibernate to get around the JNDI/JTA coupling.
In this blog entry I’ll look at Drools/JBoss Rules implementation of Alpha and Beta Nodes indexing. How such an index looks like. When it is created. What are the benefits. Some examples are also given.