I think that it isn't a problem to use Jetty in production. In brazil
there is a huge forum about java www.guj.com.br and they were using
Tomcat, the forum was slow, they changed to Jetty and added some other
techniques and now everything goes fine.

Sure that if you want to use JEE, IMHO I suggest you to use glassfish.

On Wed, Mar 25, 2009 at 11:13 AM, Chenini, Mohamed <mchen...@geico.com> wrote:
>
> Are you implying that in a production environment Glassfish, Tomcat, or
> JBoss are better to use with Wicket than jetty? I was planning to learn
> jetty to use it in development and in production and the 'Pro Wicket'
> book states that  "it [Wicket] was is a good fit for developing Wicket
> applications"
>
> Please advise.
>
> Thanks,
> Mohamed
>
> -----Original Message-----
> From: Martijn Dashorst [mailto:martijn.dasho...@gmail.com]
> Sent: Wednesday, March 25, 2009 9:25 AM
> To: users@wicket.apache.org
> Subject: Re: Looking for a book on the jetty server
>
> I'm not sure if most actually *deploy* their production servers on
> Jetty (there's nothing holding anyone back), but I think that Tomcat,
> Glassfish and JBoss are also very popular.
>
> Jetty is most commonly used during development because it is so easy to
> embed.
>
> AFAIK no books have been written for Jetty.
>
> Martijn
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
> ====================
> This email/fax message is for the sole use of the intended
> recipient(s) and may contain confidential and privileged information.
> Any unauthorized review, use, disclosure or distribution of this
> email/fax is prohibited. If you are not the intended recipient, please
> destroy all paper and electronic copies of the original message.
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Reply via email to