What exactly is the difference? I've been using Jetty 8.0.0 lately and when I try the distribution download I cannot get neither WebSockets nor Servlet 3.0 #WebServlet annotation to work. If I use hightide, it just works.
What is the point of the distribution?
I'm interested in the difference too, and what's online is confusing. Here's Jesse McConnell's ( https://stackoverflow.com/users/1185262/jesse-mcconnell ) answer to my just-posted question on the [jetty-users] mailing list ( http://jetty.4.n6.nabble.com/jetty-users-jetty-versions-tt3675449.html ):
yes, hightide is just the jetty-distribution with some additions that we can not distribute from eclipse do to their IP restrictions.
I did a lot of digging around before I got that answer, so I'll include the results below for reference. I hope this helps.
Description from eclipse.org: The Jetty Hightide application server is a distribution of the jetty Web Server assembled at codehaus with additional services like JNDI, XA & JDBC preconfigured. For jetty-hightide-6 this is an optimized, patched rebuild of jetty-6, while for jetty-hightide-7 it is distribution based on the standard jetty-7 artifacts combined with other third party integrations. -- http://www.eclipse.org/jetty/about.php
Description from docs.codehaus.org: Hightide is an optimized, versioned distribution of the Jetty open source web container. It comes pre-integrated with a number of services usually only found in J2EE application servers, or which you would otherwise have to craft together yourself: JNDI, an XA transaction service, a JMS message fabric, and a JDBC accessible database. Thanks to Jetty's light weight, pluggable architecture, Hightide allows you to easily choose which of these services you want to use, or even replace them with others. -- http://docs.codehaus.org/display/JETTY/Hightide+Documentation
FAQ: "What's the difference between Jetty from Mort Bay, Codehaus and/or Eclipse?" at wiki.eclipse.org: The latest releases of core jetty-7 and later are available from Eclipse, which use the org.eclipse.jetty packaging. For versions 6 of Jetty, plus some jetty-7 components such as RPMs, Debs, Hightide, use codehaus, which uses the org.mortbay packaging. -- http://wiki.eclipse.org/Jetty/FAQ
However, the contents of the two distributions (see 'Downloads' below) both use the o.e.j packaging, so I don't think the answer is entirely correct.
Mentions of features at http://wiki.eclipse.org/Jetty:
The Hightide distribution of jetty contains an example webapp that uses JAAS. -- http://wiki.eclipse.org/Jetty/Feature/JAAS
Jetty supports java:comp/env lookups in web apps. This is an optional feature and you need to do some setup. However, if you are using the Hightide distribution of Jetty, this feature is already fully enabled, so you can skip any setup steps, and just read the sections on how to put objects into Jetty's JNDI so that you can retrieve them at runtime. -- http://wiki.eclipse.org/Jetty/Feature/JNDI
Annotation processing is not enabled by default by the standard jetty distribution, only by the Hightide distribution. -- http://wiki.eclipse.org/Jetty/Feature/Annotations
Downloads: Version numbers seem in-sync:
http://download.eclipse.org/jetty/8.1.4.v20120524/dist/
http://dist.codehaus.org/jetty/jetty-hightide-8.1.4/
After a cursory look, the contents look extremely similar.
Related
Is there any way to host windows update server for software updates? I am aware of WSUS, but it seems that not used for public purpose.
There is SCCM which is distributed by Microsoft itself.
InTune (again offered by MS) is a cloud based solution and could
also be useful, depending on your specific requirements.
Maybe Opsi is worth a look, too. It uses Linux servers to manage
Windows clients. Some parts of it (the ones you seem to be interested
in) are free to use and open source.
Since version 9.x Jetty seems not to have an aggregate artifact that provides the Jetty server within OSGi environments. It would be very helpful if the project could provide an OSGi compliant aggregate artifact for 9.x and further. In 8.x we had the org.eclipse.jetty.aggregate:jetty-all-server artifact. Why does it not exist for 9.x?
Can anybody help me or has some explanations?
The aggregates that exist for Jetty are not meant to be used by projects directly. They were created specifically for the documentation, and specifically for command line use to demonstrate some of the features of Embedded Jetty use.
It is not recommended to use aggregates for your project.
In fact, jetty-all (a name kept for historical reasons), isn't even "all of jetty" anymore. This concept isn't even possible anymore, as there are many component options for Jetty that cannot exist in the same jar at the same time.
Would highly recommend using the individual artifacts properly, and with a build tool that supports the global central repository, such as maven, ant+ivy, buildr, groovy grape, gradle+grails, scala sbt, or even leiningen.
Once you have a good build setup, you can then pick and choose and setup your own uber jars for jetty that fit your specific needs. Keep in mind that for OSGi, this would mean having to rewrite the manifest for this uberjar to include all of the OSGi references properly. Also note, that if you do this, you will likely not play well in the rest of OSGi world that is using Jetty properly. That is a decision you should make. Do I play in my own world of OSGi and never use OSGi bundles from other open source projects, or do I want to use other popular OSGi bundles in the future.
Currently My web Application is running on jboss 5.1 and we need to migrate it to jetty server..i am looking for a complete detail and steps to do the process...Thanks in advance
I don't think there exists a step by step document along the lines you are looking for. It largely depends on your web application how simple or hard the migration would be. If you are using EJB's for instance then you would have to also factor in the openejb integration we have some support for, if it is a straight war file then it is likely much easier. There are professional services from the jetty developers available to help if you like, you can google Webtide for that. I would recommend going straight to Jetty 9.1 though, the new distribution layout makes things a fair amount easier to separate things out.
Current documentation is here though: http://www.eclipse.org/jetty/documentation/current/
I'm interested in using libdrizzle as a generic asynchronous-capable connector for mysql db for a c++ application (actually as a backend for hiberlite). Since early this year libdrizzle is no longer a separate project and its merged in the same drizzle project, so installing as a separate dependency (unrelated to the rest of drizzle) might have become slightly more complex.
I'm wondering if people has used this library for interfacing to MySql or MariaDB, probably make some mickey mouse benchmarks to have a rough idea how it stands relative to the synchronous default driver.
Also, comments on difficulties to install, setup, pitfalls (the documentation is essentially nonexistent) would be greatly appreciated.
You might want to take a look at ngx_drizzle (drizzle-nginx-module) at github.
From module description:
This is an nginx upstream module integrating libdrizzle into Nginx in a non-blocking and streamming way.
Essentially it provides a very efficient and flexible way for nginx internals to access MySQL, Drizzle, as well as other RDBMS's that support the Drizzle or MySQL wired protocol. Also it can serve as a direct REST interface to those RDBMS backends.
If you're using MySQL, then MySQL 5.0 ~ 5.5 is required. We're not sure if MySQL 5.6+ work; reports welcome!
Is there a way to meet the following criteria in distributing a Web Service to Windows machines?
1) Automatic installation and configuration of the Web Server.
2) No configuration (or even awareness) of a Web Server required by the customer.
3) No prompts to download and install Java or .NET - especially anything after .NET 2.0; those installs / restarts can take forever!
In short, is there a way to deliver a single install process that installs the Web Server along with a simple web app without requiring lengthy installations of pre-requisites? Something for even the most non-technical of users?
.NET's WCF almost meets the requirements but getting .NET updated up to 3.0 / 3.5 is a lengthy process and can be a turn-off for customers, even if the install holds their hand through the whole thing.
Rubyscript2exe was also very close, but it is extremely touchy and out-dated.
I am open to any technology / programming language - just looking for the slickest distribution process for my customers that meets the above three criteria.
I've been doing quite a bit of research on this as it is extremely important to me that my users have a simple installation experience. Here are a few things that I've found:
UltiDev Cassini: Cassini is that convenient mini-server that runs when you debug your web apps from Visual Studio or Visual Web Developer. UltiDev Cassini builds on that and looks pretty promising. It offers support for all non-beta flavors of .Net and integrates right into Visual Studio. Most interesting to me is the ability to include as part of your installer. The only down side is that pesky .Net pre-requisite. I can handle helping users get installed up to 2.0, but the install process to move to 3.0 and 3.5 is way too heavy for the typical user.
RubyScript2Exe: I like the premise of an executable Rails app. However, I attempted to use this on a Mac and it is simply too outdated and requires too many workarounds for my tastes. It's too bad, because I love Ruby on Rails development.
Server2Go: This is my favorite of the three options. It is easily distributable (just send off a zip file) and has a lot of nice options. For example, you can configure it to leave the included Apache server running even after the browser closes - that is PERFECT for a nicely packaged web service. It can also provide a customizable icon in the task bar for shutting down the service if necessary. I think this best meets my needs for the time being.
Please, if you know of any other options, let me know.
Also, you may be wondering, "Why not just write a desktop app?". The simple answer is that I don't need much of a GUI, if any. I need a simple to install web service that can be consumed by various other applications (web, mobile, and desktop included).