Java Application Server Packaging
Ubuntu currently supports a lightweight container approach through tomcat6 to deploying Java based web applications. This is sufficient for use-cases with no dependence on a full JEE feature set and where popular tool-sets such as Spring are being used to assemble and integrate applications.
However, Ubuntu does not current package a full, modular JEE stack which has more widespread adoption in larger enterprises.
Consideration needs to be given as to whether the effort of packaging a full JEE stack will bring the required level of value to Ubuntu or whether the lightweight application server (through tomcat) is the correct approach for Ubuntu.
Blueprint information
- Status:
- Complete
- Approver:
- Robbie Williamson
- Priority:
- Medium
- Drafter:
- James Page
- Direction:
- Approved
- Assignee:
- James Page
- Definition:
- Approved
- Series goal:
- Accepted for natty
- Implementation:
- Implemented
- Milestone target:
- ubuntu-11.04
- Started by
- Robbie Williamson
- Completed by
- Robbie Williamson
Whiteboard
Current Update:
So some complication around certification of the binary packaging; JOnAS 5.1 series is normally certified on JDK5 (which we don't have other that gcj which does not work). It certifies OK against Sun JDK 6 but not OpenJDK 6. As a result I've also packaged 5.2.0 M4 (development series) which should be OK with OpenJDK 6. Florent Benoit is testing this week.
Previous Update:
Tomcat 7.0 has only just moved out of beta; in addition I've not had much time to work on this packaging. I may have time later in the cycle to start work on this but at this point in time packaging Hudson is taking up all of my time.
A basic JOnAS package can be found here : http://
Florent Benoit of ow2.org is current testing this package. If it is successfully certified, james-page will publish out a stable release into a separate PPA.
UDS Notes:
* Is a full JEE stack where we should be going (see SpringSource for an alternative approach)?
* Is JEE webscale? General consensus is yes.
* Both approaches are used and valid so Ubuntu should try to support both.
* Complexity of build from source/packaging vs value of bring JEE stack to the platform i.e. is anyone going to use it?
* Build from Source
* Supporting multiple versions of dependencies to resolve conflicts?
* Binary Packaging
* Channel through PPA or Multiverse
* JEE compatilbity against binary artifact not source artifact
* JONAS (OW2) could be a potential contender - general agreement that this would be the best upstream option
* Patent Encumbered; needs to be considered.
* Potentially start small by removing backend options
* When to target Tomcat 7 -> Ubuntu?
* Relatively low cost so should be considered to support latest Servlet/JSP API's
* Current Tomcat is 7.0.4 (released 2010.10.21)
* with support for Servlet 3.0, JSP 2.2 and EL 2.2
* Maven -> debian automation.
* Required to support scalability if we choose to support a large numbers of java libraries.
Work items natty-alpha-3:
[james-page] to package Tomcat 7: POSTPONED
[james-page] to make a jonas package from binaries: DONE
[james-page] to try packaging jonas from source, see if it works / how hard it is: POSTPONED
[nijaba] to introduce james-page to ow2: DONE
[clint-fewbar] to create an automatically populated PPA with the content from the maven archive: POSTPONED
[james-page] Updated PPA packages to 5.1.6: DONE
[james-page] Package JOnAS 5.2.0 M4 (binary) and upload to PPA: DONE
Work items:
[james-page] work with JOnAS upstream to ensure JEE certification on Ubuntu: INPROGRESS