Free jboss software for linux

Jconsole is a JMX console for JBoss that provides a pre-built Web client for the JBoss application server.
It deploys the JMX features of JBoss.
Enhancements:
- Bugfixes and codebase updates were done.

Sanos is a minimalistic 32-bit x86 OS kernel for Java based server appliances running on standard PC hardware.
This enables you to run java server applications without the need to install a traditional host operating system like Windows or Linux. Only a standard Java HotSpot VM and the sanos kernel are needed.
The kernel was developed as part of an experiment on investigating the feasibility of running java server applications without a traditional operating system only using a simple kernel.
The kernel implements basic operating system services like booting, memory management, thread scheduling, local and remote file systems, TCP/IP networking and DLL loading and linking.
A win32 layer allows the Windows version of the standard HotSpot JVM to run under sanos, essentially providing a JavaOS platform for server applications. This enables you to run java based server applications, like tomcat and jboss, under sanos.
Alternatively, you can use sanos as a small kernel for embedded server applications written in C. Sanos has a fairly standard POSIX based API and an ANSI Standard C library. In this case you dont need the JVM and the win32 wrappers.
Sanos is open source under a BSD style license. Please see the COPYING file for details.
Click on the topics below for further information, or send me an e-mail if you have any questions, comments or problems regarding sanos. Please include the word sanos in the mail to prevent it from being intercepted by my spam filter.
Sanos can be downloaded as either binary or source. All the files in the binary version can be built from the source version, so you do not need the binary version, if you are building sanos from source.
The binary version contains the compiled version of sanos, with files and utilities for making a boot disk.
The source version contains all the source code and build files for building sanos from source. You will need a Microsoft Visual C compiler to build sanos from source.
Enhancements:
- GetLogicalDrives() in kernel32 implemented.
- A bug in cmd_ipconfig() in sh.c prevented proper display of network configuration if no DNS servers was configured. This problem has been fixed. (FGA)
- New -a option added to mkdfs to support file lists with alternative files names. This simplifies configurations with both debug and release builds.
- The Visual Studio wizard can now generate a floppy disk boot image configured for the application.
- Shell prompt can be configured by setting the prompt property in the [shell] section of the os.ini file.
- If command line arguments are given to the shell it now executes the built-in command and exits the shell.
- The floppy motor timeout routine now acquires the floppy mutex before turning off the motor in order to prevent race conditions.
- Advanced Power Management (APM) support implemented. The computer can now be powered off after os shutdown. The mode parameter for exitos() can be used to specify the shutdown mode (halt, reboot, poweroff, debug). A shutdown command has been added to the shell. The power status can be retrieved using /proc/apm.
- Added /proc/cpu for CPU information.
- The raise() function now returns an error if the signal number is invalid.
- Breakpoint traps are now sent to the user mode signal handler. This allows breakpoints to be handled by user mode code.
- Signals now exits the currently executing job with the signal number as exit code. However, if the debug flag in the PEB is set the debugger is entered if an unhandled signal is encountered. The debug flag can be set using the debug command in the shell. The debug flag can be configured using the debug property in the [os] section of os.ini. The default value of the debug flag is 0, unless the system is build in debug configuration.
- readv() and writev() implemented in vfs.
- The kernel log is now implemented by the device driver /dev/klog. The kernel log now support ioctl for waiting for new log entries in the kernel log. The kprintf has been extended to support different log levels.
- The syslog interface has been redesigned in to comply with POSIX. The syslog now supports logging to a syslog server by setting the loghost property in the [os] section of os.ini.
- New klog daemon to read entries from the kernel log (/dev/klog) and add them to the system log.
- The sockaddr and sockaddr_in structures has been change to conform to winsock definitions.
- The sleep() function has been renamed to msleep(). A new POSIX conformant sleep function has been added to unistd.h.
- Added sys/time.h header file. Also added tzp parameter to gettimeofday() for POSIX compliance.
- New simple text editor utility (edit.exe) added.
- The syserror() function has been moved from libc.lib to the os.dll as an exported os api call.
- readline() now uses stdin and stdout for input and output.
- Bug in iomux fixed. Now a monitored event signals the iomux and not the associated object.
- Implemented popen() and pclose(). Also added a P_SUSPEND parameter to spawn() to allow new jobs to be started suspended.
- The kernel version information is now kept in a version resource in krnl.dll. The version information is retrieved using the new module version information functions in verinfo.c.
- The build type can now be controlled by compile time switches. The kernel version can be displayed in the Windows Explorer by viewing Properties for krnl.dll and selecting the Version tab.
- User management added to kernel. Each thread is now assigned to a user and a group. A thread has both a real and an effective user and group owner. The {get|set}[e]{uid|gid}() functions can be used to change the effective and real user and group for a thread. When a new thread is created the effective user and group are inherited from the creator thread.
- Added functions to query /etc/passwd and /etc/group files.
- New whoami, id, chmod, and chown commands added to shell. The format of the output from ls has been changed to display the file permission info.
- New file system version for DFS. The new version supports user and group owner for files and directories as well as permission bits. The new DFS version also supports files larger than 2GB. The fchown() and chown() functions has been added to vfs.
- DES-based crypt() implementation added.
- The spawn() function now computes the pgm parameter from the cmdline parameter if the pgm parameter is NULL. The initpgm and initargs properties in the [os] section of /etc/os.ini has been replaced with a single property named init. The default for init has been changed to /bin/sh.
- The behavour of the initial application has been changed. Previously the os shut down after the initial application exited. Now the initial application is executed again if it exits.
- Telnet daemon moved from the shell to separate server (telnetd.exe). The new telnet daemon has a more robust handling of the telnet protocol. The telnet daemon invokes the new login utlity in order to log on user.
- FTP daemon implemented.

POMStrap is a little opensource (BSD License) application bootstrap designed to avoid the Java library dependency/version headache. The more we use open-source Java components, the more we have to deal with the classical problem of dependency conflict.
Ive personally experienced this problem when using FOP and Batik simultaneously: FOP required a specific old version of Batik to work (and render vector images), and I needed to use the latest version of Batik for image rendering.
POMStrap allows you clean separation of concern within your application (for component oriented architecture), providing strict hierarchical classloader confinement.
POMStrap is able to load application dependency as they are declared in Maven 2 project file, and execute each dependency in its own classloader without inhering from its parent avoiding version conflict.
By using POMStrap you will be able to have an application dependency schema such as:
Application-1.0
+ DepA-1.0
+ DepB-1.0
+ DepA-2.0
And DepB-1.0 executing DepA-2.0 classes (and not DepA-1.0 as it would be without POMStrap).
POMStrap also work as an application bootstrap. POMStrap project just requires a pom file (Maven 2 project file) and a class/method to fetch all required dependencies and launch the application using a command line syntax such as:
java -jar pomstrap-1.0.jar groupId:artifact:version classname[:method] [method args]
for example:
java -jar pomstrap-1.0.jar pomstrap:testApp:1.0 com.prefetch.pomstrap.App:run
If no method is provided it will try to start the classical java static main method.
Be default POMStrap looks into you local repository (in you [home directory]/.m2/repository) but you can also specify another repository URL using system property:
"-Dmaven2.repository.url=[URL]"
You can use POMStrap via a Servlet with similar init-parameters configuration (see provided example sources).
A JBoss POMStrap Service is also available and allows you to lauch applications as JBoss Service (via .sar file deployed in a JBoss instance).
By the way, POMStrap can easily be embedded in your application with minimal impact (since it does not require any external library).
Enhancements:
- This release fixes a bug in the resource loader and remote repository definition.
- POMStrap has now been successfully used in a different production environment and this release can be considered as gold.

NVBase is a highly customizable open source enterprise search engine licensed under LGPL. The project comes with several search devices like RSS, HTML, Samba, NNTP, Database and local file systems, agents for passive searching and a seamless integration of popular authentication systems. It uses state of the art technologies like:
- JBoss
- EJB 3
- Lucene
- MyFaces
- Ajax
- Compass

SubEthaSMTP is an easy to understand Java library that provides a receptive SMTP server component.
By plugging this component into your Java application, you can easily receive SMTP mail using a simple abstract Java interface.
Also included is a small sub-project called Wiser, an easy to use incoming mail testing framework.
Main features:
- A mailing list manager (ie, SubEtha Mail)
- A mail server that delivers mail to user inboxes
- A mail archiver like Mail Archive
- An email test harness (Implemented in this project. Its called Wiser.)
SubEthaSMTP was split out of the SubEtha Mail mailing list manager because it is a useful standalone component. When we wrote SubEtha, the last thing we wanted to do was write our own SMTP server. In our search for a modular Java SMTP component, we examined:
Apache JAMES
JBoss Mail Server
Dumbster
Jsmtpd
JES
Java Mail Server
Since youre reading this page you probably already know what we found: Six different SMTP implementations without the slightest thought given to reusability. Even Jstmpd, which purports to be a "A Modular Java SMTP Daemon", isnt. Furthermore, even though JBoss Mail is in active development, the team was unintersted in componentization of the SMTP processing portion of their server.
During the development of SubEthas testing harness, we tried out the Dumbster software and found that not only was the API difficult to use, it did it not work properly, the developer has not done any development on it in about a year and it does not work reliably on Mac OS X. With two simple classes we re-implemented it as an included project called Wiser.
We hate reinventing wheels. This should be the LAST FREAKING JAVA SMTP IMPLEMENTATION.
Enhancements:
- This release fixes a couple of bugs with SMTP RFC handling.

saml-registry is a SAML 2.0 Metadata management tool that is useful for building shibboleth-based federations.

The saml-registry is a j2ee-application intended as a federation management tool, primarily (but not exclusively) for use with shibboleth. Future versions will support full delegation of rights through container-based role-management. The current version relies on container-based authentication.
For convenience the current version of the sql database schema and a jboss datasource descriptor sample can be found here on the right.

Installation instructions

Download the ear-file from the maven repository and drop it in the deploy-directory of your jboss application server. This build has been tested with jboss 4.0.2 but later versions should work.

You may need to disable certain features in a standard jboss, notably the jboss-ws4ee.sar (which conflicts with webservices provided by saml-registry) - just remove it from the deploy directory. Newer versions of jboss may ship with included versions of myfaces and jsf. These files must also be removed from your jboss before deploying saml-registry (or you must repackage the application excluding these libraries from the ear).

Next create a datasource-file for the mysql datastore. The < jndi-name/ > must be set to jdbc/saml-registry. Now create the database (update the datasource file with the server, username and password). Drop this file next to the ear in the deploy-directory. Use the sql schema to populate the database.

Finally configure authentication and authorization for saml-registry. This is done in the container by editing the login-config.xml (for jboss). Create a security domain called saml-registry in login-config.xml. The attached login-config.xml contains a sample entry which is based on property-files. The UsersRolesLoginModule is described on the jboss wiki.

The authorization for saml-registry is also managed by the security domain using standard j2ee role-based security. The roles govern access to individual use-cases (represented by menu entries in the user interface). Future versions will add per-organizational access control to this basic framework so that management of entities can be delegated.

The use-cases and roles is documented by this usecase diagram. Once your security-domain is configured to serve these roles (by editing property-files or whatever) you should be able to point your browser to https://your-box.example.com/saml-registry and get the main menu (or a login page depending on how your security domain was setup).

Building from source

In order to build saml-registry from source (which can be obtained from the subversion repository) you need maven2 and java5 to build the sources. The saml-registry is based on an MDA toolchain called andromda. Normally maven2 should download and install all dependencies, however the user interface needs the jsf2 cartridge from the andromda plugins project which may not be distributed from the andromda maven repository. If maven2 complains about unresolved dependencies for jsf2 then checkout the andromda plugins project and build it manually.

Spike Asset Manager (SAM) is an open-source cross-platform framework for probing a system for components and reporting them. It includes a driver file that probes for components commonly found in a LAMPJ stack (Apache, MySQL, PHP, Tomcat, etc).
SAM can find multiple versions that are installed, query the rpm database and indicate whether components are running. Driver files may be edited to search for different components.
SAM can be extended by writing extension plugins (shell, perl, python, java, etc). It can also be extended by changing the code and creating additional directives for the driver file.
The list of components that SAM currently looks for include:
- apache2
- axis
- commons-logging
- hibernate
- java
- jetspeed
- jboss
- log4j
- mysql
- openldap
- openssl
- perl
- php
- python
- spring
- struts
- tomcat
Enhancements:
- This development release adds a Web server.
- There is now an AJAX enabled Web client to perform what was previously done via command line.
- This allows a common interface (across operating systems) as well as local and remote administration. AJAX is made possible with integration through MochiKit and JSON.
- The Web site has also moved to the SpikeSource developer Web site.

EasyEclipse Server Java is for development of server-side Java applications, such as JavaServer Pages, EJBs and Web Services.
EasyEclipse Server Edition contains lots of plugins to manage different application servers (Tomcat, JBoss, WebLogic), develop on some server-side frameworks (Struts, Java Server Faces), and manipulate common file types on servers (HTML, XML, JSPs).
This distribution includes the following plugins:
Core components with a JDK:
- Eclipse Platform 3.2.1 - Shared platform services from Eclipse.
- Eclipse Tools 3.2.1 - Common libraries for various Eclipse projects.
- Java JDK for Windows 1.5.0.09 - Run Java application on Sun Java(tm) runtime, packaged for Eclipse use. (Windows only)
- Java JDK for Linux 1.5.0.09 - Run Java application on Sun Java(tm) runtime, packaged for Eclipse use. (Linux only)
Tools for general Java development:
- Eclipse Java Development Tools 3.2.1 - Edit, compile, run, debug, test, refactor, document and deploy Java applications.
Some essential utilities:
- AnyEdit Tools 1.5.6.2 - Useful right-click menus in editors: "Open file under cursor", "Open type under cursor", et cetera.
- Eclipse Utils Plugins 1.0.0.1 - Save the cursor position of editors when closing and re-opening a file. Access common team actions with explorer buttons.
- Color Editor 1.2.4 - Edit with syntax highlighting over 100+ file formats.
Tools for development of server-side applications in Java:
- Sysdeo Tomcat Launcher 3.2.0.beta - Start, stop, and manage Tomcat and WAR files without leaving Eclipse.
- JBoss IDE with AOP and EJB3 2.0.0.Beta2 - Develop, deploy, test and debug JBoss-based applications, with support of Enterprise Java Beans 3.0 and Aspect-Oriented Programming.
- Hibernate Tools 3.2.0.beta8 - Edit Hibernate mappings, execute HQL queries and develop applications with Hibernate, a Java persistence and object-relational mapping framework.
- Weblogic Server Plugin for Eclipse 2.0.0.RC3-1 - Start, stop and manage a WebLogic server. Run and debug applications on a Weblogic server.
- Spring IDE 1.3.6 - Develop, manage and deploy Spring Framework based applications.
- Eclipse J2EE tools 1.5.2 - Create and deploy J2EE based applications, including Servlets, JSP and EJB.
- Eclipse Database tools 1.5.2 - Access, manage and query SQL relational databases and servers.
- Amateras IDE 2.0.2 - Edit HTML, XML and JSP. Manage Struts and Java Server Faces configuration files visually.
Tools for web development:
- Eclipse Web tools editors 1.5.2 - Edit and validate XML, XSL, XML Schemas, DTD, HTML, JavaScript and CSS files. Test and validate web services.
- Eclipse HTML Tidy 1.2.2.patch-01-1 - Format and validate HTML, XHTML and XML documents within your favorite editor.
- Amateras HTML and XML editor 2.0.2 - Edit HTML, JSP, XML and CSS files.
Database management tool:
- QuantumDB 3.0.3 - Access, manage and query SQL relational database and servers access using standard JDBC drivers.
Version Control tools (note that CVS support is included in the Eclipse Platform):
- Subclipse 1.1.8 - Access and manage Subversion repositories within Eclipse.