The title of this post may be a bit misleading. This article is not about how people find open source software (OSS) to use, it’s about how people go about finding OSS used in the applications they develop.
In this exercise, I will demonstrate an approach to converting an Axis2-based web service contained within a web application running on JBoss 7, to a JAX-WS-compliant web service running on the JBossWS framework. For JBoss developers, JBossWS is a great choice for a web services runtime as it is based on the popular, and mature, Apache CXF framework. The Eclipse (Juno) IDE configured with the JBoss Tools 4.0 plugin will be the primary tools used in this effort.
Red Hat and the CentOS community recently announced that the CentOS community has joined with Red Hat to collaborate on future versions of CentOS. Red Hat has hired several members of the CentOS community, as well as added a few new members to the CentOS Governing Board.
In the world of large enterprise, technology infrastructure “procurement” usually includes a lengthy process of evaluating and selecting new goods or services, funding approvals, contract negotiation, and finally purchasing something. Three of these four procurement processes should not relate to enterprises using free and open source software (OSS), correct? So why even consider creating a strategy for procuring open source?
During the interview process at OpenLogic, one question all prospects are asked is “Did you use open source software (OSS) at your previous job?” If yes, “How did you comply with the licenses?” Answers range all across the board, but the most common response is “I assumed it was just free to use.” Individuals in charge of managing open source in their company should ask current and prospective employees the same question. More often than not, the answer will be the same: “I assumed it was just free to use."
As the cloud grows, so does the use of open source software.
Using open source is a growing trend in technology that may be tough to implement at first because it requires a shift in philosophy from holding information tightly, to sharing and collaborating across platforms and continents. The challenge is well worth it because open source allows programmers to create user-friendly, uniform applications easily while saving money and creating community and collaboration. Here are a few reasons why it is a solution worth investigating.
The goal of this post is to provide a high-level discussion of JBoss OSGi and to increase awareness of its potential benefits and drawbacks to a Java enterprise architect/developer.
One of the benefits of using open source software is the access to cutting edge technology. Assuming that the community of developers is a mature one, the newest release of a project will have gone through a beta release to have users help test and fix the majority of the bugs, and then a GA (general available) release will become available. An enterprise using these kinds of projects can begin implementation of the new version the exact same day it is released as a beta (still in a “quality assurance” stage of development), or an enterprise can wait for the more stable GA release.
OpenLogic has released pre-built AMIs of your favorite open source stacks on the Amazon AWS Marketplace.
If you read a post on The Enterprise OSS Blog, please leave a comment. Let us know what you think, even if it's just a few words. Comments do not require approval, but they are moderated.OpenLogic reserves the right to remove any comments it deems inappropriate.