Reviews run for a minimum of one week. The outcome of the review is decided on this date. This is the last day to make comments or ask questions about this review.
Cargo Tracker was officially part of the Java EE Blueprints project and focused on DDD. I would like to bring the project forward onto Jakarta EE.
Eclipse Cargo Tracker provides an example application that showcases core Jakarta EE technologies.
- Demonstrate well established architectural patterns/blueprints for enterprise development with Jakarta EE using pretty close to a real world application.
- Demonstrate a concrete implementation of DDD concepts.
- Showcase some core Jakarta EE technologies.
- Jakarta EE does not attempt to be a walled garden. Like all open standards, the goal of Jakarta EE is to provide a reliable core standard foundation that a vibrant ecosystem of plug-ins and extensions can be built around. In that spirit, we will incorporate a select set of representative tools that complement Jakarta EE well such as Maven, JUnit, Cargo, JMeter, soapUI, Arquillian, PrimeFaces and DeltaSpike.
- Comparison with other technologies such as Spring or .NET. We suggest you do your own research using the plethora of good information already available. This project is squarely about showing you how you could write good Jakarta EE applications and nothing else.
- Attempting to demonstrate the very wide gamut of Jakarta EE APIs and features. While we do incorporate a pretty representative set of Jakarta EE APIs and features, it is not our goal to serve as a kitchen sink of comprehensive Jakarta EE samples. The Jakarta EE Examples project serves that purpose far better than us.
- While it is certainly possible to learn certain aspects of Jakarta EE (primarily how to architect good Jakarta EE applications), this project is not intended to teach you the basics of Jakarta EE. The Jakarta EE Tutorial is intended as a basic learning tool for Jakarta EE.
This project demonstrates how you can develop applications with the Jakarta EE platform using widely adopted architectural best practices like Domain-Driven Design (DDD). The code is intended to mirror a non-trivial application that developers in the real work would work on. It attempts to demonstrate first-hand how you can use Jakarta EE to effectively meet practical enterprise concerns such as productivity, agility, testability, flexibility, maintainability, scalability and security.
Since Java EE is moving to Eclipse, Cargo Tracker should move here as well to maintain community cohesion. It is a valuable project in the overall Jakarta EE portfolio.
The original project was in MIT license at Oracle. That is what I prefer to retain.
The first build should be possible right after the transfer from Oracle. After that, I plan to merge my temporary updates in subsequent months, which will include adopting Jakata EE 8. The project is currently at Java EE 7.
Beyond that there is a roadmap that existed at Oracle: https://github.com/javaee/cargotracker/issues. I plan to keep working on it going forward.
I plan to keep working on the items here: https://github.com/javaee/cargotracker/issues. The biggest next bit of work is adopting Jakarta EE 8 and Java SE 8.
I plan to blog, tweet and speak about the project. Hopefully that will result in a few more contributors.