JBoss Application Server

JBoss Application Server is the number one most widely used Java application server on the market.
Download

JBoss Application Server Ranking & Summary

Advertisement

  • Rating:
  • License:
  • LGPL
  • Price:
  • FREE
  • Publisher Name:
  • Red Hat, Inc.
  • Publisher web site:
  • http://www.redhat.com

JBoss Application Server Tags


JBoss Application Server Description

JBoss Application Server is the number one most widely used Java application server on the market. JBoss Application Server is the number one most widely used Java application server on the market. Hundreds of professional open source developers have contributed to the JBoss Application Server over the years and community contributors are not only welcome but encouraged. In fact all JBoss employed contributors to the JBoss Application Server were hired from the community and each of them contributed to an open source project in one way or another.A J2EE certified platform for developing and deploying enterprise Java applications, Web applications, and Portals, JBoss Application Server provides the full range of J2EE 1.4 features as well as extended enterprise services including clustering, caching, and persistence. We need the community to drive new features in each of these features. You are a powerful force in professional open source, and your contribution is essential to keeping JBoss AS the most used Java application server on the planet.JBoss Application Server includes support for Enterprise Java Beans (EJB) 3.0 which is designed to dramatically simplify the enterprise Java programming model.JBoss 5 is the next generation of the JBoss Application Server build on top of the new JBoss Microcontainer. The JBoss Microcontainer is a lightweight container for managing POJOs, their deployment, configuration and lifecycle. It is a standalone project that replaces the famous JBoss JMX Microkernel of the 3.x and 4.x JBoss series. The Microcontainer integrates nicely with the JBoss framework for Aspect Oriented Programming, JBoss AOP. Support for JMX in JBoss 5 remains strong and MBean services written against the old Microkernel are expected to work.JBoss5 is designed around the advanced concept of a Virtual Deployment Framework (VDF), that takes the aspect oriented design of many of the earlier JBoss containers and applies it to the deployment layer. Aspectized Deployers operate in a chain over a Virtual File System (VFS), analyze deployments and produce metadata to be used by the JBoss Microcontainer, which in turn instantiates and wires together the various pieces of a deployment, controlling their lifecycle and dependencies.Here are some key features of "JBoss Application Server":· Boss EJB3 included with JBoss 5 provides the implementation of the latest revision of the Enterprise Java Beans (EJB) specification. EJB 3.0 is a deep overhaul and simplification of the EJB specification. EJB 3.0's goals are to simplify development, facilitate a test driven approach, and focus more on writing plain old java objects (POJOs) rather than coding against complex EJB APIs.· JBoss Messaging is a high performance JMS provider in the JBoss Enterprise Middleware Stack (JEMS), included with JBoss 5 as the default messaging provider. It is also the backbone of the JBoss ESB infrastructure. JBoss Messaging is a complete rewrite of JBossMQ, which is the default JMS provider for the JBoss AS 4.x series.· JBossCache 2.0 that comes in two flavors. A traditional tree-structured node-based cache and a PojoCache, an in-memory, transactional, and replicated cache system that allows users to operate on simple POJOs transparently without active user management of either replication or persistency aspects.· JBossWS 2 is the web services stack for JBoss 5 providing Java EE compatible web services, JAXWS-2.0.· JBoss Transactions is the default transaction manager for JBoss 5. JBoss Transactions is founded on industry proven technology and 18 year history as a leader in distributed transactions, and is one of the most interoperable implementations available.· JBoss Web is the Web container in JBoss 5, an implementation based on Apache Tomcat that includes the Apache Portable Runtime (APR) and Tomcat native technologies to achieve scalability and performance characteristics that match and exceed the Apache Http server.Requirements:· JavaWhat's New in This Release:· Need additional trace level logging about security domain cache validation· Custom header based authentication· Add configurable policy for determining master node for HASingleton· Upgrade JBossSerialization to 1.0.0.CR4· Role Mapping Login Module that maps application role to declarative role· HAPartition should use its Marshaller for marshalling RPC responses· Add a system property to configure TCPPING.initial_hosts· Add system property to configure multiplexer stack· Deployment Level Principal-Role Mapping passed to authorization layer· Slow DataSource Failover - JCA Stale Connection Detection· Clone the JBossMX javax.management.timer.Timer implementation, to a jboss package· LoadBalancePolicy that tries to pin all requests associated with a tx to one server· Logging of cluster rpc method exceptions at warn level is incorrect· two timers executing at the same time in some conditions· "jboss:service=invoker,type=http,target=HAJNDI" misconfigured in file httpha-invoker.sar/META-INF/jboss-service.xml· JBossCacheManager session expiration algorithm ignores replication events· Lock Contention on org.jboss.ejb.BeanLockManager· Clustered SSO improperly invalidated upon web application shutdown· hashCode() of org.jboss.util.id.GUID and UID appears to return the same value for all GUIDs created· Lock contention on BasicMBeanRegistry::get· Synchronization into org.jboss.ejb.EnterpriseContext$EJBContextImpl· Problems with separated ClassLoaders for EARs and pooled invoker (PooledInvokerHA).· Authenticated user can bypass declarative role checks for servlets· LdapExtLoginModule does not handle roles containing '/' correctly· Remove all calls to InetAddress.getHostName() (causes reverse DNS lookup)· JBoss ignores "Class-Path" attribute in WAR's MANIFEST.MF· Legacy MainDeployer.deploy use of checkIncomplete causes leaks/test failures· Cluster loses his master


JBoss Application Server Related Software