[
https://issues.apache.org/jira/browse/TAP5-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Kemnade updated TAP5-245:
--------------------------------
This issue has been last updated about 1.5 years ago and has no information
about the versions that are affected. That makes it hard to determine whether
it is still relevant.
If the issue still persists with the current stable version (5.3.7) or the most
recent development preview of Tapestry (5.4-beta-6), both of which are
available from Maven Central, please update it as soon as possible, adding the
respective version(s) to the issue's "Affects Version/s".
> Better documentation on development environment.
> ------------------------------------------------
>
> Key: TAP5-245
> URL: https://issues.apache.org/jira/browse/TAP5-245
> Project: Tapestry 5
> Issue Type: Improvement
> Components: documentation
> Reporter: Borut Bolcina
> Labels: tapestry5-review-for-closing
>
> I am just copying the email discussion post:
> Luther,
> it is true - you can work with WTP and Tomcat 6, but that is like driving the
> BMW M5 without the M button being pressed.
> Try running the quick start T5 application with mvn jetty:run and with
> WTP/Tomcat. Try changing Start.java and then clicking the refresh button in
> the browser. Even in this one page web application with 2 java files it takes
> 10-times longer with WTP/Tomcat combo to display the changed Start page. I
> can imagine it gets worse with larger apps.
> And here is my point - if one of the main strengths of Tapestry 5 is live
> class reloading, then it is of paramount value to tell developers how can
> they harness the power in different development environments. This is where
> the documentation fails. I also own the Alexander's book and as much as the
> book is welcomed, it is outdated and the information given on page 43 is not
> true (at least in present moment):
> "You will see that the change you have made is not reflected by the running
> application, because you have changed an HTML file, and not Java code. Smilar
> to NetBeans, Eclipse doesn't care about changes in HTML files. One way to
> update the application in such case is to follow the advice given for
> NetBeans - make change, even if it is an insignificant one, to some Java
> file, and save the file. The application will then be reloaded automatically."
> This is so not T5-ish.
> If there are many ways to develop T5 web apps, then some of this cases should
> be explained clearly as this is IMHO one of the barriers many new tapestry
> users are hitting at the very beginning. Of course some cases can be
> published on wiki, but the most common two or three must be on main T5 page -
> this is where most users start.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
