A point of pride for the TomEE community is a large library of examples contained in the TomEE GitHub project. Whenever you clone or otherwise download the TomEE GitHub project you get nearly fourteen dozen examples you can review and run to learn more, not just about TomEE, but Java EE in general. The examples are like a free, code-centric cookbook that covers everything from programming a simple Java web application to CDI interceptors, to WebSockets with TLS Security. With 166 coded examples to choose from it seems there is something for everyone. Getting started with TomEE and running its…
Read More
Tomitribe supports a lot of clients that use ActiveMQ and JMS in production. If you need expert support to optimize and maintain your ActiveMQ setup, contact Tomitribe today for professional assistance. This post introduces you to both ActiveMQ and JMS. If you already understand the fundamental concepts behind JMS messaging, skip ahead to “A Short ActiveMQ and JMS Tutorial”.. It should take five minutes or less. If you are new to JMS then keep reading! JMS Concepts A messaging system is composed of a JMS Broker (middleware), Queues and Topics, and Producers and Consumers. The JMS Broker There is a…
Read More
If you think your company is immune to cyber attacks, think again. By some estimates, nearly half of all websites have, at this very moment, a critical security vulnerability and nine out of ten have at least a moderate security vulnerability.1 No One Is Safe Even the largest and most sophisticated sites are not fully secure. It’s estimated that of the 500 busiest websites one third are not secure including sites like ESPN.com, BBC.com, Wikia.com, MyShopify.com, Chegg.com, and NBA.com1. Within the last year, some of the largest companies in the world have experienced breaches exposing sensitive data and affecting millions…
Read More
This is the second installment in a two-part article covering the Process Task portion of the Contribution Workflow. The Contribution Workflow is covered in detail in the first part within “Section 1: The Contribution Workflow Overview.” The Process Task portion of the Contribution Workflow is where you do the work on an issue (bug fixes, enhancements, tests, documentation) after getting assigned a JIRA ticket. This is where the rubber meets the road; where the actual work of writing or coding a solution takes place. The following diagram shows how the Process Task portion of the Contribution Workflow fits into the…
Read More
In the last installment, “It’s Easy! Your First TomEE Pull-Request: Using JIRA”, we showed you how to discover and get assigned a task in the TomEE open source project. This article, broken up into two parts, shows you how to get set up so you can start contributing and how to use Git to preserve your changes and save them up to your GitHub account. Section 1: The Contribution Workflow Overview 1.1 JIRA Ticket 1.2 Process Task 1.3 Submit Changes 1.4 Merge Changes 1.5 Clean Up Section 2: Process Task 2.1 Fork, Clone, Branch TomEE 2.1.1 Fork 2.1.2 Clone 2.1.3…
Read More
While all open source tools (i.e. GitHub, Maven, Mailing lists, Java IDEs) used by the TomEE open source community are important, the process of identifying and managing the work done on the project is critical to our success. The tool we use for managing work is the TomEE JIRA issue tracking system. Note: If you are not already familiar with JIRA tickets or find them confusing, you should read “It’s Easy! The Anatomy of a JIRA Issue” after reading this article. It will help clarify all the information a typical JIRA Issue addresses. Becoming a part of the TomEE community…
Read More
The “TomEE for the Holidays” campaign ended on January 16th of this year. It was great to see so many new Contributors (close to 50) join the TomEE project. In addition, participation from veteran contributors skyrocketed resulting in a level of communication and collaboration that would make any open source community proud. With the success of the “TomEE for the Holidays” initiative, the question became obvious: “How can we (Tomitribe) maintain a high level of participation and comradery in the project?” There were many things that made “TomEE for the Holidays” a success. Encouraging people new to open source to…
Read More
One of things that I had to learn about when joining the TomEE open source project was JIRA. JIRA is an issue tracking system with some light project management. It’s a great tool for keeping track of who is working on what and what bugs or issues need to be addressed. Note: JIRA isn’t an acronym it’s a truncation of the word, Gojira which is the real Japanese name for Godzilla. The folks that created JIRA chose the name as a tongue-in-cheek jab at their biggest rival at the time, Bugzilla. When you join the TomEE community you will end…
Read More
One of the greatest joys of my life has been working in Open Source. Why? First, I get to work on exactly what I want when I want. Software development is a creative process and working for someone else doesn’t always let me express myself. I need that. If my contributions are helpful, in line with the project’s goals, and are approved by my peers I can make a difference. That brings me to the second thing I love about open source: The people. Every project is different but in the TomEE project, everyone is volunteering their efforts and time…
Read More
In our last post we provided a step-by-step tutorial that explained how to debug Enterprise Java applications on TomEE from the Eclipse IDE. This time we'll do the same thing but with IntelliJ! I've always found debugging Enterprise Java applications to be a challenge, but modern features of the Java Virtual Machine and tools like IntelliJ make it easy. If you are already familiar with IntelliJ but have not debugged a TomEE application, then this will be a quick but useful tutorial. If you are new to IntelliJ or TomEE you'll find the steps outlined here very easy to follow.…
Read More
