Rustan Leino and Mike Barnett on Spec#
Rustan Leino and Mike Barnett of Microsoft Research discuss the technology in Spec# and its futures.
- .NET,
Tracking change and innovation in the enterprise software development community
Posted by Ryan Slobojan on Sep 17, 2007 08:00 AM
JBoss, a division of RedHat, recently announced the first release of their Enterprise Application Platform (EAP), which is based off of JBoss Application Server 4.2. InfoQ took the opportunity to learn more about this release and the potential changes it brings.
The first release of EAP is version 4.2, which corresponds with the version of JBoss Application Server that it is based on - it also bundles in JBoss Clustering, JBoss Cache, JBoss Messaging, Hibernate, JBoss Seam and JBoss Transactions. EAP fully implements the J2EE 1.4 specification, and also provides several features of the Java EE 5.0 specification including EJB 3.0, JSP 2.1, Servlets 2.5, JSTL 1.2 and JSF 1.2 as well as a few other smaller components.
The release of EAP also marks one of the first releases in the new JBoss development and support model - from now on, support can only be purchased from JBoss for EAP, not for the standalone JBoss application server. EAP support is sold on a subscription model which is very similar to RedHat's Enterprise Linux subscription model, with customers paying an annual subscription fee and receiving free upgrades and support during the subscription period. JBoss also supports each release of EAP for 5 years, with 3 years of that being full support and the following 2 years being maintenance support. In addition to technical benefits, the subscription also provides indemnification from lawsuits like those filed by the now-bankrupt SCO against Linux vendors and users.
WebSphere Virtual Enterprise 3 minute demo
The Agile Business Analyst: Skills and Techniques needed for Agile
Spring App Platform, Java Concurrency/Multicore, Eclipse Mylyn and more @ QCon SF Nov 19-21
Rustan Leino and Mike Barnett of Microsoft Research discuss the technology in Spec# and its futures.
Henrik Kniberg talks about 10 possible reasons to fail while doing Scrum and XP. Maybe the team does not have a definition of what Done means to them, or they don't know what their velocity is.
This article outlines 9 principles Marc Lammers discovered while building the world’s best field hockey team, mapping them to software development practices.
Michael Poulin explains the necessity for SOA governance to ensure an Enterprise SOA's success, relying on concepts from the OASIS SOA Reference Model and Reference Architecture.
This article covers setting up a RichFaces portlet using JBoss Portlet Container and JBoss Portlet Bridge, deploying a RichFaces portlet, and RichFaces capabilities.
This article discusses scalability worst pratices including The Golden Hammer, Resource Abuse, Big Ball of Mud, Dependency Management, Timeouts, Hero Pattern, Not Automating, and Monitoring.
Obie Fernandez shares his experience selling consulting services for both Thoughtworks and Hashrocket and give tips how Ruby developers can work with clients.
Jeffries and Hendrickson derive Agile practices from the natural laws of software development. They don't just say "Be Agile!", but they explain why Agile practices make perfect sense.
1 comment
Reply