the Jetty versions that implement the Servlet 3 spec are 8.x and greater.
Jetty 7.x still implements 2.5, and that's why you have those missing
method errors.
However, you do not need Servlet 3 to use CometD in Jetty, unless your
application make direct use of Servlet 3 features.
So, the recommended setup would be CometD 2.3.1 + Jetty 7.4.5, and
make sure you have the right servlet jar in the classpath (must be the
servlet 2.5 jar).
Jetty autodetects the Servlet specification version by loading the
Servlet class and testing if new Servlet 3 methods are present, you
must be careful about what servlet jar you have in classpath.
With the right jar, you should be good.
For an example of how to setup CometD using Jetty embedded, look here:
https://github.com/cometd/cometd/blob/master/cometd-java/cometd-java-examples/src/main/java/org/cometd/examples/CometdDemo.java
https://github.com/cometd/cometd/blob/master/cometd-javascript/common-test/src/test/java/org/cometd/javascript/AbstractCometDTest.java
Simon
--
http://cometd.org
http://intalio.com
http://bordet.blogspot.com
----
Finally, no matter how good the architecture and design are,
to deliver bug-free software with optimal performance and reliability,
the implementation technique must be flawless. Victoria Livschitz
--
You received this message because you are subscribed to the Google Groups "cometd-users" group.
To post to this group, send email to cometd...@googlegroups.com
To unsubscribe from this group, send email to cometd-users...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/cometd-users
Visit the CometD website at http://www.cometd.org