Your SlideShare is downloading. ×

JBoss @ CVUT FIT April 2013

313

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
313
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. 15th April 2013Red Hat & JBoss @ ČVUT FITJBoss Community x Enterprise Václav Tunka Software engineer JBoss Enterprise Platforms
  • 2. What is JBoss?
  • 3. What is JBoss Application Server?● Open Source Java EE server.● Found by Marc Fleury in 1999.● The name came from Enterprise Java Beans (EJB) -> EJBoss.
  • 4. Runtime for back-end applications.
  • 5. Programmers can concentrateon customer logic.
  • 6. Transactions
  • 7. Messaging
  • 8. Load balancing
  • 9. Persistence
  • 10. Clustering
  • 11. Caching
  • 12. Java EE standards – to sum up● Web Server (HTTP, HTTPS)● Web container (JSP, JSF, Servlets, ...)● Enterprise Java Beans (EJB)● Persistence API (JPA)● Transactions API (JTA)● Web Services (JAX-WS)● Messaging (JMS)● Management (JMX)● Security (JAAS)
  • 13. Lets talk about community projects first
  • 14. Packaging and component integration is the key
  • 15. What is productization?● Productization is a systematic effort to create a supported and tested product version out of JBoss and thirdparty opensource projects.● Cooperative effort with help of many other departments● Productization department is ultimately responsible for the products
  • 16. Why Productize?● Meet Software License Requirements● Provide Consistent Branding Message● Improve User Experience● Deliver Secure Applications● Enable Effective Product Support● Improve Product Packaging/Installation/Maintenance
  • 17. Productization: Fedora x JBoss.org projects
  • 18. Fedora is productized already1) Legal2) Branding3) Usability4) Security5) Support6) Packaging
  • 19. The JBoss Community is not productized● Focused on R&D● Legal requirements are not always checked● Over 70 JBoss.org projects ● Different brands ● Many different communities
  • 20. JBoss Community Builds● Different Project Sites (JBoss.org, github, etc)● Different SCMs (svn, git, etc)● Different Build Tools (Ant, Maven, Gradle)● Thirdparty Projects (Apache, Codehaus, Sun/Oracle)
  • 21. Fedora vs. JBoss Community● Fedora takes community projects and packages them into a coherent system● The JBoss Community focuses on delivering a variety of (very) loosely related projects
  • 22. Productizing JBoss EAP
  • 23. JBoss EAP Productization1) Legal2) Branding3) Usability4) Security5) Support6) Packaging
  • 24. Challenges● Java/Maven vs. RPM● Rebuilding Takes Time ● Locate the source ● Understand the build ● Find the dependencies ● Build ● Add Bugs! :)● Delay between upstream changes and product release
  • 25. Lots of Dependencies● JBoss AS has ~200 direct dependencies● All build and test dependencies for all components? ● Greater than 1000
  • 26. Quick summary Community projects vs. Enterprise products What is productization? Why is it important?
  • 27. References● Dimitris Andreadis – JBoss.org x Jboss.com http://www.slideshare.net/dandreadis/jbossorgjbossco m● Backbone image CC● Craftman image CC● ATM image CC● Message image CC● Dogs images CC● Clock image CC● Grapes image CC
  • 28. Additional Creative Commons images● Geocaching CC image● JBoss.org design & slide decks
  • 29. TITLE SLIDE: HEADLINEPresentername Thanks for listening!Title, Red HatDate
  • 30. Come work for us!● The job is a combination of developement, packaging and release engineering● You should have overview of Java ecosystem● You should know maven and ant● Experience with releases and packaging is welcome
  • 31. What is productization?● We take jboss.org community projects and other opensource libraries and package them together● We also provide fixes for the product branch and keep it in sync with upstream● If the upstream community is inactive, we take charge● We build every 3rd party dependency from sources

×