Jetty has moved!
Jetty is a project at the Eclipse Foundation.
Jetty is a project at the Eclipse Foundation.
| Homepage: | http://www.eclipse.org/jetty |
| Downloads: | http://download.eclipse.org/jetty/ |
| Documentation: | http://www.eclipse.org/jetty/documentation/current/ |
| About: | http://www.eclipse.org/jetty/about.php |
| Jetty Powered: | http://www.eclipse.org/jetty/powered/ |
Contact the core Jetty developers at
www.webtide.com
private support for your internal/customer projects ... custom extensions and distributions ... versioned snapshots for indefinite support ... scalability guidance for your apps and Ajax/Comet projects ... development services from 1 day to full product delivery
Skip to end of metadata
Go to start of metadata
private support for your internal/customer projects ... custom extensions and distributions ... versioned snapshots for indefinite support ... scalability guidance for your apps and Ajax/Comet projects ... development services from 1 day to full product delivery
Jetty and JBoss EJB3
JBoss have released with an alpha version of an embeddable EJB3 implementation. It is available for download
Here are the steps required to get jboss-EJB-3.0_Embeddable_ALPHA_5 working with Jetty:
- make sure you're using jre 1.5
- download jboss-EJB-3.0_Embeddable_ALPHA_5.zip and unzip it
- go to the
docs/embedded-tutorial/embedded-wardirectory and build it (just typeant). - unjar the war file in
docs/embedded-tutorial/embedded-war/build/standalone.warto your$jetty.home/webappsdirectory. - move all of the jars in
$jetty.home/webapps/standalone/WEB-INF/libexcept for tutorial.jar to$jetty.home/lib/ext/jbossNote 1 - finally, edit the
$jetty.home/webapps/standalone/EmbeddedEJB3.jspfile. The JNDI lookups for the beans in this file don't work and don't match the documentation, so you need to change them. Find the lines:change them to: - start jetty:
- surf to
http://localhost:8080/standalone/EmbeddedEJB3.jspto test EJB3s in Jetty with the JBoss supplied demo
Note 1: Besides being a good idea to move the jboss jars out of the webapp if you intend on using them with other webapps, it seems to be necessary (at least for now) to avoid a strange ClassNotFound exception.
Labels