[jetty-user] Re: Getting started with Jetty, BlazeDS, Flex & CometD?

David Hoffer <[email protected]> Tue, 15 Nov 2011 11:33:36 -0700
Newsgroups gmane.comp.java.jetty.support
Message-ID <CAA8BW8Hv7vZ80LfrkLuhvK0QAkCOsi9EhMeDjg2=ds_wS_zA+w@mail.gmail.com>
Regarding jetty-blazeds not being fully mavenized, I now see the problem.
Those are adobe BlazeDS components they still haven't put in a public maven
repo...what a pain.

So besides that....is jetty-blazeds the best approach for a Flex/Comet
solution that works with Servlet 3?

Thanks,
-Dave

On Mon, Nov 14, 2011 at 3:26 PM, David Hoffer <[email protected]> wrote:

> It's been awhile since I have used Flex/BlazeDS, I have a new project
> where I need a very efficient & scalable comet like solution for a Flex
> application with backend Java server.  So I'm thinking Servlet 3.0 (Jetty
> Continuations is deprecated right?)  Since I understand BlazeDS doesn't
> support Servlet 3.0 yet I assume that means I need jetty-blazeds?  Is this
> a modified BlazeDS stack that supports Servlet 3.0?  One problem with this
> is that it isn't fully mavenized...which I need.  It complains that
> flex-messaging-core & flex-messaging-common aren't available, why publish a
> maven artifact that has references to two artifacts on the local file
> system?  What are these artifacts, who wrote the code?  (The guy managing
> our Nexus server is going to wonder why org.mortbay.jetty created two
> com.adobe.flex artifacts, etc.)
>
> Also is CometD the right/best comet solution to go with the Jetty,
> BlazeDS, Flex stack?
>
> Am I going in the right direction here?  Any help is greatly appreciated.
> Are there some getting started docs for Jetty, Servlet 3.0, high
> performance comet solution?
>
> Thanks,
> -Dave
>