Great.. my servlet will inject EJB3 beans anywa<y, so tomcat and jetty
are already out of the game :)
On Thu, Jan 15, 2009 at 6:38 PM, <glassfish_at_javadesktop.org> wrote:
> There's nothing really wrong with this. The only downside is that while GF v3 is on the fast track to be an early adopter and implementer of Servlet 3, that doesn't mean that others are sure to follow For example, I have no idea when Tomcat or Jetty might offer a compatible v3 container, it may well be very soon, I don't follow either project. Most likely the other commercial vendors will be behind the curve as to actual compliance as well.
>
> So, the only detail there is that you'll be, early on, limited to basically working with bleeding edge and early releases of GF v3.
>
> Clearly that can frustrate development, keeping up with a developing container, etc.
>
> That's the only real downside because you're relying on features that are, while perhaps stable, a moving target both in scope and actual implementation, and later on you may have limited deployment options in terms of other container support when you decide to go live.
>
> Not saying its a bad idea, just pointing out the consequences of it.
> [Message sent by forum member 'whartung' (whartung)]
>
> http://forums.java.net/jive/thread.jspa?messageID=326274
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>