Jetty Hightide Download
An in depth overview of the Jetty Application Server, and how it stacks up among other Application Servers. Download the full PDF report from RebelLabs. For the more hardcore app developers there is a project called Jetty Hightide that provides additional features such as JNDI, XA transactions, JMS. A quick note about Jetty Hightide. Previous releases of Jetty (6, 7 and 8) each released an additional distribution that contained some 3rd party integrations to give a more JEE experience however with Jetty 9 we have stopped providing this integration. Hightide is an open source, versioned and optimized distribution of Jetty providing a comprehensive toolset for the development of scalable, state-of-the-art web 2.0 applications.
Since the very beginning, has been IOC friendly and thus has been able to be. But the injecting and assembling the jetty container is not the only need that Jetty has for configuration and there are several other configuration files (eg contexts/yourapp.xml, jetty-web.xml, jetty-env.xml) that have needed to be in the format. With the release of Jetty-7.4, the jetty-spring module has been enhanced with and XmlConfiguration Provider, so now anywhere there is a jetty xml file can be replaced with a spring XML file, so that an all spring configuration is now possible. But note that there is no plan to use spring as the default configuration mechanism. For one, the 2.9MB size of the spring jar is too large for Jetty’s foot print aspirations (currently only 1.5MB for everything).
Starting with spring Jetty First you will need a download of jetty-hightide, that includes the spring module.
This equates to the Configure element of the Jetty XML format. Note also that both the Server and Contexts ids are used by subsequent config files (eg etc/jetty-deploy) to reference the beans created here and that the ID space is shared between the configuration formats. Thus you can mix and match configuration formats. Example Context XML As another example, you can replace the contexts/test.xml file with a spring version as follows.
Of course, with spring, you can also start jetty by running spring directly and using a more spring-like mechanism for aggregating multiple configuration files. Conclusion While spring and jetty XML are roughly equivalent, they each have their idiosyncrasies. The Jetty API has been developed with the jetty XML format in mind, so if you examine the full suite of Jetty XML files, you will see Getters and methods calls used to configure the server. These can be done in spring (AFAIN using helper classes), but it is a little more clunky than jetty XML.
This can be improved over time by a) having spring config files written by somebody more spring literate than me; b) improving the API to be more spring friendly; c) adapting the style of configuration aggregation to be more spring-like. I’m receptive to all three and would welcome spring users to collaborate with to improve the all spring configuration of jetty.
Jetty Hightide Download
Then in 2009 or so we decided to move the project to The Eclipse Foundation and were suddenly having to sort out how to distribute a split project as not everything was able to come to eclipse because of IP reasons (they are very strict about what can and can't be downloaded from eclipse) and we had to work for years with a org.eclipse.jetty:jetty-distribution and then something that contained some of the stuff that was left at The Codehaus. That extra distribution took on the monikor of hightide and over time things started getting removed from it that made it different from the normal jetty-distribution.
Ultimately it because nothing more then a thin skin over the jetty-distribution so we have decided to let it fade away as something unique. Simcity 5 key generator. Then in 2009 or so we decided to move the project to The Eclipse Foundation and were suddenly having to sort out how to distribute a split project as not everything was able to come to eclipse because of IP reasons (they are very strict about what can and can't be downloaded from eclipse) and we had to work for years with a org.eclipse.jetty:jetty-distribution and then something that contained some of the stuff that was left at The Codehaus. That extra distribution took on the monikor of hightide and over time things started getting removed from it that made it different from the normal jetty-distribution.
Ultimately it because nothing more then a thin skin over the jetty-distribution so we have decided to let it fade away as something unique.