+1
On 16.06.2010 09:06, Markus Joschko wrote:
I also object strongly against "requiring" jetty. In our company we
always use the same AS for development that also runs in production.
That can be Jboss or Weblogic with all the J2EE setup like JMS queues
and JTA transactions.
Reading that jetty is "required" for development would be a killer
argument against tapestry. I would prefer kind of a "tip" box that
shortly lists the advantages of using jetty for development. However
development should be possible with every web container.
On Wed, Jun 16, 2010 at 3:56 AM, Kalle Korhonen
<[email protected]> wrote:
I just don't think the issue is Tomcat. The problem is Eclipse WTP's
built-in generic and thus awful support for servlet containers
(including Tomcat) that people are trying to use.
Kalle
On Tue, Jun 15, 2010 at 5:57 PM, Thiago H. de Paula Figueiredo
<[email protected]> wrote:
On Tue, 15 Jun 2010 21:36:46 -0300, Howard Lewis Ship<[email protected]>
wrote:
I think we could save people a lot of trouble by coming out and saying
in the (upcoming docs rewrite) that they are required to use Jetty for
development. Everyone keeps shooting themselves in the foot trying to
use Tomcat and its so damn simple to use Jetty instead.
I think we should be very careful wording this so it doesn't seem that
Tapestry only works in Jetty. "Required" is quite strong, maybe we should
use "highly recommeded, saving you a lot of headaches".
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and
instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
