- 3+ year marathon of redesigning the application server over
- The JBoss AS 5 is from the Java EE™ 5 codebase that fully complies with the Java EE 5
conformance testing certification requirements
- A completely new kernel architecture (JBoss Microcontainer)
- The most important by this release is that, JBoss 5 AS is now build on top of the new JBoss Microcontainer and that replaces the famous JBoss JMX Microkernel of the 3.x and 4.x series
What is JBoss Microcontainer?
MC is a lightweight container and is responsible for the management for POJOs, their deployment, configuration and lifecycle.
What with the integration with others JBoss Frameworks?
JBoss AOP?
The MC integrates nicely with JBoss AOP.
JBoss JMX?
JBoss 5 AS still supports JMX all MBean services written against the old Microkernel are expected to work fine.
JBoss VDF?
More important framework in the JBoss 5 AS is the Virtual Deployment Framework (VDF) . This framework takes aspectized deployers to 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.
JBoss 5 AS is also integrated with other standalone JBoss projects like:
- JBoss EJB3: simplifying the component programming
- JBoss Messaging new implementation of the JBossMQ
- with the latest JBossCache (PojoCache, inMemory, transactional, ...)
- JBossWS Java EE compatible
- JBoss Transaction : 18 year history as a leader in distributed transactions
- Web container based on Apache Tomcat that includes the Apache Portable Runtime (APR) and Tomcat native technologies.
About more new features will take place in a next post and for more information about this new release, takes a look at this http://www.jboss.org/
]]>
\ --> ctrl+alt+?
{ --> ctrl+alt+7
} --> ctrl+alt+0
[ --> ctrl+alt+8
] --> ctrl+alt+9
@ --> ctrl+alt+q
~ --> ctrl+alt+*
| --> ctrl+alt+>
( --> shift+8
) --> shift+9
“The new planned JBoss Application Server 5 will support the entire Java EE 5 specification.”
JBoss 4.2.X implemented EJB 3.0 functionality by the way of EJB MBean Container. That means it runs as plugim in the APPServer. As a consequence of the EJB 3.0 plugin integration, JBoss 4.2.X supports injection of @EJB references and EntityManager between different EJB components and this support is limited only to the EJB 3.0 MBeam and the JAR files.
Any reference of @EJB into a WAR (with servlets and JSF) can’t be released in JBoss 4.2.X AS.
I hope the information was helpful.
JAVA_OPTS="$JAVA_OPTS -Xms128m -Xmx512m -XX:CMSPermGenSweep:ngEnabled
-XX:MaxPermSize=128m -Dsun.rmi.dgc.client.gcInterval=3600000
-Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true"
The PermGenSpace of a JBoss AS instance has a standard value of 64m, therefore breaks down often the server instance.
]]>TopLink Essentials are the reference implementation (RI) of JPA, is an open source effort that is licensed under the Common Development and Distribution License (CDDL) v1.0. It can be freely downloaded and used under the terms of this license agreement. This means, you can only use it for the management of persistence and orm with Java EE and Java SE. The binary distribution of TopLink consist of 2 jars:
In addition to TopLink Essentials that makes the JPA implementation alive, Oracle offers its Oracle TopLink product (10.1.3) that contains an earlier preview binary of JPA and also offers developers additional object-relational capabilities, object-XML mapping (JAXB), non-relational mapping using Java 2.0 Connector Architecture (JCA).
]]>